How it runs when the products are in place.
Fictional sample. A fictional structural engineering practice on Microsoft 365. Nothing here describes a real customer or a real project.
-
1
The scope is the plan, until a person changes it
Larkspur's signed scope goes into SimpleOS Delivery as a drafted plan with phases, tasks, dependencies and the exclusions the document rules out. The project engineer previews it, moves one milestone, and approves it. The acceptance criteria stay attached to the project, so a change order starts from the record rather than from memory.
-
2
Subcontractors see the burn, never the rate
Vendor organisations on the project get a tokenized, read-only burn portal: hours against budget, nothing else. Vendor scorecards sit on the Larkspur side.
-
3
Hours become an invoice someone approved
Simple Time drafts entries from calendar and mail with a confidence value and the reasoning, the project manager approves the week, and the invoice is built from approved entries with a branded PDF and a payment link. Nothing is billed from an unapproved entry.
Every sentence above describes what the named products do today, in the words of each product's own "what works today" list. What a product does not do yet is on that product's page, with the date it was checked.