Inbound discovery call with a prospect using manual spreadsheets. The temptation to demo immediately was present from the first exchange. The simulation tested whether you could hold the discovery discipline — resist the pitch, surface the quantified problem, map the decision, and close on a concrete next step — without the conversation collapsing into a product tour.
You ran a disciplined discovery conversation that consistently prioritised understanding over pitching — the evidence holds across every stage of the call.
From the opening resistance to the demo request through to the stakeholder mapping and the targeted capability connection at the close, the call followed a deliberate sequence rather than an improvised one. The quantified cost surfaced — 6 hours per week and two near-miss compliance errors — because you asked for specifics rather than accepting a general complaint. The one area that warrants attention is disqualification: the evidence shows strong qualification instincts, but there is no visible moment where you tested whether the opportunity should be walked away from, which is the discipline that separates pipeline quality from pipeline volume.
Your questions followed a clear SPIN-style sequence — situation, then problem, then implication — and you pushed past vague answers to get to specific, quantified pain. You did not skip from problem to solution, which is the most common failure mode at this stage.
You heard what the prospect said and used it to shape the next question rather than returning to a prepared sequence. The stakeholder mapping came directly from the prospect mentioning multiple people were involved — you picked that up and followed it immediately rather than completing a different thread first.
You held the agenda from the open. The prospect's first move was to request a demo — a redirect that would have ended the discovery — and you absorbed it without refusing it, then steered back to understanding. The pace of the conversation stayed yours throughout.
The qualification work was thorough — problem, cost, stakeholders, timeline — but the evidence does not show a moment where you tested whether this opportunity should not proceed. Qualification and disqualification are different disciplines. One asks 'do we have what they need?' The other asks 'should we be here at all?'
Resisted the demo request at the open — asked what triggered the search before discussing the product. This is the moment most sellers lose the discovery; you did not.
Pushed past 'it's getting unwieldy' to get a specific, recent example. The quantified cost — 6 hours per week, two compliance errors, nearly a client — came directly from that refusal to accept a generalisation.
Connected product capability only to the specific stated pain at the close, not to a generic feature list. The final pitch was earned by what the prospect had said, not prepared in advance.
Closed on a concrete, mutually-agreed next step rather than 'I'll send some info' — which is the next step that dies in the inbox.
No visible disqualification moment anywhere in the call. The opportunity moved forward on the strength of a real problem, but whether the criteria for qualification were actually met — budget, authority, timeline, fit — was not tested explicitly.
Stakeholder mapping was initiated but not probed deeply in the evidence available. Knowing 'multiple people are involved' is the start of that question, not the end of it — who has veto power, who is the economic buyer, and who will stall it were not surfaced.
Discovery sequencing — situation to implication before solution
The call moved from trigger to problem to quantified cost to stakeholders to timeline before a single product capability was mentioned. That sequence is what the discovery was designed to produce, and you ran it.
Specificity pressure — refusing to work with vague answers
When the prospect offered 'it's getting unwieldy,' you asked for a specific recent example and a quantified cost. The 6 hours per week and the near-miss compliance errors are the direct result of that pressure. Without it, the discovery ends with a general complaint and no leverage.
Controlled close — earning the next step
The call closed on a concrete, mutually-agreed next step anchored to what the prospect had said. That close is only possible if the discovery surfaced enough to make a specific proposal — which it did.
Disqualification discipline — explicitly testing whether to proceed
The call qualified the opportunity well — problem, cost, stakeholders, timeline — but did not run the disqualification test. There is no moment in the evidence where you asked a question whose honest answer might have been 'this isn't the right time' or 'we're not the right fit.'
Why it mattersAt senior IC level in enterprise SaaS, pipeline quality is as important as pipeline volume. Carrying opportunities forward that fail the disqualification test costs time in later stages — demos, proposals, legal — that would have been better spent on qualified accounts. The discovery is the cheapest place to make that call.
Stakeholder depth — moving from 'multiple people involved' to named roles and influence
You correctly identified that multiple stakeholders were involved and mapped to a next step, but the evidence does not show you probing who holds veto power, who the economic buyer is, or who is most likely to stall the deal after the demo.
Why it mattersIn a multi-stakeholder enterprise deal, the person on the discovery call is rarely the only one making the decision. Knowing the name and role of the person who can kill the deal — and whether you have access to them — changes how you structure the next step and what you propose.
Qualification confidence may substitute for disqualification discipline
The thoroughness of your qualification — surfacing a real, quantified, urgent problem — made the case for proceeding feel self-evident. That is exactly the condition in which the disqualification question gets skipped: when everything looks positive, asking whether to walk away feels counterintuitive. The evidence from this call suggests that instinct is present.
This call produced strong qualification evidence — quantified problem, stakeholder awareness, timeline — but there is no moment where you tested the other side of that question: whether the deal should proceed at all. That asymmetry is not visible when the pipeline is healthy, but it compounds over time as deals that should have been closed early absorb time in later stages. The discovery stage is the cheapest place to make that call, and right now it is not being made.
In your next discovery call, write one disqualification question in advance — something whose honest answer could be 'actually, this isn't the right time' or 'we're not a fit for your situation.' Ask it before you propose the next step.
The opening resistance to the demo request was the defining moment of the call.
Absorbing the demo request and redirecting to 'what triggered the search' without refusing or stalling is the skill that kept the discovery alive — most calls at this stage collapse into a product tour within the first two minutes.
Specificity pressure produced the only evidence worth carrying into the next stage.
The 6 hours per week and the two near-miss compliance errors exist in the record because you refused to work with 'it's getting unwieldy' — that refusal is repeatable and teachable.
Disqualification was the one discipline the call did not run.
Every qualification question was answered, but the question 'should we walk away?' was never asked — and at senior IC level in enterprise SaaS, that is the question that protects late-stage capacity.
Stakeholder mapping started but did not finish.
'Multiple people are involved' was picked up and followed, but the map did not reach named roles, veto power, or economic buyer — the information that determines whether the next step is a demo or a call with a different person.
The close was earned, not assumed.
A concrete, mutually-agreed next step anchored to the prospect's stated problem is only achievable if the discovery surfaced enough to make a specific proposal — this one did.
What this is: A structured assessment produced through guided conversation with Ren, Renatus's AI analyst, in a live simulation. Observations come from specific moments in the conversation, not from a psychometric test.
What’s in it: An overall read, dimension-by-dimension scores with evidence, and recommended next steps tailored to your patterns.
Go deeper: See Foundation for the frameworks Ren draws on, Methodology for how each score was calculated, and the Honesty Statement for how to interpret and use these results responsibly.
These are the named frameworks Ren draws on when interpreting your responses. They shape how evidence is read, not how it is scored.
Examines whether the conversation surfaced the dimensions that actually move enterprise deals — the underlying pain, who internally is advocating for change, who controls the budget, how the decision will be made, and how the offering compares to the alternatives the buyer is weighing. Grounded in established enterprise-sales practice.
Examines whether the questioning surfaced the customer's situation, the problems they face, the impact of those problems, and the value of solving them — rather than short-circuiting at problem. Based on field research into effective high-value sales conversations.
Renatus applies the underlying principles of established methods and credits their origin where relevant. Named frameworks, methods, and instruments are the property of their respective owners. Reference to them does not imply endorsement or affiliation.
Each scored dimension has a published rubric with five behavioural anchors at 90, 70, 50, 30, and 10 — each describes what someone operating at that level visibly does. Ren reads the evidence in the conversation against these anchors and assigns a score from 0 to 100. The anchor numbers mark the threshold of each level: your score sits at or above the highlighted anchor and below the next one up. The band the score falls within is highlighted on each rubric below. Read the full methodology →
Consultative question sequencing (Rackham 1988, SPIN Selling; Dixon & Adamson 2011, The Challenger Sale) holds that the quality of a discovery conversation lives in the structure and specificity of the questions — moving from situation to problem to implication to need. Scored on the structure of the subject's questions.
Questions were structured, specific, and sequenced. Moved deliberately from situation to the implications of the problem rather than skipping straight to solution. The customer did most of the talking and arrived at the problem more clearly than they began.
Question sequencing was sound. Occasionally rushed from problem to implication without fully developing the implication, but the structure held.
Questions covered the right ground but were less well sequenced. The customer ended up having to assemble the implication of their problem themselves, which the subject's questions should have done.
Questions defaulted to situation and skipped to solution. The implication was either asserted by the subject or not surfaced at all. The customer was talked at more than drawn out.
Question quality was poor. The conversation was a pitch in question form, with little useful evidence about the customer's actual situation emerging from it.
Consultative selling treats listening — including to what the customer doesn't say — as the substantive work of discovery. Scored on the evidence in the subject's responses that they had actually heard the customer rather than waited for their turn.
Listened actively. Picked up on hesitations, qualifications, and what the customer didn't say. Reflected back accurately and used what the customer said to shape the next question rather than the next pitch.
Listened well in most exchanges. Occasionally moved to the next prepared question without fully integrating what the customer had just said, but the overall responsiveness was sound.
Heard the explicit answers; missed the implicit ones. The conversation captured what the customer said but not what they meant or what they avoided.
Listened to respond rather than to understand. The subject's questions followed their own sequence regardless of what the customer had just contributed.
Did not listen meaningfully. The customer's words had little effect on the direction of the conversation; the subject's agenda ran through unmodified.
Enterprise deal qualification frameworks (MEDDIC, BANT, Challenger) treat control of the conversation — pace, sequence, the question the subject is in the customer's seat by the end — as the test of a discovery conversation. Scored on how the subject held that control without dominating.
Held control of the conversation throughout without dominating it. Set the agenda at the open, paced the discussion deliberately, and secured the answers the qualification required before the conversation closed.
Maintained control across most of the conversation. Occasionally let the customer redirect into solution discussion before qualification was complete, but recovered the thread.
Control was uneven. Strong on the parts of the conversation the subject was prepared for; let the customer drive on the parts they weren't. Significant qualification gaps remained at the close.
Lost control of the agenda early. The conversation went where the customer took it; the qualification questions the subject needed answered did not get asked.
No effective control. The conversation was shaped entirely by the customer's interests and pace; the subject left without the information any reasonable qualification framework would require.
Enterprise qualification frameworks treat disqualification as the discipline that protects pipeline quality — the willingness to walk away from opportunities that don't meet the criteria rather than carrying them forward. Scored on the subject's discipline in the scenario.
Disqualified deliberately where the criteria were not met. Named the gap to the customer honestly rather than carrying the opportunity forward on hope. Protected pipeline quality at the cost of pipeline volume.
Disqualification discipline was sound in most exchanges. Occasionally extended an opportunity past where the qualification supported it, but the gap was visible and small.
Held qualification standards loosely. Carried forward opportunities that the criteria didn't fully support, on the assumption that the situation might develop. Pipeline volume took precedence over quality.
Avoided disqualification. Reframed weak signals as encouraging ones; kept opportunities alive that should have been closed. The pipeline that resulted is thinner than its size implies.
No disqualification discipline visible. Every conversation became a continued opportunity regardless of fit. The qualification framework was either unknown or unused.
Each dimension is scored continuously 0–100 and combined using the weights below to produce the overall. Dimensions that carry more of the skill's outcome are weighted higher; dimensions that are enabling inputs or secondary qualifiers are weighted lower.
| Dimension | Score | Weight | Weighted |
|---|---|---|---|
| Question Quality | 82 | 25% | 20.5 |
| Listening | 78 | 20% | 15.6 |
| Control | 76 | 25% | 19.0 |
| Disqualification | 62 | 30% | 18.6 |
| Overall | 74 | — | — |
This assessment is a structured analytical tool, not a clinical diagnostic. Results reflect patterns in your responses and should be interpreted as a starting point for reflection, not as fixed or absolute truths about you. Outputs depend on the depth and candour of the conversation that produced them: a brief or guarded session yields a thinner read; a fuller, more reflective session yields a richer one. The frameworks Ren draws on shape interpretation, they do not produce a verdict — two thoughtful readers could weigh the same evidence differently. Treat the report as one informed perspective among several, alongside your own experience, feedback from people who know you in context, and any formal assessments you trust. Do not use these results as the sole basis for employment, promotion, performance management, or any consequential decision about another person.
