© 2026 Will Matthews. The R.I.G.H.T Framework™ — Built from 27 years in enterprise presales and technical sales. Cambridgeshire, United Kingdom. Contact: wmatthews@elmsectest.co.uk
Meetings
What R.I.G.H.T really does, perhaps more than anything else, is fundamentally change how an SE views meetings. Most SEs spend their careers operating reactively. Someone from Sales books a call, throws a vague title into Outlook, maybe forwards an email chain containing half a clue, and the SE turns up hoping context will somehow materialise during the first five minutes. In many companies, that becomes the entire rhythm of the role. Meetings simply happen to the SE. The calendar fills, the demos pile up, the PoCs multiply like rabbits, and “busy” becomes mistaken for “effective.”
R.I.G.H.T changes “meetings” mentality completely. Instead of drifting from meeting to meeting like a technical passenger in someone else’s sales process, the SE starts approaching every interaction with intent. Every meeting now has a purpose beyond merely surviving it. The question stops being “What am I showing?” and becomes “What am I trying to establish?” That sounds like a subtle difference, but in reality it changes everything. Take the typical request every SE has heard a thousand times: “Can you jump on a demo next Thursday?” Traditionally, the SE says yes, opens the slide deck, dusts off the golden demo, and starts mentally preparing to explain the same five features for the nine-hundredth time. But a R.I.G.H.T-oriented SE responds differently. The instinctive follow-up becomes: “Absolutely. What are we trying to establish from the meeting?” That single question forces clarity into the room. Suddenly the meeting has to justify its own existence. Is the customer simply curious? Are they investigating a genuine problem? Are they gathering information for a project? Are they trying to validate an assumption? Are they looking for reassurance? Or are they merely entertaining themselves on a Friday afternoon because someone higher up told them to “look at vendors”? This is where the SE stops being a product demonstrator and starts becoming an investigator. The realisation many SEs eventually come to, usually after years of burnout, is that a frightening amount of enterprise activity is theatre. Endless “high-level introductions,” “discovery calls” with no discovery, demos with no defined problem, PoCs launched on optimism alone. Entire weeks disappear into a fog of corporate motion where everyone looks busy but very little is actually advancing. The SE becomes trapped inside a kind of industrialised busyness machine. The R.I.G.H.T framework acts as a filter against that chaos. The first thing an SE should really be trying to understand in meetings is the Reason. Not the surface-level request, but the genuine business pain underneath it. This is where so many meetings collapse into mediocrity because people confuse use cases with features. As we wrote elsewhere, integration with Microsoft EntraID is not a use case. A reporting screen is not a use case. A dark mode toggle certainly isn’t a use case. The use case is the human or operational problem sitting beneath the technology. Your VPN example illustrates this perfectly. A weak Sales Rep asks for “SSH over VPN” to be demonstrated, but has absolutely no understanding of why the customer supposedly wants it. Without context, the SE is effectively being asked to perform a magic trick for no reason. But the moment the real business challenge emerges three hundred engineers in India needing secure access to infrastructure in the United States to maintain SLA compliance the entire conversation changes. Now the SE has something meaningful to work with. The discussion can become tailored, intelligent, relevant. The SE can frame the demo around operational continuity, remote access governance, contractor risk, scalability, and resilience. The product suddenly becomes secondary to the problem. And ironically, that is usually the moment the product starts becoming genuinely compelling. That is one of the hidden truths of presales: Customers rarely care about the technology as much as vendors think they do. What they care about is whether you understand their world. A good SE meeting should therefore feel less like a performance and more like a collaborative investigation. The customer should walk away thinking: “These people understand what we’re dealing with.” Not: “They clicked through their dashboard very confidently.” This naturally leads into Intent, which is one of the areas where experienced SEs develop almost supernatural instincts. Intent is not measured by enthusiasm. Prospects saying “great demo” means almost nothing. People compliment demos constantly. British people especially will thank you politely even if you’ve bored them to the edge of death. Attendance means little too. Large enterprises can generate meetings endlessly without ever buying anything. Real intent reveals itself through behaviour. Prospects with genuine intent give access to stakeholders. They discuss internal problems honestly. They expose political challenges. They share timelines. They invest effort. They bring technical people into conversations. They ask difficult questions because they are mentally trying to make the project real. People without intent behave differently. They consume information endlessly while risking nothing themselves. They ask for presentations, then more presentations, then perhaps a “quick technical overview,” then maybe a “lightweight PoC,” all without ever emotionally committing to solving the underlying problem. This is why “Why?” and “So what?” become such powerful tools in meetings. They force clarity. They gently drag conversations away from vague enthusiasm and toward consequence. “What happens if this isn’t solved?” “What’s driving this now?” “What happens if the project slips six months?” “Why does this matter internally?” These are not aggressive questions. In fact, mature customers often appreciate them enormously because so few vendors ask them. Most vendors are too busy unloading PowerPoint slides like a B-52 bomber carpet-bombing a village. Then there are the Guardrails, and this is often where the truly valuable SE separates themselves from the demo jockeys. Guardrails are the uncomfortable realities surrounding the opportunity. Budget limitations. Procurement complexity. Security concerns. Political resistance. Lack of internal resources. Existing contractual obligations. Architectural blockers. Executive indifference. These things kill deals every day, yet astonishing numbers of sales cycles proceed without anyone openly discussing them. A mature SE surfaces these issues early, not because they want to destroy momentum, but because they want to understand reality. This is where “Happy Ears” sales culture becomes dangerous. Some Sales Reps become emotionally attached to the fantasy of the opportunity and start treating qualification like sabotage. The SE asking difficult but reasonable questions suddenly becomes “negative” or “too technical” or “complicating things.” But in truth, the SE is often the only adult in the room. Because qualification is not negativity. Qualification is respect for time. And this is where the framework starts becoming commercially powerful. The SE is no longer just helping deliver meetings. They are helping determine whether the company should invest time, technical resources, PoC effort, executive attention, and forecasting credibility into the opportunity at all. That naturally leads into Hypothesis, which is where the best SEs begin behaving less like presenters and more like consultants. Every meaningful meeting should contain some degree of hypothesis testing. The SE begins forming educated assumptions about the customer’s situation and carefully validating them. “I suspect the operational visibility is the real issue here.” “It sounds like your challenge isn’t data collection but organisational coordination.” “My impression is that the handoff between teams is causing delays.” Then the SE tests those assumptions collaboratively: “Am I understanding that correctly?” That changes the emotional dynamic of the meeting entirely. The customer stops feeling “sold to” and starts feeling understood. The conversation becomes cooperative rather than performative. And finally there is Time — perhaps the great revealer of truth in enterprise sales. Urgency exposes seriousness. A prospect with no timeline may still be genuine, but very often the absence of time pressure indicates the absence of pain. Real projects usually collide with real consequences. Compliance deadlines. Contract renewals. Operational failures. Budget windows. Executive pressure. Customer dissatisfaction. Something is forcing movement. Without that pressure, opportunities can drift for years in a strange limbo where endless activity occurs without any genuine momentum. A strong SE therefore keeps gently anchoring meetings back to time: “When does this need solving?” “What happens if nothing changes?” “What’s driving the schedule internally?” These are not merely sales questions. They are risk questions. Priority questions. Reality questions. And perhaps that is the biggest transformation R.I.G.H.T creates in an SE. The SE stops being a passive technical assistant and becomes the technical conscience of the opportunity. They stop measuring success by how many meetings they attend and start measuring it by the quality of understanding created inside those meetings. Ironically, once an SE reaches that point, they become vastly more valuable to everyone around them — especially leadership. Because while many people inside a sales organisation generate activity, very few generate clarity.
PROBLEM
A strong SE focuses on the underlying business challenge, not just the requested feature or demo. The goal is to understand what is genuinely causing pain, risk, cost, inefficiency, or frustration inside the customer’s organisation, and whether the problem is significant enough to justify change.
Intent
Commercial Reality
Stakeholder Mapping
Risk
Momentum
Not every meeting represents a real opportunity. An SE should constantly assess whether the customer is actively trying to solve a problem or simply gathering information. Genuine intent is usually revealed through urgency, stakeholder engagement, openness, and willingness to define meaningful next steps.
Technology decisions are rarely just technical. A good SE understands the broader business impact of the problem, including operational risk, financial consequences, efficiency gains, and strategic importance. Understanding the commercial stakes helps determine how serious the opportunity really is.
Large organisations contain multiple stakeholders with different priorities, concerns, and levels of influence. An SE should always consider who benefits from the solution, who may resist it, who controls approval, and which important voices may still be missing from the conversation.
Every opportunity carries risks that could delay or kill the project entirely. Strong SEs identify technical, organisational, political, security, and operational risks early. Understanding these risks allows the team to qualify opportunities properly and avoid wasting time on unwinnable situations.
Every meeting should move the opportunity forward in some meaningful way. Whether through deeper understanding, stakeholder alignment, technical clarification, or agreement on next steps, an SE should constantly assess whether genuine progress is being made or whether the meeting is simply generating activity without direction.
6 Pillars of any meeting
No single meeting is likely to reveal every important detail about an opportunity. Some information may come from previous conversations, internal discussions, email exchanges, trusted stakeholders, or even observations made outside the meeting itself. The role of the SE is not to rigidly interrogate the customer, but to remain constantly aware of what information is still missing. Every meeting should therefore be viewed as an opportunity to improve understanding, reduce uncertainty, and move closer to determining whether the opportunity is real, winnable, and commercially meaningful. The following pillars provide a simple mental framework for the areas an SE should continually assess throughout the sales process.