Founders
How to account for human delivery work when modeling AI developer APIs costs
AI developer APIs: Human delivery work belongs in the operating model even when founders perform it without a salary allocation.
Human delivery work belongs in the operating model even when founders perform it without a salary allocation. Track time spent reviewing outputs, configuring customers, handling exceptions, and repairing failures. Separate recurring delivery from one-time product development.
Start with the decision
Define work categories before logging effort. Use a consistent internal costing convention and show its limitations. Compare customers that need different levels of assistance rather than averaging away expensive exceptions.
The illustrative scenario
This is an educational workbook. The company or fund and all numerical inputs below are fictional. They are not ADIN results, customer claims, market benchmarks, or a forecast.
The fictional API transforms uploaded documents into structured fields for a developer integrating an operations system. The developer controls implementation, but an operations owner decides whether the extracted output is usable.
A successful HTTP response does not prove that a field is correct. Changes in document layout, retries, and ambiguous inputs need visible behavior and a defined fallback.
A monthly cost bridge with visible assumptions
For this exercise, assume 2300 completed units in a month, 4 minutes of human work per unit, and a fictional labor rate of $30 per hour. The labor rate, service cost, and revenue are invented inputs. They are not current vendor prices, customer results, or a suggested commercial offer. A successful HTTP response does not prove that a field is correct. Changes in document layout, retries, and ambiguous inputs need visible behavior and a defined fallback.
The bridge subtracts only the costs shown. The remainder is not an accounting gross margin or profit figure: other expenses, taxes, timing differences, and classifications are outside this simplified model. A negative result is useful information about the assumptions, rather than evidence that an entire product category cannot work.
Now change one input. If the workflow requires twice the review time, the human-work line doubles even when the provider's unit price stays constant. If volume rises, distinguish a genuinely fixed cost from a cost that will step up. Reconcile the model with observed delivery logs before using it to support a pricing or fundraising claim.
| Item | Illustration |
|---|---|
| Completed workflow units | 2300 |
| Assumed revenue for this month | $3,200.00 |
| Variable service cost | 2300 × $0.04 = $92.00 |
| Listed fixed delivery cost | $780.00 |
| Human work at an assumed $30/hour | $4,600.00 |
| Remainder after these listed costs | -$2,272.00 |
Use this worksheet
Answer the questions with a source, date, owner, and next action. Mark an unknown as unknown. Use public or permissioned information and involve a qualified specialist when a question requires expertise beyond the team’s competence.
- What work is recurring?
- Who performs it?
- How is time recorded?
- What costing convention is used?
- Which work could disappear with a product change?
Questions specific to this scenario
- What constitutes a valid record?
- How are retries identified?
- Who owns changes to the output contract?
Use versioned input fixtures, field-level expected outputs, retry logs, and integration support requests. Keep test data provenance and access permissions attached to the examples.
A concrete next test
Trace a successful record, a malformed input, and a retry through the consuming application. Ask the integrator where an error becomes visible and who can repair it. Include the downstream validation step when defining completion and measuring cost.
Interpret the result
A time log can reveal that apparent software scale depends on hidden service work. It does not by itself determine accounting treatment. Have the relevant finance professional review formal margin and reporting definitions.
Compare a successfully consumed record with the current integration. Include retries, validation failures, and support time in both the quality and cost discussion.
Sources and method
These primary resources provide background for the concepts. The fictional scenario, calculations, and worksheet are ADIN educational examples; the sources do not report or validate those invented results. Reviewed October 11, 2026.