In Lesson 4, you learned how to choose between Cowork and Frontier based on your organisational context. Now the question shifts from "which platform?" to "how does this agent pay for itself?"
Before you deploy a domain agent, you need to understand how it creates value and how that value is captured. Technology without a value model is a cost centre. It gets funded once, questioned twice, and cut in the next budget cycle. The agents that survive are the ones whose value is visible, measurable, and tied to a model that the organisation understands.
The enterprise agentic landscape has converged on four monetisation models. Each fits a different pattern of value delivery. Choosing the right model is not a minor detail -- it determines whether your agent deployment is seen as an investment or an expense.
Deploy the agent. It produces a measurable outcome. Capture a percentage.
The success fee model is the most naturally compelling because value is directly visible: the agent did something, and that something produced a result you can measure. But it requires one critical precondition -- a clean attribution methodology agreed before deployment. Without pre-agreed attribution, you cannot determine which outcomes the agent caused versus outcomes that would have happened regardless.
Domain
Typical Fee Structure
Why It Fits
Sales
$3-8 per qualified lead, 0.5-1.5% of attributed closed revenue
Leads and revenue are directly measurable
Finance
1.5-2.5% of attributed savings identified
Cost reduction is quantifiable against baseline
Supply Chain
0.5-1% of attributed procurement savings
Spend reduction is tracked against purchase history
The word "attributed" is doing heavy lifting. Before deploying a success-fee agent, you must agree on:
Get attribution wrong, and the model collapses into argument. Get it right, and it is the most powerful justification for continued investment.
Recurring fee regardless of value in a given period. Per-seat, per-team, or enterprise-wide.
The subscription model works when value is continuous but difficult to attribute to specific outcomes. The agent helps every day, but you cannot point to one moment and say "that generated $X."
Domain
Why Subscription Fits
Typical Range
HR
Continuous value across recruiting, onboarding, policy questions -- hard to tie to specific revenue
Team-level: $800-$2,500/month
Product Management
Diffuse, ongoing value across discovery, planning, and stakeholder communication -- hard to tie to specific revenue
Team-level: $2,000-$8,000/month
Operations
Ongoing process documentation and compliance value that prevents failures but cannot be attributed to specific savings
Department: $1,500-$5,000/month
Subscription's weakness is that it does not self-justify. A success-fee agent proves its value every time it generates a fee. A subscription agent requires active measurement to demonstrate that the recurring cost is worth paying.
Without deliberate value tracking, subscriptions become line items that finance questions during budget reviews. The fix: build measurement into the deployment from day one. Track time saved, errors prevented, queries handled -- whatever makes the value visible even when it cannot be attributed to specific revenue.
High-stakes, regulated, or proprietary domains where security and compliance reviews are expected and the pricing reflects the risk profile.
License agreements are annual contracts with significant upfront negotiation. They fit domains where the consequences of agent failure are severe enough that both parties need contractual protections.
Domain
Typical Annual Range
Why License Fits
Legal
$40,000-$150,000/year
Regulatory compliance, attorney-client privilege, malpractice risk
Banking / Finance
$60,000-$200,000/year
IFRS 9, Basel III/IV compliance, AML/KYC regulatory exposure
CA/CPA Practice
$40,000-$120,000/year
Audit standards, tax compliance, professional liability
Deploying under a license model means passing through:
This procurement process takes months, not weeks. It is appropriate for Level 3+ maturity organisations (you will learn about maturity levels in Lesson 6) that have the governance infrastructure to manage these reviews.
Publish your SKILL.md as a reusable plugin. Other teams or organisations subscribe.
The marketplace model turns your domain expertise into a product. You write a SKILL.md that encodes general best practices in your domain -- not your organisation's proprietary knowledge, but the knowledge that any practitioner in your field would benefit from.
This is the critical boundary. Your company's internal compliance procedures, client lists, and proprietary methods are not marketplace material. But your knowledge of how to structure a regulatory review, how to approach building code analysis, or how to qualify a sales lead in your industry -- that general domain expertise is publishable and valuable.
Model
Value Pattern
When to Use
Key Risk
Success Fee
Measurable, attributable outcomes
Sales, finance, cost reduction
Attribution disputes
Subscription
Continuous, diffuse value
HR, product management, operations
Fails to self-justify
License
High-stakes, regulated domains
Legal, banking, CA/CPA practice
Lengthy procurement
Marketplace
Reusable domain expertise
General best practices
IP boundary confusion
Use these prompts in Anthropic Cowork or your preferred AI assistant to explore these concepts further.
What you're learning: You are practising model selection against your own domain. The AI forces you to evaluate each model against your specific value delivery pattern, not just pick the first one that sounds reasonable.
What you're learning: You are evaluating whether a single model fits or whether a hybrid approach is needed. Real deployments often require blending models, and this prompt teaches you to think about trade-offs rather than defaulting to one answer.
What you're learning: You are grounding the abstract models in current market reality. Knowing what competitors charge and how they structure pricing gives you a reference point for your own deployment decisions.
Domain agents create value in four distinct patterns, each requiring a different monetisation model. Success Fee captures a percentage of measurable outcomes (sales leads, cost savings). Subscription charges a recurring fee for continuous but hard-to-attribute value (HR, documentation). License provides annual contracts for high-stakes, regulated domains (legal, healthcare). Marketplace turns domain expertise into reusable SKILL.md plugins. Choosing the wrong model is a deployment failure, not a minor detail -- it determines whether the agent is seen as an investment or an expense.
📋Quick Reference
Access condensed key takeaways and quick reference notes for efficient review.
Free forever. No credit card required.
Ask