What the New Head of Revenue Asks on Day Thirty
By Rich Garcia, Co-founder of Mayetik · June 23, 2026 · 7 min read
She's been in the role for thirty days. She has read the investor deck, the competitive landscape, the pipeline report, the most recent win/loss summary. She has had fifteen conversations — with the sales team, the founders, the biggest customers. She is oriented enough now to ask specific questions instead of open ones.
The question she asks is this: over the last eighteen months, what have buyers been saying about why deals stall at technical evaluation? Not the label in the pipeline. Not the rep's theory. What have buyers actually said — in discovery calls, in evaluation conversations, in the moments before they went quiet?
She asks this of the VP of Sales. He says he'll look into it and get back to her.
Nobody comes back.
What the Discovery Call Produces
The conversations she is asking about happened. Every deal that reached technical evaluation had a discovery call before it — a conversation where a buyer described exactly what they meant by technical evaluation, what previous experience was making them cautious, which stakeholder inside their organization was the actual obstacle, and what would need to be true for the concern to be resolved.
That's not a summary. That's not a theory. That's the buyer's own account of their situation, given before they had committed to anyone, before they had any reason to shape what they said.
In those conversations, buyers are at their most specific. They say what they tried before. They say what failed and what the failure looked like. They describe the engineering lead who blocked a previous integration and what that person will need to see. They explain the difference between a real dependency and a stall. None of this was invented after the fact. It was said, in the room, and the rep heard it.
What happened to it after that is the problem.
What the CRM Note Carries
The discovery call became a CRM note. The note says: "technical evaluation — pending; engineering sign-off required." That is what was recorded. The buyer's reasoning — the prior integration failure, the specific concern about API reliability, the internal champion who doesn't have enough standing to push the evaluation through without a proof of concept — is not in the note.
This is not a discipline problem. Notes can't contain conversations. A CRM note is an event record: what happened, what the next step is, what stage the deal is in. The reasoning behind the buyer's words requires context that the event record format doesn't support. So the reasoning gets discarded — not intentionally, just as a structural consequence of compressing a conversation into a field.
When the rep who ran the call is still on the account, the reasoning lives in their memory. They can be asked what the buyer meant and they'll know. When that rep moves to a different territory, leaves the company, or simply isn't in the room when the CRO asks her question, what remains is the note. The note says technical evaluation. It says nothing about why.
Over eighteen months of discovery calls, what compounds is the event log. The reasoning doesn't compound. It goes with each rep who carried it.
What She Inherits When She Inherits a Brief Corpus
The CRO whose first organization ran discovery calls as structured sessions asks the same question on day thirty and gets a different answer.
Not a theory from whoever is still around. Not a rep's reconstruction of a handful of deals. An answer drawn from the conversations themselves: here is what buyers said about technical evaluation across eighteen months of deals, in their own words, with the patterns across accounts visible and the variations between segments named.
The pattern that was always there — that deals stalling at technical evaluation in financial services traced to a different concern than deals stalling at technical evaluation in healthcare, that one concern appeared in early conversations and was resolvable with a proof of concept while the other appeared later and wasn't — was always there in the conversations. The only question was whether it was kept in a form that survived the reps who carried it.
When it was, the new CRO doesn't have to start from the theories her team offers on day thirty. She has the source. She can read the briefs. She can see what buyers said before the outcome was determined — before anyone knew which deals would close and which would stall — and she can work from that rather than from the retrospective account of what the team believes happened.
She can do her job. The incoming head of revenue who inherits a CRM full of notes is doing a different job: assembling a theory about what buyers mean from the residue of conversations that no longer exist in retrievable form.
The Test the New Executive Runs Without Knowing It
The question a new executive asks on day thirty is not a question about history. It's a diagnostic.
She is not asking what happened in those deals in order to relitigate them. She is asking because how the organization answers her tells her what she's working with. An organization that can answer — not with theories, but with what buyers said — has been building institutional memory. An organization that responds with "let me dig through the notes" has a record of activity.
The difference between those two situations is not the conversations that happened. Both organizations ran discovery calls. Both had buyers describe why deals stalled at technical evaluation. The intelligence was generated either way.
What differs is whether it was kept in a form that survives the rep who ran the call. Notes survive the rep. The reasoning in the note — the why — doesn't.
The new CRO on day thirty is the most accurate test of whether an organization has institutional memory, because she's asking questions the organization didn't know it needed to prepare answers for. She didn't ask about what's in the CRM. She asked what buyers said. Those are not the same question. The answer to the second one was in the conversations. Whether it's still there depends on how those conversations were kept.
Mayetik helps revenue teams run discovery calls, win/loss reviews, and CS health checks as structured sessions that produce searchable briefs — so the CRO who joins on day thirty can ask what buyers said and get an answer, not a theory. 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
A Knowledge Repository Is Not Institutional Memory
Most teams believe they have institutional memory. What they have is a repository. A repository stores what was captured. Institutional memory makes it usable by someone who wasn't there. Those two things are not the same — and the gap between them explains why teams with excellent documentation still lose knowledge, still repeat research, and still depend on whoever happens to remember being in the room.