What is real here, what is scripted, and what we need from you

This is a front-end build, made to agree the product before any back end is written. Everything you can click works. The intelligence behind it is scripted, and this page says exactly where the line falls.

Real in this build

Every screen, state and permission rule. Switch role in the bar at the bottom and the same page changes what it lets you do. A consultant opening People and access gets turned away, and the attempt is logged.
One shared dataset across all five roles, kept in this browser. Capture on the phone, then open the web record: it is there. Approve a payment as the client and the contractor sees it.
The client dashboard is computed, not drawn. Work done per section, value earned, money paid against work completed, what is payable now and the section percentages behind it, what is holding the job up. Every figure comes from the BOQ and the record. Nothing on it was typed in.
The progress arithmetic. Item amount times its weight, split across the stages you described: supply frames, supply boards, install frame, install board, accessories, quality check. One photograph moves the sample project from 19.2% to 20.4%.
Payment milestones that unlock themselves at the thresholds in the contract, and the full chain after that: issue, certify, approve, pay, with the dispute and return paths built.
The numbers cannot contradict each other. Every screen reads the same figures, so the dashboard, the BOQ, payments and the weekly report always agree.
It opens by double-clicking index.html. No server, no install, no network. It works on a plane.

Scripted for now

Reading the BOQ, the contract and the schedule. The results shown are prepared. In the product they come from document AI, plus your own Excel of item names and stage percentages.
Reading WhatsApp and email. The messages in the record are sample content. In the product they arrive through the WhatsApp Business Platform and a project inbox address.
Linking a photograph to a BOQ item and stage. The three sample photos in the phone view have prepared answers, including the confidence figure.
Ask the record. Four questions have written answers. Ask anything else and it shows you the entries it would answer from, rather than pretending.
The "about one day to go" forecast on the dashboard is a straight-line projection from the project average. A real one would read the schedule and the crew on site.
Sign-in, invitations, notifications by email and WhatsApp, and PDF exports. The screens are real; nothing is sent.

Numbers we invented, and where they appear

replace these with yours before anyone quotes them

USD 490 per live project per month, on the landing page and throughout the provider console. A placeholder, not a recommendation.
The running costs: USD 0.004 to read a message, USD 0.11 a photo, USD 0.03 an email. Plausible orders of magnitude for planning, not quotes from a supplier.
The project volumes: 1,284 messages, 96 photos and 143 emails on the sample project. That is what a five month fit-out plausibly generates. The record itself holds 29 entries, which are the ones that changed something.
The sample project. Harbour Street Office, Meridian Freight, Atelier Forma Interiors and everyone in it are invented, priced in US dollars at a realistic level for a 740 m² office fit-out.

What we assumed from the call

The platform starts once design and tendering are finished and a contractor is appointed. It is not a design or tender tool.
Either side can hold the account: a client who brings in their contractor, or a contractor who brings in their clients. One subscription per live project, and whoever is invited pays nothing.
A client usually has one live project at a time, so they land straight on it. A contractor lands on their list of projects.
Stage percentages per item are general trade knowledge held centrally, not negotiated per contract. A project keeps the split it started with if the central library later changes.
A delay notice or a payment notice always reaches all sides. One party cannot switch it off for the others.
The consultant certifies progress and invoices. Where there is no consultant, somebody still has to.

What we need to settle together

WhatsApp groups. The platform number has to sit in each project group. Official group support for business numbers has limits on group size and features, so we will confirm the route with you early: the official Groups API, an approved provider, or, as a fallback, a forward-to-Tally number with chat export upload. The product design is the same either way, and we would rather agree it before quoting than discover it during the build.
Your Excel of item names and stage percentages. It becomes the first version of the master library, and it is the thing that makes reading a BOQ work.
Two or three real BOQs and one contract, anonymised, so we can measure reading accuracy before we price that part of the work.
Who certifies when a project has no consultant: the client directly, or nobody?
Your price. The console shows cost per project so the fee can be set on numbers rather than a guess. We need your target price and the message volumes you expect.

Later, as you said

Comparing site camera footage with the designer’s 3D views to confirm progress visually. You parked it yourself on the call, and that was the right call. The record, the BOQ link and the stage model built here are exactly what that feature would plug into, so nothing on these screens has to change to add it.

Using this build

The data lives in this browser only, and nothing leaves it. Reset demo in the bar at the bottom puts everything back to the start, which is worth doing before you show it to anyone. If a screen ever looks empty after an update, that is old data in the browser: reset it once and it is fine.