What remains to be done—and paid for—after the first deployment?
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.
Reliability reviews, model changes, support, incident response, new connectors and knowledge transfer can justify ongoing work. A recurring invoice also commits someone to keep doing that work. Unlimited support, low retention or unpriced changes can consume the entire margin.
These examples deliberately include software startup costs and a downside for every play. A service fee buys defined coverage. A software subscription buys the product’s stated capability; implementation and provider usage need explicit treatment.
Assurance earns by operating within a real capacity limit
A deployed workflow buys scheduled evaluation, operating review and a limited change budget. The scope is not unlimited incident coverage.
Buyer / budget holder
The workflow’s operating owner
Who pays this invoice
The customer pays the monthly operating fee
Ledger boundary
Intent as the operating service supplier
Period covered
One month of a bounded operating service
Customer value: An owner, review cadence and defined escalation path make changes and failures visible. The service does not guarantee that every failure is preventable.
$6,000 in illustrative fees minus $4,850 in listed costs leaves $1,150 before central overhead and tax. This is not company profit or personal income.
Fees less listed costs
$1,150
After a proposed $300 cash designation
$850
Reserve is not an expense or an extra payment to a participant. A negative remainder means this model cannot fund that reserve from its contribution. Fees do not establish accounting recognition or cash collection.
Show the full fee and cost ledger
Illustrative fees / billings within this business boundary
Scope
Quantity × rate
Amount
Bounded operating service
1 month × $6,000
$6,000
Who could earn what, for which work, and when payment is due
Work / recipient
Quantity × rate
Business invoice / cost
Earned when
Payment trigger
Scheduled evaluations Assurance business
16 hours × $100
$1,600
Scheduled evaluation evidence delivered
Monthly invoice
Operations and escalation Operations business
12 hours × $100
$1,200
Defined operating duties performed
Monthly invoice
Maintenance capacity Engineering business
8 hours × $125
$1,000
Authorized maintenance performed
Monthly invoice
Adoption and account service Account service business
4 hours × $125
$500
Current service duties performed
Monthly invoice
Monitoring and model resources Vendors
1 month × $400
$400
Service consumed
Vendor cycle
Service administration Administration function
2 hours × $75
$150
Administration performed
As incurred
An unpriced incident consumes extra engineering
A recurring invoice is not recurring profit when incident effort is unbounded.
$6,000 in illustrative fees minus $7,350 in listed costs leaves -$1,350 before central overhead and tax. This is a loss under these assumptions.
Fees less listed costs
-$1,350
After a proposed $300 cash designation
-$1,650
Reserve is not an expense or an extra payment to a participant. A negative remainder means this model cannot fund that reserve from its contribution. Fees do not establish accounting recognition or cash collection.
Show the full fee and cost ledger
Illustrative fees / billings within this business boundary
Scope
Quantity × rate
Amount
Bounded operating service
1 month × $6,000
$6,000
Who could earn what, for which work, and when payment is due
Work / recipient
Quantity × rate
Business invoice / cost
Earned when
Payment trigger
Scheduled evaluations Assurance business
16 hours × $100
$1,600
Scheduled evaluation evidence delivered
Monthly invoice
Operations and escalation Operations business
12 hours × $100
$1,200
Defined operating duties performed
Monthly invoice
Maintenance capacity Engineering business
28 hours × $125
$3,500
Authorized maintenance performed
Monthly invoice
Adoption and account service Account service business
4 hours × $125
$500
Current service duties performed
Monthly invoice
Monitoring and model resources Vendors
1 month × $400
$400
Service consumed
Vendor cycle
Service administration Administration function
2 hours × $75
$150
Administration performed
As incurred
How each participant benefits—and what they owe
Participant
Potential benefit
Condition / responsibility
Operator and reviewer
Earn for reserved and delivered operating capacity.
Named service window, workload and review obligations.
Current account steward
Can earn for actual adoption and service work.
A current role schedule; historic introduction alone does not earn an automatic renewal share.
Contract route, payment terms and assumptions
Accepted deployment → separate monthly service scope → evidence review → renew, resize or end.
The service window, included work and escalation limits are agreed before renewal.
Changes beyond capacity are separately priced or deferred, rather than silently promised.
No 24/7 coverage, uptime promise or unlimited support is implied.
The budget includes current account service but no permanent referral percentage.
Evidence behind this mechanism
Every amount above is a constructed teaching input. Sources explain mechanisms and constraints; they do not supply these prices, prove demand or establish Intent’s eligibility.
This scenario is a proposed commercial design, not an observed industry benchmark.
Open skills; paid implementation and maintenance
The published code remains available under its license. Teams pay for installation, a verified configuration and a bounded maintenance service.
Buyer / budget holder
Engineering teams adopting reusable agent workflows
Who pays this invoice
Three teams buy onboarding and support
Ledger boundary
Intent as an implementation and support supplier
Period covered
Three months, three customer teams
Customer value: A supported setup and a route to operating it independently. Paying for support does not retroactively restrict rights already granted by the code license.
$9,000 in illustrative fees minus $8,160 in listed costs leaves $840 before central overhead and tax. This is not company profit or personal income.
Fees less listed costs
$840
After a proposed $300 cash designation
$540
Reserve is not an expense or an extra payment to a participant. A negative remainder means this model cannot fund that reserve from its contribution. Fees do not establish accounting recognition or cash collection.
Show the full fee and cost ledger
Illustrative fees / billings within this business boundary
Scope
Quantity × rate
Amount
Team onboarding
3 teams × $1,500
$4,500
Bounded support
9 team-months × $500
$4,500
Who could earn what, for which work, and when payment is due
Work / recipient
Quantity × rate
Business invoice / cost
Earned when
Payment trigger
Supportable release preparation Maintainer business
$9,000 in illustrative fees minus $10,080 in listed costs leaves -$1,080 before central overhead and tax. This is a loss under these assumptions.
Fees less listed costs
-$1,080
After a proposed $300 cash designation
-$1,380
Reserve is not an expense or an extra payment to a participant. A negative remainder means this model cannot fund that reserve from its contribution. Fees do not establish accounting recognition or cash collection.
Show the full fee and cost ledger
Illustrative fees / billings within this business boundary
Scope
Quantity × rate
Amount
Team onboarding
3 teams × $1,500
$4,500
Bounded support
9 team-months × $500
$4,500
Who could earn what, for which work, and when payment is due
Work / recipient
Quantity × rate
Business invoice / cost
Earned when
Payment trigger
Supportable release preparation Maintainer business
Can earn for maintenance and customer-specific work.
Mutually agreed rights and service obligations; publishing code does not automatically create royalties.
Customer teams
Can use the licensed code and choose whether ongoing help is useful.
The paid service scope is separate from the open-source license.
Contract route, payment terms and assumptions
Public licensed tool → optional paid onboarding → scoped maintenance → renew or self-operate.
Onboarding is accepted per team; support has a defined period and capacity.
A sponsor, license buyer, reseller and support customer are different commercial relationships. None is assumed merely from a download.
The 3% collection allowance is a round planning input, not a quoted platform fee.
Downloads, stars and sponsorship eligibility are not paying customers.
A maintainer’s pre-existing code and rights remain theirs unless a separate agreement says otherwise.
Evidence behind this mechanism
Every amount above is a constructed teaching input. Sources explain mechanisms and constraints; they do not supply these prices, prove demand or establish Intent’s eligibility.
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.
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.
A subscription must also recover its first build
A small workflow product sells subscriptions and onboarding. Its first-quarter ledger includes the initial build and customer acquisition, so a recurring fee does not hide startup losses.
Buyer / budget holder
Ten teams with the same narrow workflow need
Who pays this invoice
Each customer pays onboarding and monthly subscriptions
Ledger boundary
Intent as the fictional product operator
Period covered
First 90 days; ten paying customers present from day one
Customer value: A maintained workflow with a documented scope and operating owner. Adoption is useful only if the actual workflow need is met.
$11,970 in illustrative fees minus $14,309.1 in listed costs leaves -$2,339.1 before central overhead and tax. This is a loss under these assumptions.
Fees less listed costs
-$2,339.1
After a proposed $0 cash designation
-$2,339.1
Reserve is not an expense or an extra payment to a participant. A negative remainder means this model cannot fund that reserve from its contribution. Fees do not establish accounting recognition or cash collection.
This model needs 15 customers to cover the included fixed costs over its stated horizon.
Assumes each customer contributes the same three-month receipts and variable cost from day one, with fixed build/hosting/maintenance unchanged. Capacity limits and step costs can invalidate scaling.
Show the full fee and cost ledger
Illustrative fees / billings within this business boundary
Scope
Quantity × rate
Amount
Subscription
30 customer-months × $299
$8,970
Onboarding
10 customers × $300
$3,000
Who could earn what, for which work, and when payment is due
Work / recipient
Quantity × rate
Business invoice / cost
Earned when
Payment trigger
Initial product build Product engineering business
60 hours × $100
$6,000
Initial scope accepted
Build milestones
Acquiring the first customer cohort Acquisition function
Only five customers buy; the build is already committed
The build, shared hosting and maintenance stay committed while customer-dependent receipts shrink. The smaller cohort still assumes the same acquisition cost per won customer.
$5,985 in illustrative fees minus $10,904.55 in listed costs leaves -$4,919.55 before central overhead and tax. This is a loss under these assumptions.
Fees less listed costs
-$4,919.55
After a proposed $0 cash designation
-$4,919.55
Reserve is not an expense or an extra payment to a participant. A negative remainder means this model cannot fund that reserve from its contribution. Fees do not establish accounting recognition or cash collection.
This model needs 15 customers to cover the included fixed costs over its stated horizon.
Assumes each customer contributes the same three-month receipts and variable cost from day one, with fixed build/hosting/maintenance unchanged. Capacity limits and step costs can invalidate scaling.
Show the full fee and cost ledger
Illustrative fees / billings within this business boundary
Scope
Quantity × rate
Amount
Subscription
15 customer-months × $299
$4,485
Onboarding
5 customers × $300
$1,500
Who could earn what, for which work, and when payment is due
Work / recipient
Quantity × rate
Business invoice / cost
Earned when
Payment trigger
Initial product build Product engineering business
60 hours × $100
$6,000
Initial scope accepted
Build milestones
Acquiring the first customer cohort Acquisition function
Earn for build, acquisition, onboarding and operations.
Their agreements must be funded before uncertain subscription growth arrives.
Product operator
May recover development cost as sufficient customers stay and pay.
Acquisition, support and infrastructure costs must stay within capacity; no growth guarantee.
Contract route, payment terms and assumptions
Validated repeat need → product build → customer onboarding → subscription operation → retention or cancellation.
The example assumes the entire cohort pays for all three months from day one; it is not an acquisition forecast.
Subscription cancellation, refunds and data export need explicit terms. Annual cash prepayment would not erase future operating obligations.
All customer, price and cost inputs are fictional. No current Intent product revenue is represented.
The 3% processing allowance is a planning input, not a platform quote.
Break-even includes the initial build; it excludes central company overhead, taxes, financing and any extra capacity hired beyond the modeled scale.
Evidence behind this mechanism
Every amount above is a constructed teaching input. Sources explain mechanisms and constraints; they do not supply these prices, prove demand or establish Intent’s eligibility.
This scenario is a proposed commercial design, not an observed industry benchmark.
A hosted workflow has suppliers even when it uses AI
The customer pays for an operated workflow. Model consumption, licensed data, infrastructure and human support remain real costs.
Buyer / budget holder
A business that needs the workflow operated
Who pays this invoice
The customer pays the operating supplier
Ledger boundary
Intent as the fictional workflow operator
Period covered
One month of a bounded hosted workflow
Customer value: A usable workflow with a clear operator, budget boundary and usage policy. Model output volume is not itself evidence of useful outcomes.
$4,000 in illustrative fees minus $2,570 in listed costs leaves $1,430 before central overhead and tax. This is not company profit or personal income.
Fees less listed costs
$1,430
After a proposed $200 cash designation
$1,230
Reserve is not an expense or an extra payment to a participant. A negative remainder means this model cannot fund that reserve from its contribution. Fees do not establish accounting recognition or cash collection.
Show the full fee and cost ledger
Illustrative fees / billings within this business boundary
Scope
Quantity × rate
Amount
Bounded hosted workflow
1 month × $4,000
$4,000
Who could earn what, for which work, and when payment is due
$4,000 in illustrative fees minus $4,130 in listed costs leaves -$130 before central overhead and tax. This is a loss under these assumptions.
Fees less listed costs
-$130
After a proposed $200 cash designation
-$330
Reserve is not an expense or an extra payment to a participant. A negative remainder means this model cannot fund that reserve from its contribution. Fees do not establish accounting recognition or cash collection.
Show the full fee and cost ledger
Illustrative fees / billings within this business boundary
Scope
Quantity × rate
Amount
Bounded hosted workflow
1 month × $4,000
$4,000
Who could earn what, for which work, and when payment is due
Receive payment for their actual contracted products or metered use.
Consumption and license terms, not a share of all customer value.
Operator and customer
Can agree a useful service with a transparent usage boundary.
Retried work, support demand, data rights and spend caps must be priced and monitored.
Contract route, payment terms and assumptions
Customer operating scope → human operations plus authorized vendors → usage review → resize or renew.
Vendor invoices can fall due before customer collection. A customer subscription is not an unlimited vendor budget.
Operating a service is different from reselling a vendor’s product; any resale or white-label rights need actual authorization.
The request cost and 3% collection allowance are fictional blended planning inputs, not named-provider prices.
No free credit, subsidy or sponsorship is assumed. Credits would reduce an eligible vendor bill, not become cash available for every expense.
Evidence behind this mechanism
Every amount above is a constructed teaching input. Sources explain mechanisms and constraints; they do not supply these prices, prove demand or establish Intent’s eligibility.
Separates funding approval, cash claims, invoices and credits. Eligibility and program terms apply; the customer-paid discovery example is not an AWS award.
Distinguishes approved resale from ordinary vendor consumption. This does not authorize resale of an arbitrary model, API, dataset or contributor’s software.
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.
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.
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.
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.