Illustrative scenario
S$ 42
Contribution, not blended margin
A commerce team selling on its own site and two marketplaces.
Playbooks
How the pack lands in a real month
Four illustrative scenarios. They are not client stories, not testimonials, and not results we claim to have produced. They show the grain of the work.
Multi-channel commerce
The ledger shows a healthy gross margin. Paid media, take-rates and last-mile fees live in three other files. In this scenario the pack splits contribution by channel after variable cost. Own-site sits near S$42 contribution per order; one marketplace sits near S$9 after ads and fees. The next campaign budget follows the channel that still pays back, not the blended number that hid the leak.
What we would build: a channel P&L, a 13-week cash view that follows marketplace payout lags, and a dashboard tile for contribution this week versus last.
Illustrative scenario
Subscription cash versus booked revenue
A software firm bills annually and recognises monthly. Cash looks strong in month one of a cohort and thin in month ten. In this scenario the pack keeps recognised revenue on one tab and a 13-week cash view on another, with cohort payback in a third. Hiring is tested against the cash path, not the accrual path.
What we would build: a deferred-revenue bridge, cohort unit economics, and a cash model that treats annual prepay as a timing item, not a run-rate.
11 mo
Payback that survives a price change
Illustrative payback after a 12% list-price cut on one plan.
Illustrative scenario
Multi-entity group in Singapore
Two operating entities and a holding company, SGD and one foreign currency. Each entity already has a ledger. The board still receives three packs and a manual consolidation the night before. In this scenario the dictionary locks intercompany rules once. The pack consolidates on a named day and still traces a line back to the entity file it came from.
What we would build: a consolidation sheet, a currency note, and a board pack that does not invent a fourth set of numbers.
Illustrative scenario
Project firm with WIP
A services company bills on milestones and tracks time in a separate tool. Utilisation looks fine; cash does not. In this scenario the pack joins WIP, utilisation and a 13-week receipts view so a delayed milestone shows up as cash risk, not as a surprise in week twelve.
What we would build: a project contribution cut, a WIP ageing, and a cash view that follows contracted payment dates.
Use a playbook as a starting brief
Write which scenario is closest and what your pack cannot answer today. We will say in one working day whether a 14-day sprint still fits.