Founders
How to present pilot revenue separately from recurring revenue for AI voice agents
AI voice agents: Present pilot revenue and recurring revenue with explicit definitions and periods.
Present pilot revenue and recurring revenue with explicit definitions and periods. A one-time payment can validate willingness to fund a test without establishing a repeatable subscription. Keep recognized revenue, cash collected, bookings, and contract value distinguishable.
Start with the decision
Build a bridge from the actual agreements and invoices to each reported measure. Mark cancellations, discounts, services, and conditional renewals. Have the finance owner review formal accounting and metric definitions before using them in fundraising materials.
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 product handles appointment requests for a multi-location service business. A caller may change their request mid-conversation, and the scheduling system is the final record of an available slot.
A short call is not useful if it books the wrong appointment. Separate successful scheduling from hangups, transfers, and calls where the caller never confirmed the details.
Turn the scenario into an evidence decision
Consider a review of AI voice agents in which a confident explanation arrives before the supporting records. Start with the first question in the table. Write down what an answer would change: the next interview, the experiment's scope, a request for specialist review, or a decision to wait. A question without a consequence can produce a longer document while adding little understanding.
Next, inspect the record named in the table and record its date, owner, permission boundary, and limitations. Collect permissioned test calls, interruption cases, confirmation records, and failed booking attempts. Keep different languages and noisy environments visible in the sample. If the record contradicts the explanation, preserve both accounts and ask which definition, period, or workflow differs. Do not silently select the version that makes the opportunity look strongest.
Finish with a conditional statement: if the specified evidence supports the claim under these conditions, take the named next step; otherwise investigate the unresolved question. A precise bridge lets investors assess commercial progress without guessing. Avoid annualizing a short pilot into a recurring run rate unless the definition and limitations are clearly stated and supported. This worked exercise is about the decision process. It does not assert that a fictional company has met a real diligence standard or that a template can authorize an investment.
| Item | Illustration |
|---|---|
| Decision question | What period is reported? |
| Case-specific constraint | A short call is not useful if it books the wrong appointment. Separate successful scheduling from hangups, transfers, and calls where the caller never confirmed the details. |
| Record to inspect | Collect permissioned test calls, interruption cases, confirmation records, and failed booking attempts. Keep different languages and noisy environments visible in the sample. |
| Comparison to preserve | Compare completed, correct bookings with the existing phone process. Include repeat calls and staff repair time instead of measuring call duration alone. |
| Unresolved case question | Who confirms the booking? |
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 period is reported?
- Which payment is one-time?
- What recurs under contract?
- What is collected versus recognized?
- Who reviewed the definition?
Questions specific to this scenario
- Who confirms the booking?
- What happens when a caller interrupts?
- How is a failed transfer recovered?
Collect permissioned test calls, interruption cases, confirmation records, and failed booking attempts. Keep different languages and noisy environments visible in the sample.
A concrete next test
Run permissioned tests with an interruption, an unavailable appointment, and a failed transfer. Ask the scheduling owner to verify the final records, then inspect what the caller was told. A correct transcript alone does not establish a correct booking.
Interpret the result
A precise bridge lets investors assess commercial progress without guessing. Avoid annualizing a short pilot into a recurring run rate unless the definition and limitations are clearly stated and supported.
Compare completed, correct bookings with the existing phone process. Include repeat calls and staff repair time instead of measuring call duration alone.
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.