Website Every screen Assumptions Design system Every screen, by surface and module 32 screens prove 16 modules. All roles share one set of data held in this browser: what the supervisor captures on the phone is what the client approves on the web. Use Reset demo in the bar below to start again.
Start the guided story
Website 2 screens Screen What it proves Modules Landing page The product, the argument for it, entry to every role, Book a Free Demo Call M1 M2 Sign in Credentials with validation, or open as any role M1
Project workspace · shared by client, contractor and consultant, each with their own permissions 26 screens Screen What it proves Modules Client dashboard THE client screen: work done by section, money against work, what is payable now and why, what is holding the job up M2 M9 M10 M11 Dashboard, as contractor Same dashboard, contractor decisions: claim the payment, price the instruction, answer the delay M2 M9 M10 Dashboard, as consultant Same dashboard, certification waiting M2 M9 M10 Projects, as contractor Four projects, what needs him today M2 Projects, as consultant Two assigned projects; certificates waiting M2 Setup: documents What Tally read from the three documents M3 Setup: first run New project wizard, reading state, unreadable-scan error M3 Channels WhatsApp group, number mapping, unknown number, inbox, dropped connection M6 People and access Invite, per-person access, capability matrix M1 People and access, denied Permission-denied state, logged M1 BOQ As written and as understood, weights, stage split per item M4 BOQ review Low-confidence matches, confirm and teach the library M4 Schedule Dated activities against what the record shows M5 The record Split view, filters, search, zero results, relink, manual entry M7 Progress Where the percentage comes from, stage by stage, photo by photo M9 Progress, as consultant Verify or dispute a figure M9 Payments, as contractor Issue the invoice when a milestone unlocks M10 Payments, as consultant Certify or dispute M10 Payments, as client Approve and record payment, or return M10 Delays Cause, responsible party, effect, evidence, response M11 M14 Instructions and variations The WhatsApp instruction Tally caught; price it M13 Approvals waiting Who is holding what, for how many days; approving clears the risk M14 Reports Weekly report written from the record; pack builder M15 Evidence pack Chronological, cited, printable M15 Ask the record Cited answers, and an honest “not in the record” M12 Notifications Per-role inbox and rules M11
Site app · phone 4 screens Screen What it proves Modules Today What the schedule expects, captures so far, no-signal switch M8 Capture Photo, caption, AI link, progress moves, payment unlocks M8 Project group The WhatsApp group with what Tally understood under each message M6 M8 Sent and waiting Offline queue and sent history M8
Provider console · the team that runs Tally 5 screens Screen What it proves Modules Overview Accounts, revenue, running cost, what needs attention M16 Accounts Client-held and contractor-held accounts, new account M16 Item library Synonyms and stage splits; add and remove M16 M4 Usage and cost AI and WhatsApp cost per project against its fee M16 Audit log Append-only, filterable M16
This build 2 screens Screen What it proves Modules Assumptions What is real, what is scripted, what we need from you M1 Design system Tokens, type, controls, domain components, bans M1
Modules S = you asked for it · O = we added it M1 Accounts and accessOwner invites people, sets access person by person; a fixed matrix stops either side editing the other’s evidence. M2 Portfolio dashboardsEach side sees its own projects and what needs it today; click through to the project. M3 Project setupThe three documents: BOQ, contract with payment terms, schedule. First-run and unreadable-scan states. M4 BOQ intelligenceReads PDF or Excel, matches trade synonyms, weights items, splits each into stages, queues unsure matches for a person. M5 Schedule understandingDated activities, not a Gantt; checked daily against the record. M6 Channel linkingPlatform WhatsApp number in the group, number to role mapping, project inbox address, dropped-connection state. M7 The recordEvery photo, message and email in order, linked to a BOQ item, original preserved. M8 Site capturePhone capture with timestamp and caption, AI linking, offline queue. M9 Progress engineBOQ-weighted progress with the evidence behind every point; consultant verify or dispute. M10 Payments and transactionsMilestones from the contract unlock on measured progress; issue, certify, approve, ledger. M11 Delays and notificationsSchedule against record, delay notices, notification rules. M12 Ask the recordPlain-language question, cited answer, honest zero-result. M13 Instructions and variationsVerbal WhatsApp instructions caught as unpriced, priced, approved. Ours. M14 Delay attribution and approvals ageingResponsible party with evidence; who is holding an approval and for how long. Ours. M15 Reports and evidence packWeekly report written from the record; chronological cited pack for a claim. Ours. M16 Provider consoleAccounts, subscriptions, master item library, AI and WhatsApp cost per project, audit log.