CSE Roadmap

Common tier · about 3 hours · 12 parts

Part 9 of 12 · 2 min read

Mistakes that quietly turn margin negative

Common mistakes, and what the example does not do.

Mistakes that quietly turn margin negative

  • Pricing on cost per call or per token and ignoring failures.
  • Flat seat pricing with unbounded usage.
  • Averaging across customers and missing the heavy tail.
  • Using stale vendor list prices; they change often, so read the current price page.
  • Not counting retries, tool costs, or failures in cost.
  • Outcome pricing without a definition of the outcome.
  • No per-customer margin tracking.
  • Optimising for escalation rate because it lowers the vendor's cost.
  • Copying a cost figure without recomputing it.
  • Setting a price once and never revisiting it.

What the example does not do

About this example What the example does not do
  • Every input is assumed. There is no real traffic, price list or customer data.
  • Customers are random draws, not a real distribution; real usage has seasonality, growth and churn.
  • No demand model: the example does not model willingness to pay, discounting, negotiation or how price changes usage.
  • Complexity affects cost and resolution through one invented exponent (-0.3).
  • Failure credits and the human task cost are single numbers; reality varies by customer and contract.
  • No fixed costs: engineering, evaluation, compliance, sales and support are excluded, so gross margin overstates profit.
  • No competitor, tax, currency or contract terms.
  • Optional real experiment: export a month of real traces and billing, compute cost per task, per resolved task and margin per customer, and compare with this module's model to see which assumption was most wrong.

Check yourself

Why is cost per call the wrong unit?

Show answer

The unit is a task, and failed or escalated tasks still cost money. Cost per resolved task is cost per task divided by the share the agent resolved.

For the curious Resolution rate moves the margin more than token price

A 20 percent drop in the agent resolution rate cut the blended margin by 27.5 points in the one-at-a-time test. Vendor cost per agent-resolved task was $1.50 at 35 percent resolution and $0.10 at 75. With each price list tuned to a 60 percent margin on 200 simulated customers, per seat put 10 percent of customers at a negative margin and per task 1.5 percent. Every input is assumed.

What you will use daily at work

Practice What it looks like
Instrument cost per task from day one Tokens, tools, infrastructure and failure credits.
Define resolved with the customer Outcome pricing needs a shared definition.
Price between floor and ceiling Floor is cost over (1 minus margin); ceiling is customer value.
Re-run the numbers when inputs move Model prices, caching and resolution rate.