Chapter 11 of 11
Can the whole system earn?
Do project margins survive the costs of running the company?
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.
Project contribution must fund a company.
$3,740 remains before tax. That is $260 short of a proposed $4,000 reserve.
If the owner leaves $3,000 of work unpaid, cash temporarily looks better; the economic cost is still real. A sustainable arrangement needs a credible way to pay for that work, not an invisible subsidy.
AI changes effort and the bargain.
Faster implementation can reduce some delivery costs. It can also reduce the price buyers accept, increase review work or make an asset easier to copy. Test price, delivery time, assurance, maintenance and demand separately.
A fixed scope could reward better tooling; an outcome-linked model could share verified value. Neither works if the measured outcome is outside the team’s control or the floor fee cannot fund responsible delivery.
Shared assets need an owner and a budget.
Reuse can improve a future engagement only when rights, maintenance and relevance are clear. A common component may receive a scoped license, a maintenance budget or a buyer-funded extension.
Record who can change it, who can license it, who pays for updates and what happens when someone exits. Publishing an asset does not establish a perpetual claim on every project that touches it.
No customers still has a cost.
The software example commits $6,000 to building, $300 to hosting and $1,200 to maintenance over its first 90 days. With no customers it has a $7,500 loss before any failed acquisition spending. Money spent pursuing customers does not disappear because nobody converts.
A second win needs actual capacity.
The $80,000 project budgets 632 role-hours across eight weeks, including 360 engineering hours, plus separately priced component work. A second simultaneous project needs another available team or a changed schedule; the same hours cannot be promised twice.
Before an award, confirm each firm’s available hours, skill fit, dependencies and reserve capacity. A community directory or certificate does not establish that availability.
What the first experiments need to prove
| Experiment | Evidence of a win | Reason to stop or change |
|---|---|---|
| Independent brings a customer; buys a bounded package | Customer permission, accepted scope, paid invoice, useful handover and supplier margin after actual time. | Unclear prime, disputed attribution, endless presales or unpriced integration work. |
| Buyer funds evaluation before deployment | A paid decision-quality assessment, even if the result is no build. | Buyer only values favorable findings, no usable baseline or no decision-maker. |
| A team pays for a maintained workflow or skill | Repeated use, a renewal decision, manageable support and a clear maintainer budget. | Every install becomes custom consulting, support exceeds the fee or adoption never persists. |
For each test, name the payer, accountable lead, budget limit, acceptance evidence and review date. Decide what to repeat using observed work and settled invoices; interest, community size and repository adoption are different signals.
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.
The tool is only part of the investment
The 2021 Productivity J-Curve paper explains how complementary intangible investment can initially lower measured productivity before later benefits appear.
Application to this design: Budget workflow redesign, integration, learning and review. Compare the complete change with an existing product or a simpler process improvement; test whether anyone captures enough value to fund it.
Limits: An aggregate measurement framework does not predict a particular project’s payback, justify indefinite losses or supply a percentage to add to these examples.
A measured task gain is not a revenue forecast
Generative AI at Work, revised November 2024, studies 5,172 support agents and reports 15% more issues resolved per hour on average. Effects differed substantially by experience and skill.
Application to this design: Measure accepted work, quality, operator time and actual cash effects separately. Keep adoption and cash realization as assumptions to test, rather than multiplying revenue by a published productivity result.
Limits: This is one customer-support setting. The result does not establish engineering savings, this customer’s ROI, a contractor rate or a universal AI uplift.
Even the productivity estimate needs scrutiny
METR’s February 2026 update says its later developer experiment gives an unreliable signal of the current effect: participant and task selection changed, and concurrent-agent work complicated time measurement.
Application to this design: Track end-to-end delivery, review and rework on comparable tasks. Change price, engineering effort and assurance effort independently; faster generation need not increase retained margin.
Limits: Neither the earlier slowdown nor the later estimates establish today’s universal engineering effect. Self-reported value, measured task speed and collected revenue are different outcomes.
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.
Monetization changes can damage the bargain
In March 2023, Docker reversed its announced Free Team sunset after community feedback and offered refunds to affected customers who had upgraded.
Application to this design: Keep public-use rights, optional paid services and membership expectations clear. Make proposed changes, decision authority, objections and participant exit visible; community trust cannot be treated as automatic demand.
Limits: This documents a policy reversal, not Docker’s business failure or a measured loss caused by the announcement. It supplies no optimal price or governance formula.
A growing content library is not a cash entitlement
Demand Media’s Content & Media revenue fell from $137.038 million in 2014 to $73.814 million in 2015. Reported visits and revenue per thousand visits both declined.
Application to this design: Track audience access, qualified conversations, paid conversion and monetization separately. Budget publishing as an expense unless a sponsor or buyer actually funds it; do not count the same downstream sale twice.
Limits: The filing describes multiple contributing factors, while its marketplace business grew. This is not evidence that all creator businesses fail or an estimate of a solo creator’s earnings.
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