The FACT Framework: How We Evaluate GTM Leadership Candidates

Every search firm has a screening process. Most of them look roughly the same: review the resume, confirm the titles and tenures, do a thirty-minute call to check for obvious red flags, and submit whoever clears the bar. The result is candidate flow that is plausible but not precise — people who could probably do the job, rather than people who have specifically done this job, in this environment, for this buyer.

At M Search, we use a four-dimension evaluation framework we call FACT. It was developed over years of placements specifically in B2B software GTM, and it's the rubric behind every candidate we submit. Here's how it works.

F — Functional Expertise

The first dimension is the most straightforward: does the candidate have the functional competencies the role requires? For a VP of Sales, that means experience building and managing a quota-carrying team, proficiency in forecasting and pipeline management, knowledge of how to structure a sales process for a complex enterprise sale, and a demonstrated ability to develop talent.

This sounds basic, and it is — but it's frequently where searches go wrong. The title "VP of Sales" covers an enormous range of actual experience. Some VP Sales candidates have managed a team of fifty across multiple segments. Others have managed a team of five in a single geography. Some have owned the full revenue function including marketing alignment, channel, and customer success. Others have owned only direct sales. The functional depth of the role and the functional depth of the candidate need to match.

We evaluate functional expertise through structured interviews that surface specific examples, not just claims. The question is not "have you built a sales team?" It's "walk me through the team you inherited, the decisions you made in the first ninety days, and what the org looked like eighteen months later."

A — Achievements in Domain

Functional competence tells you what someone can do. Achievements in domain tell you what they have actually done, in contexts that are relevant to your search.

Domain achievements go beyond quota attainment. They include: building a repeatable sales motion in a new market, reducing time-to-productivity for new hires, improving forecast accuracy, opening a new vertical, or successfully navigating a company through a PE transition while maintaining team stability. The achievement needs to be specific, verifiable, and relevant to the mandate at hand.

The key word is verifiable. We run back-channel references before submission wherever possible — not after an offer is made. The purpose is not to find reasons to reject a candidate, but to build a more complete picture of how they've actually operated, separate from how they present themselves in an interview.

C — Customer Set Overlap

This is the dimension most often underweighted in executive searches, and it's frequently the difference between a hire that ramps in sixty days and one that takes nine months to find its footing.

Customer set overlap means: has the candidate sold to the same type of buyer, in the same type of company, at a similar deal size and sales cycle complexity? If you're selling treasury intelligence software to CFOs at mid-market manufacturing companies, a candidate who has spent their career selling HR tech to SMB founders is not a fit — regardless of how impressive their quota numbers are.

At the senior level, customer set overlap also means relationships. A VP of Sales who has spent ten years selling into the office of the CFO comes with something that can't be taught: a network of buyers who know them, trust them, and will take their call. That network has direct commercial value in the first twelve months of the role.

We map candidate customer set overlap explicitly against the client's ICP before screening. If the overlap is not there, the candidate doesn't proceed — regardless of other strengths.

T — Technical Acumen

In B2B software, GTM leaders need to speak the language of the product. This doesn't mean they need to be engineers. It means they need to understand the problem the software solves, how it solves it, why it's differentiated, and how to communicate that differentiation to a technically sophisticated buyer.

Technical acumen is particularly critical for complex or emerging categories — AI infrastructure, financial operations software, cybersecurity, data platforms. In these markets, buyers are often technical practitioners who can detect superficial product knowledge immediately. A sales leader who can't hold a substantive conversation about the product will lose credibility with both the buyer and the internal team they're managing.

We evaluate technical acumen by asking candidates to describe, in their own words, how a previous product solved a customer problem — and then pushing on the specifics. The depth and accuracy of their answer tells us more about their technical fluency than any certification or credential.

Weighting by Context

The FACT framework is not a static rubric. Each dimension is weighted differently depending on the search.

For an early-stage company that has never had a VP Sales, functional expertise and achievements in domain are weighted heavily — you need someone who has built something from scratch and can do it again. For a PE-backed company post-acquisition with an existing team, customer set overlap and technical acumen may matter more — you need someone who can step into a running organization and credibly lead it without a long ramp.

For a cross-border US expansion search, functional expertise is table stakes, but achievements in domain need to specifically include experience building pipeline without brand support, and customer set overlap needs to be mapped against the US buyer profile rather than the home market profile.

The framework provides consistency across searches. The weighting provides relevance to each specific mandate. Together, they produce a candidate assessment that is both rigorous and contextually appropriate — which is what separates a precise submittal from a plausible one.

What FACT Looks Like in Practice

When we submit a candidate, the client receives a structured summary that maps the candidate against each FACT dimension explicitly. Not a biography. Not a cheerful cover letter. A clear, honest assessment of where the candidate is strong, where they're adequate, and where they carry risk — along with our recommendation on whether to proceed and why.

The goal is not to convince the client to interview everyone we submit. The goal is to give the client the information they need to make a fast, confident decision — and to protect their time by only submitting candidates who have cleared a genuinely high bar.