The Revenue Assumptions Nobody Has Checked
By Rich Garcia, Co-founder of Mayetik · June 27, 2026 · 8 min read
The annual plan review is in its second hour. The revenue model has a 24% conversion rate from qualified pipeline to close — the trailing twelve-month average. The CFO asks where the assumption comes from. Sales says that's what they've been running at. She asks what buyers are actually saying about how they make this decision — what's driving the rate. The room offers theories. Two new competitors entered the category last quarter. Buyers are involving more stakeholders. The ICP may be shifting. The sales leader describes what reps are hearing. The CMO cites the last research brief.
None of it is what buyers have said. It is what the team believes buyers mean, filtered through notes and summaries.
The 24% goes into the model.
What the Model Requires
The revenue forecast requires assumptions about buyer behavior: what share of qualified prospects will close, how quickly, at what contract value, how long they'll stay, and under what conditions they'll expand. These numbers are not arbitrary — they're derived from historical performance, which means they represent what actually happened.
What they don't represent is why.
A 24% conversion rate is a description of outcomes. The mechanism behind it — why buyers who entered the funnel converted at 24% and not 28% or 19% — is not in the model. It's not in the CRM data. It was in the buyer conversations that produced those outcomes, and it was discarded in the notes and briefs that summarized those conversations.
The model treats the historical rate as a baseline. But a baseline derived from outcomes the organization doesn't understand is not a foundation — it's a number that will hold until conditions change, and then fail to explain itself. The 24% tells the CFO what buyers did. The reasoning behind what they did — the conditions that led to a decision, the alternatives they considered, the concern that nearly stopped the deal — was generated in those conversations and has not been kept.
When the Number Changes
The conversion rate was 24% for three consecutive quarters. In Q4 it came in at 17%.
The CFO needs to understand why before committing to a Q1 forecast. The explanation available comes from the functions that own the number. Sales says deal cycles lengthened — buyers took longer to decide and several deals pushed into Q1. Marketing says the ICP mix shifted in Q3 — a higher share of enterprise prospects who move more slowly. Product says a competitor shipped a feature in October that changed how buyers evaluate the category. Each function is offering a theory about what buyers did and why they did it.
None of them have the buyer's account. The conversations that produced the Q4 rate are gone — compressed into CRM notes, summarized in pipeline reviews, distilled into probability percentages. What buyers said in those conversations — before the Q4 results were visible — is not available.
The CFO builds a bridge between Q4 actual and Q1 projected using the best explanation available. It is the only option. Asking what buyers said about what changed is not a question the organization can answer.
What the CFO Gets
When the organization runs buyer conversations as structured sessions — discovery calls, ICP interviews, CS health checks — the corpus that accumulates changes what's available when a number moves.
The conversion rate drop is still a fact. But it's a fact with a mechanism. The corpus shows that buyers in Q4 conversations described a longer internal approval process — a pattern that appeared in nine conversations in September and October and was absent in Q2. Not a theory derived from outcome data after the miss. What buyers said, at the time, before the Q4 results were determined.
The CFO building the Q1 model doesn't have to choose between the sales leader's theory and the marketing leader's theory. The buyer conversations that happened during the quarter are structured and queryable. When deals lengthened, buyers said why — in their own words, in real time, before anyone knew what the quarter would produce. The pattern that explains the rate change is in the corpus.
The forecast assumption doesn't become a certainty. But it becomes a calibrated estimate grounded in buyer reasoning rather than what the teams that own the number believe happened — and when it needs to be revised, the revision is grounded in the same source. The CFO knows what the assumption is built on. When conditions change, the corpus shows what changed and when.
What the Number Was Always Measuring
Every conversion rate, churn rate, and expansion trigger in the revenue model is a compressed description of buyer behavior. The number records the outcome. The mechanism behind it lives in the conversation — in discovery, in the renewal discussion, in the CS health check that happened three months before the churn decision.
Those conversations have always happened. The buyer who closed or didn't close, stayed or churned, expanded or contracted, had a reason. If the conversations that produced the outcome were structured to produce something more than a CRM note or a health score, the mechanism behind every assumption in the model is recoverable. The 17% isn't a mystery that requires a post-mortem. It's the output of conversations that were happening in real time, in which buyers were explaining exactly what was changing in how they made this decision.
Most revenue models are built on residue because that's what's available. The buyer reasoning that would turn a historical rate into a calibrated assumption — one the organization understands well enough to know what would change it — was generated in every customer-facing conversation the organization has ever run. It was discarded before it could reach the model.
The number didn't change without a reason. The reason was in the conversation.
Mayetik helps revenue teams run customer conversations as structured sessions that produce briefs rather than notes, surface the buyer reasoning behind conversion rates and churn signals, and build the intelligence that makes a forecast assumption more than a residue of prior performance. Start your free trial.
Start capturing knowledge today
Mayetik helps teams design better questions, capture structured conversations, and synthesize intelligence that compounds over time.
Found this useful? Share it.
Next in Part 5
The Risk That Appeared in Five Conversations
A risk surfaced in a QBR as something new. It had appeared in five independent conversations across three projects over six months — in a sales brief, a CS health check, a product retrospective. Three teams, different words, the same underlying exposure. Nobody connected them because there was no system to connect them.