Discovery call → priced SOW → accept and pay
The problem
Statements of work are written by hand from call notes. Scope drifts from what the client said, and capacity conflicts surface after the client has signed.
How it's resolved
The AI reads the discovery call against the studio’s service catalog and its written rates and estimating rules, and writes the statement of work as a document, each line citing the moment in the call or the rule it came from. Code prices every line in whole cents and checks every role’s hours, month by month. When a month runs short, the studio’s own rule moves the work with no client date first, the AI explains the move in the margin, and the partner applies it in one click. The client opens a proposal in its own colors by its link, with no account, and pays the deposit. The order splits by seller and the hours are booked.
What you'll see
- 01The call’s last seconds: the partner promises a statement of work this week
- 02The AI drafts it from the recording, each line citing its moment in the call or one of the studio’s rules
- 03At 01:35 the client asks for single sign-on, and the studio’s rule adds the security review that comes with it
- 04$97,020 against the client’s $100,000 budget, with senior engineering 32 hours short in December
- 05The studio’s rule moves the AI pilot to January, and the partner applies it in one click
- 06The client accepts its proposal and pays the $29,106 deposit; the order splits by seller and 550 hours are booked
Under the hood
Each business term in the video, and the Traide building block it runs on.
| In the business | On Traide |
|---|---|
| Statement of work | Draft order, sent as a quote |
| Where a line came from | Order line note |
| Subcontractor | Seller, with its own sub-order |
| Role hours | Capacity pools, booked as TICKET entitlements |
| Rate card | Policy (CMS page), read by the AI |
| Deposit | Payment, captured on acceptance |
- Reading with citations
- Pricing in code
- Capacity planning
- Generation
Have a problem like this one?
You'll talk to a senior engineer, not a sales rep, and leave with a clear first move — whether or not we work together.