A 13-week cash forecast that explains itself
The problem
Cash forecasts are rebuilt in spreadsheets every week, and nobody can quickly say why a week moved.
How it's resolved
Lintelmark Workplace Exchange, a fictional B2B marketplace for office fit-out. Five studios sell to firms on net 30 and net 45, and the ledger already holds what each firm owes and what each studio is owed. Over the weekend, through the API, two shipments slip four weeks and one ships early. Code rebuilds the 13-week forecast from the ledger, reconciles every order part to it to the cent, and places each collection by the firm’s terms and each payout by the weekly run. The controller asks why week 7 dropped. Code computes the bridge against last week’s locked version: four entries explain all of the $402,040 change. The AI puts them into words, and code checks every figure it writes. A slider has the largest firm pay 30 days late, and week 7 falls under the floor. The controller signs this week’s version, written to the marketplace’s books and read back.
What you'll see
- 01This week’s 13-week ladder against last week’s locked version: week 7 has dropped
- 02Rebuilt from the ledger after three changes through the API: 11 order parts reconciled to the cent
- 03“Why did week 7 drop?” Code’s bridge: four entries explain all $402,040 of the change
- 04The AI explains it in words, and code checks every figure it writes
- 05Week 7’s net splits into the three ledger entries it came from
- 06The largest firm pays 30 days late: week 7 falls to $126,490, under the $150,000 floor
- 07The controller signs version 2, written to the marketplace’s books and read back identical
Under the hood
Each business term in the video, and the Traide building block it runs on.
| In the business | On Traide |
|---|---|
| Closing cash | Ledger: funds collected and payouts disbursed, inside the bank balance |
| Money in and out | Ledger: receivables by firm and payables by studio, reconciled to the cent |
| When cash moves | Account and order metadata: net 30, net 45, each part’s ship-by date |
| The locked version | Seller private metadata, written and read back |
Guardrail. Code computes every number. The AI only explains them, and code checks every figure it writes. The controller signs each version. The opening cash is the controller’s bank balance, kept with each version; everything after it comes from the ledger and the terms on each account and order. Test money.
- Forecasting
- Explanation
- Scenario reasoning
More demos
- Workflow orchestrationDiscovery call → priced SOW → accept and pay
- Workflow orchestrationDay-1 ready: one approval, four teams
- Product developmentA catering order by text, in the customer’s language
- Workflow orchestrationThree-way match on autopilot
- Commerce and marketplace buildsAgent-ready tours and stays
- Product developmentAn activity guide → accessible, translated registration
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.