ScopeRunway — Pre-Alpha Walkthrough

Thanks for taking a look. This is a working pre-alpha, not a finished product — read the honesty notes below before you start, they'll save you a surprise.

Before you start — what this is and isn't

• Your data lives only in your browser. There's no account and no server-side copy. Everything is saved to this browser's local storage. Clearing site data, switching browsers, or switching devices loses it — export before you do either (Export JSON on any project page gets you a file you can re-import).
• EUR only, for now. Every figure — typed in or AI-extracted — is euros. There's no currency field yet. If your numbers are in another currency, treat the figures as unitless for this review.
• Desktop only. No mobile layout.
• This is pre-alpha. Some rough edges are expected — that's what this review is for.

1. Get in

You'll have a link and an access code from me directly. Enter the code once — it's remembered for a year in this browser.

2. Create a project

From the project list, New Project. You'll set:

• Project name and sector (Residential, Commercial, Industrial, …)
• Target budget in whole euros
• How to start the breakdown:
  • Blank project — three placeholder categories to edit from scratch
  • Import from file — load a previously exported .json
  • Create with AI (beta) — upload a project brief (PDF/DOCX/TXT/MD, up to 3 files) and the app drafts a starter breakdown: facility type, sector, and scope items, all editable before anything is saved. No brief handy? There's also an offline path — import a prepared *.semantic.json with no API call at all. It's labelled beta in the app for a reason — check what it produces before trusting it.

3. Build the physical hierarchy

On the project page, under Sites & Facilities: + Site, then + Facility under that site. This is the physical structure the project sits on — site → facility → floor — separate from the fee breakdown below.

4. Break down the fee — WBS

Open WBS. This is the core of the tool: your target budget split across weighted categories (e.g. Strategic/Pre-Design, Technical Design Production, Project & Design Management, Digital Delivery/BIM), each showing its live euro amount and a running balanced check against your total. Drag the category weights, override any line's percentage or amount directly, add sub-lines, or apply a structural template. Undo/redo is there if you want to experiment.

5. Phasing, Schedule, Programme, Deliverables

• Phasing — spread the WBS across project phases.
• Schedule — a Gantt-style view of that phasing over time.
• Programme — the deliverables register in schedule form.
• Deliverables — per-facility deliverable list (populated once a facility exists under a site).

6. Export

Export JSON (full project, re-importable) or Export CSV (register-style export) — both on the project page and inside WBS.

What I want your opinion on

This isn't a bug hunt — it's a validation check. Specifically:

1. Does the WBS breakdown match how you'd actually structure a fee? Would you change the default categories or weights?
2. Is the physical hierarchy (Site → Facility → Floor) the right shape, or does your work need something it doesn't capture?
3. The AI brief import — try it with a real (or realistic) brief. Does the draft it produces save you time, or create more editing work than it's worth?
4. What's missing that would stop you from using this on a real project today, beyond the known gaps below?

There's a full roadmap on the landing page if you want to see what's already planned — including a Risk & Assumptions Register in active development, and the EUR-only limitation, which is a known gap, not an oversight.

Send feedback either through Give feedback in the app, or directly to me.