The Follow-Up Meeting
Leo returns with updated projections and answers to the investors’ earlier concerns. David and Mia discuss the remaining conditions, and the group works toward a clear next step without treating a handshake as a signed deal.
Dialogue12

Thanks for making time to meet again. I’ve revised the projections to separate contracted revenue from pipeline, and I’ve added a downside case that assumes slower customer conversion.
That distinction helps. In the downside case, though, you still reach break-even in month twenty-four. What has to go right for that timing to hold?
We’d need to keep hiring tightly tied to customer growth and convert roughly a third of qualified pilots. If either assumption slips, break-even moves back by at least two quarters.
And the new enterprise contracts? Are those signed, or are we still looking at letters of intent that can be withdrawn without much consequence?
Two are signed, with implementation schedules attached. The third is still a letter of intent, so I’ve excluded it from contracted revenue and treated it as upside rather than a base assumption.
Good. On the data-security review, our counsel wants an independent assessment before the next financing milestone. Can your team complete that without diverting product engineers for months?
Yes. We’ve scoped an external assessment, and the cost is already in the updated budget. Our engineers would support the review, but the assessor would lead it and report findings directly.
That addresses the process, but not the threshold. We’d need any critical findings resolved before funds are released, with a reasonable cure period for less serious issues.
That’s workable if “critical” is defined against an agreed framework and the cure period reflects the actual remediation effort. I’d also want the release condition applied consistently to both sides.
Fair. We can circulate draft language with objective criteria. We’re aligned on the business case, subject to diligence, the security review, and agreement on the final documents.
I appreciate that. I’ll send the revised model and the security scope tonight. Just to be precise, we’re discussing a possible investment, not treating today’s agreement as binding.
Exactly. If the documents reflect what we’ve discussed and diligence doesn’t uncover a material surprise, we’ll be in a position to make a decision next week.
Vocabulary8
- downside case
A financial forecast that shows what could happen under less favorable conditions. Here, it assumes customers convert more slowly.
- break-even
The point when a business’s revenue covers its costs. The investors ask what assumptions support reaching that point in month twenty-four.
- qualified pilots
Trial projects with potential customers who meet specific criteria. Converting them means turning those trials into paying business.
- letters of intent
Documents that express an intention to make a deal but may not create a firm commitment. The dialogue distinguishes them from signed contracts.
- excluded it from contracted revenue
Left an item out of revenue counted as secured by signed agreements. This phrase is useful when explaining cautious financial projections.
- cure period
An agreed amount of time to fix a problem or breach. Here, it applies to less serious security findings before funds are released.
- objective criteria
Clear, measurable standards that do not depend only on personal judgment. They can make contract conditions more predictable and fair.
- material surprise
An important, unexpected finding that could affect a decision. In this context, it refers to a significant issue discovered during due diligence.
Key Sentences8
- 1
I’ve revised the projections to separate contracted revenue from pipeline, and I’ve added a downside case that assumes slower customer conversion.
This sentence explains how a forecast has been made more transparent and cautious. Reuse the structure to describe specific changes you have made to a plan or report.
- 2
What has to go right for that timing to hold?
A concise way to ask which assumptions are necessary for a forecast or deadline to remain realistic. Use it to probe the conditions behind someone’s estimate.
- 3
If either assumption slips, break-even moves back by at least two quarters.
This clearly connects a change in assumptions to its impact on a timeline. Reuse the pattern “If [condition] slips, [result] moves back” when discussing risks.
- 4
The third is still a letter of intent, so I’ve excluded it from contracted revenue and treated it as upside rather than a base assumption.
This sentence carefully distinguishes a possible deal from revenue that is firmly secured. It is useful when explaining why a projection does not rely on uncertain commitments.
- 5
That’s workable if “critical” is defined against an agreed framework and the cure period reflects the actual remediation effort.
This accepts a proposal while setting conditions for making it reasonable. Reuse “That’s workable if…” to negotiate terms without rejecting the idea outright.
- 6
We’re aligned on the business case, subject to diligence, the security review, and agreement on the final documents.
This summarizes shared understanding while making clear that important conditions remain. “Subject to” is useful for stating that an agreement depends on specific requirements.
- 7
Just to be precise, we’re discussing a possible investment, not treating today’s agreement as binding.
This politely clarifies that a discussion has not created a legal commitment. Use “Just to be precise” to correct a possible misunderstanding in a professional setting.
- 8
If the documents reflect what we’ve discussed and diligence doesn’t uncover a material surprise, we’ll be in a position to make a decision next week.
This gives a clear next step while identifying the conditions that must be met first. Reuse the structure “If [conditions], we’ll be in a position to [action]” when describing a conditional plan.