How it runs when the products are in place.
Fictional sample. A fictional forty-person advisory firm on Microsoft 365. Nothing here describes a real customer.
-
1
A signed scope becomes a plan someone approved
Meridian signs a scope of work in Simple Growth, where the proposal was drafted, accepted by signature and the deposit taken. The signed document imports into SimpleOS Delivery as a drafted plan: phases, tasks, dependencies and the exclusions the document rules out. The delivery lead reads it as a preview, changes two tasks, and approves it. Nothing is committed until she does.
-
2
Hours are captured from the week, not remembered on Friday
Simple Time drafts entries from Outlook calendar, Outlook mail and Teams chat, each one carrying a confidence value and the reasoning behind it. A consultant corrects two of them. His manager approves the week from a queue. The invoice is built from approved entries, with the retainer drawn down, and nothing reaches the client before that approval.
-
3
The slipping project shows up before the status meeting
Delivery scores portfolio risk and flags overdue work across every active project, and proposes a rebalance of the workload heatmap. The proposal is a proposal: a person accepts it or does not. Vendors on the project see hours against budget in a read-only burn portal and never see rates.
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.