Your Product's Cost Structure

James pulled up the comparison table from Module 9.4, Chapter 1. The number that kept pulling his attention was not the $12,300 that Architecture 1 cost. It was the $50-70 on the other side. "That number is suspiciously round," he said. "What is actually in it? I want to see every line."

Emma opened a spreadsheet. "Good instinct. A total without line items is a guess. Let me show you what the operator actually pays each month to keep TutorClaw running."

James leaned forward. This was the part he understood from years in operations: you cannot control costs you cannot see.

---

You are doing exactly what James is doing. You have a product that costs $50-70 per month to run. Now you need to see exactly where each dollar goes, what it buys, and which services carry the load.

The Operating Costs Table

Here is every component that makes up TutorClaw's monthly infrastructure bill:

Look at the three $0 lines. LLM tokens cost nothing because of the Great Inversion (Module 9.4, Chapter 1). Storage and Gating cost nothing because Cloudflare's free tiers are massive compared to TutorClaw's 10 MB of text content.

Map It to Module 9.3

Every row in that table maps to a component you designed in Module 9.3. The production version simply swaps local mocks for cloud services:

• MCP Server (VPS): Replaces localhost. Same 9 tools, same transport.
• Content Storage (R2): Replaces content/chapters/. get_chapter_content reads from R2 instead of disk.
• Content Gating (Workers): Replaces check_tier(). Same logic, executed at the edge.
• Learner Database: Replaces learners.json. Same data, robust SQL.
• Code Sandbox (Docker): Replaces mock subprocess with real isolation. Same tool interface.
• Payments (Stripe): The same integration you built in the final chapters of Module 9.3.

The key insight: production is a swap of implementation, not a redesign of logic. Your tests still pass because the tool contracts are unchanged.

The Revenue Model

Costs are one side of the equation. Here is the other:

Notice the Free tier includes an offline shim skill. The upgrade paths are logical: more chapters, more exchanges, and active code execution.

How the Monetization Gate Works

The gate that enforces these tiers lives inside the MCP server, not in the learner's OpenClaw:

1. get_learner_state returns exchanges_remaining and tier.
2. get_chapter_content returns an upgrade prompt if the user is out of tier.
3. get_upgrade_url returns the Stripe checkout link.

This is server-side enforcement. Even if a learner modified their local shim skill, the MCP server would still reject the tool call.

Unit Economics at Scale

With 16,000 learners split across tiers (75% free, 19% paid, 6% premium):

Infrastructure-only margin is an incredible 99.5%. However, Stripe's flat fees ($0.30 per tx) can consume $1,200/mo for 4,000 subscribers. Accounting for processing, the gross margin is ~89%.

Try With AI

Exercise 1: Fixed vs. Variable Costs

Exercise 2: Break-Even at Different Tiers

Exercise 3: Cost Structure for a Different Product

---

James studied the tables. "Forty users. The entire infrastructure cost is covered by forty people paying less than two dollars a month. In my old warehouse job, the electricity bill alone was more than this."

Emma nodded. "VPS is your electricity. The database is your water meter. Stripe is your credit card terminal fee. And the LLM is like telling your customers to bring their own power tools."