Chapter 8 of 11
When the cash arrives
Can a profitable project still run out of money?
Illustrative examples only. These are possible commercial arrangements, not current offers, agreed pay, promised work, forecasts, or evidence of customer results. All amounts are USD, before tax.
The same $80,000 project, on a calendar.
The fee and $59,760 cost budget match the project chapter. This schedule assumes customer receipts of $32,000 at mobilization, $24,000 at day 30 and $24,000 at day 60. Costs are paid on their own dates. The schedule is fictional; dates and due conditions must be negotiated before work.
| Collection scenario | Customer cash collected | Largest funding gap | Final project cash | After $4,000 reserve |
|---|---|---|---|---|
| Receipts on the agreed dates | $80,000 | $8,000 | $20,240 | $16,240 |
| Every receipt arrives 30 days late | $80,000 | $40,000 | $20,240 | $16,240 |
| The final $24,000 is never collected | $56,000 | $8,000 | -$3,760 | -$7,760 |
A late receipt changes financing need. A permanently unpaid receipt also reduces what the project retains. Neither permits the prime to silently rewrite supplier due dates. Starting cash must at least cover the modeled gap, with additional headroom for risks not modeled here.
Inspect the dated cash events
| Day | Event | Cash movement | Balance after event |
|---|---|---|---|
| 0 | Payment | -$4,000 | -$4,000 |
| 0 | Receipt | $32,000 | $28,000 |
| 15 | Payment | -$18,000 | $10,000 |
| 30 | Payment | -$18,000 | -$8,000 |
| 30 | Receipt | $24,000 | $16,000 |
| 45 | Payment | -$16,000 | $0 |
| 60 | Payment | -$3,760 | -$3,760 |
| 60 | Receipt | $24,000 | $20,240 |
| Day | Event | Cash movement | Balance after event |
|---|---|---|---|
| 0 | Payment | -$4,000 | -$4,000 |
| 15 | Payment | -$18,000 | -$22,000 |
| 30 | Payment | -$18,000 | -$40,000 |
| 30 | Receipt | $32,000 | -$8,000 |
| 45 | Payment | -$16,000 | -$24,000 |
| 60 | Payment | -$3,760 | -$27,760 |
| 60 | Receipt | $24,000 | -$3,760 |
| 90 | Receipt | $24,000 | $20,240 |
| Day | Event | Cash movement | Balance after event |
|---|---|---|---|
| 0 | Payment | -$4,000 | -$4,000 |
| 0 | Receipt | $32,000 | $28,000 |
| 15 | Payment | -$18,000 | $10,000 |
| 30 | Payment | -$18,000 | -$8,000 |
| 30 | Receipt | $24,000 | $16,000 |
| 45 | Payment | -$16,000 | $0 |
| 60 | Payment | -$3,760 | -$3,760 |
What the research changes about this model
These selected studies and historical cases explain mechanisms to test. They are not a systematic review, industry earnings survey or validation of this network. The teaching applications are our proposed responses, not conclusions that the sources tested for Intent. Scenario prices and volumes remain explicit assumptions.
Technical reputation does not remove demand risk
Thoughtworks reported a 13.1% revenue decline and a $68.661 million net loss in 2023. Management described cautious client budgets, shorter contracts and lower headcount among the factors affecting revenue.
Application to this design: Include lost pursuits, delays, unfilled capacity and cancellation. Require evidence of funded demand before committing shared capacity; a technically capable network can still lack paying work.
Limits: A large firm’s historical downturn is neither an industry failure rate nor an Intent forecast. Management’s explanation does not isolate causation, and net loss is not cash burn.
Research, evidence boundaries and diagram method
This is a proposed operating model illustrated with constructed numbers. The sources below establish program mechanisms and constraints; none establishes the scenario rates, Intent revenue, individual compensation or a guaranteed source of projects.
- Anthropic: Services Track and Partner Hub — Distinguishes practice standing from referral credit and deal protection. Does not establish any scenario fee, Intent tier, inbound work or cash entitlement. Checked 2026-10-12.
- OpenAI Partner Network — Shows an official build, co-sell and delivery program. No claim of Intent enrollment, procurement approval, referral rate or awarded work. Checked 2026-10-12.
- AWS Partner Central: Creating a fund request — Separates funding approval, cash claims, invoices and credits. Eligibility and program terms apply; the customer-paid discovery example is not an AWS award. Checked 2026-10-12.
- AWS Marketplace: Managing disbursements — Explains why accepted work and available cash can occur at different times. A marketplace example only; other procurement and payment routes have their own terms. Checked 2026-10-12.
- Microsoft: Manage co-sell opportunities — Supports a customer-consent gate before sharing contact details in co-sell. Does not grant another firm ownership of an account, a universal commission or guaranteed seller help. Checked 2026-10-12.
- Langfuse: Self-hosted pricing — A public example separating open-source software from paid enterprise capabilities and support. This is an offer structure, not evidence of Intent demand, profitability or transferable pricing. Checked 2026-10-12.
- GitHub Sponsors: Sponsorships, fees and taxes — Shows a distinct sponsorship route for eligible open-source contributors. Sponsorship is not a guaranteed sale, support contract or license transfer; no sponsorship is assumed in the ledgers. Checked 2026-10-12.
- AWS Marketplace: Channel Partner private offers — Distinguishes approved resale from ordinary vendor consumption. This does not authorize resale of an arbitrary model, API, dataset or contributor’s software. Checked 2026-10-12.
Diagram method: Cathryn Lavery’s open-source Diagram Design, using its Sankey, waterfall, bar, line, architecture and layer-stack references in Intent’s established visual style. The selected chart grammar explains the relationship; the worked examples supply the data.
Apply it to a real workflow.
Start with a customer problem, the people who can help, and a clearly bounded first piece of work.
Request an outcome