The report takes seconds to generate. You spend the next twenty minutes checking the figures, replacing an awkward paragraph, and fixing the export before the customer can use it.
That time belongs in your delivery costs. So do the failed attempts, the support conversation, and the work required to get a new customer started. If you leave them out, you can end up selling more of a service that pays you poorly.
Our post on earning trust through delivery follows the customer's experience after a purchase. The same work deserves a place in your operating model.
Follow one customer through a full month
Consider a fictional service that prepares client reports for small agencies. It charges $200 per account each month. The following figures are illustrative assumptions, not customer results or industry benchmarks.
Model usage costs $18, hosting costs $12, and payment fees cost $6 per account. Looking only at those expenses leaves $164 from the subscription.
Now include the delivery labor. Assume report review costs $90 and customer support costs $24 per account, using allocated labor costs. Total delivery cost is $150, leaving $50 of gross profit, or 25% of the $200 price, under this stated cost definition.
The customer might be delighted with the finished reports. You still need to decide whether the remaining $50 can support acquisition and the rest of the company. Gross profit must help cover product development, administration, and other expenses outside that delivery calculation.
The unit economics guide walks through these distinctions. Keep your definitions consistent and reconcile the figures with your accounting records.
Record the corrections you keep making
For one reporting cycle, write down what happens between the first generated draft and the customer's usable output. Include the person doing the work and the time required.
You may find repeated problems with source data, unsupported claims, formatting, or exports. Group similar corrections so you can see which changes would remove recurring work. A better input form might save more review time than a longer generation prompt.
Keep unsuccessful attempts in the record. A completed report that required five generations used more compute and attention than one that worked the first time. The customer sees the final result; your costs include the attempts that came before it.
Founder labor can be easy to miss because no separate invoice arrives. Estimate what it would cost to have a capable person perform the task, and label that estimate. Compare it with actual paid delivery costs as the team grows.
Test the customer who uses the product heavily
An average account can hide an expensive one. In the fictional example, increasing model usage cost from $18 to $60 while leaving the other assumptions unchanged raises delivery cost to $192. The $200 subscription would leave $8 before acquisition and the company's remaining expenses.
Check whether your pricing package gives customers a sensible limit, a usage charge, or a service tier that fits the work. Explain those terms before purchase. A customer should be able to understand what changes their bill.
Also check what happens during onboarding. A one-time setup effort may be worthwhile for an account that stays, but it creates an immediate cash and capacity need. Record it separately from recurring monthly work so you can see both.
Our pricing guide includes a worksheet for comparing packages with delivery costs. Test normal and heavy usage before calling a plan unlimited.
Improve the expensive step without weakening the result
Some manual work is worth doing while you learn. Reviewing outputs can reveal the failure modes a customer would otherwise discover. Decide which checks the product can perform reliably, which require a person, and how you will verify a change.
Measure the finished result after reducing review time. Track customer corrections, failed deliveries, refunds, and support requests alongside the cost saving. A lower labor bill can become expensive if customers receive work they cannot trust.
You may decide to automate a repeated formatting fix, narrow the kinds of input you accept, or charge separately for human review. Another option is to keep a service-heavy offer and price it accordingly. Choose the model you can deliver consistently.
Before increasing acquisition spending, compare the gross profit from recent customers with what it cost to win them. The CAC and payback guide explains why recovery depends on gross profit as well as revenue.
This week, choose one account and follow its work from setup through delivery and support. Record the compute, retries, labor, and corrections. Use that record to decide which cost to reduce and which promise to revise before selling the next account.