Methodology Playbook

Summary

Founders frequently misread their stage of growth and either hire a CRO too early or step into the role without understanding what it actually demands. Kevin's view is that CRO readiness has two distinct dimensions: organizational readiness to hire one, and leadership readiness to become one. Both require deliberate diagnosis before action.

Methodology

Kevin distinguishes between two related but separate challenges founders face around the CRO function. The first is the hiring question: a company is not CRO-ready until it has solved repeatable outbound and achieved cross-functional alignment — hiring into structural gaps sets any CRO up to fail. The second is the transition question: when a founder does step into a formal revenue leadership role themselves, it requires a specific leadership framework, not simply doing more selling or managing more people. Kevin resists giving tactical task lists in either scenario, instead elevating the conversation to the organizational and leadership requirements the situation actually demands. He uses structured diagnosis to challenge the founder's self-assessment of their stage, surfacing the gaps that must be closed first. The result is a sequenced approach: fix the foundation, then hire or step into leadership with clarity on what the role truly requires.

Summary

Engineering underperformance is almost always a leadership problem before it is a talent or process problem — the absence of a strong technical leader creates cultural drag, erodes cross-functional trust, and blocks revenue. Founders must diagnose whether the root cause is a leadership gap, a process gap, or a talent gap before choosing an intervention. Whether the solution is promoting internally or hiring externally, it must be executed with full leadership alignment or it will fail.

Methodology

Kevin begins by helping founders move away from generalized complaints about engineering culture or work ethic and toward specific, observable behaviors that point to a root cause. He distinguishes three distinct failure modes — leadership gap, process gap, and individual talent gap — and coaches founders to be precise about which one they are actually facing. When the question is whether to promote an internal engineering manager, Kevin treats leadership team alignment as a hard prerequisite, not a soft preference — unresolved concerns among key leaders are a blocker that must be surfaced and resolved explicitly before any promotion decision is made. He also connects engineering capacity directly to revenue, reframing engineering hires not as overhead or scaling decisions but as revenue-unblocking actions tied to specific pipeline that cannot convert without them. Across all of these situations, Kevin holds the founder accountable for owning the engineering leadership problem rather than delegating blame to individual contributors or letting the issue compound as a cultural drag on the broader organization.

Summary

Kevin's hiring philosophy is built on two non-negotiables: never lower the quality bar to solve a velocity or pipeline problem, and treat the hiring team's genuine excitement as a required threshold, not a nice-to-have. Every step of the hiring process — from take-home assignments and critical thinking exercises to objection checklists and third-party interviews — is designed to surface signal that interview performance alone cannot provide. Candidate evaluation is treated like a sales process: diagnose real objections, address root concerns with evidence, and ensure alignment across all decision-makers before closing.

Methodology

Kevin structures hiring as a multi-stage diagnostic process rather than a linear interview funnel. Early in the process, he recommends assigning take-home work tied directly to the role — researching target accounts, building a 30-60-90 day plan, or solving a simulated problem — to filter for commitment and surface critical thinking that conversations cannot reliably reveal. He treats candidate evaluation as separable from personality assessment: work quality is judged on its own merits first, then manageable traits like arrogance or risk factors like outside startups are evaluated against specific, verifiable data points rather than gut aversion. When a hiring manager is blocked by past trauma or vague risk aversion, Kevin coaches them to distinguish substantive addressable concerns from fear-based reasoning, and to work through each objection directly with the candidate before any final decision meeting — arriving with evidence, not just advocacy. For wavering candidates or high-stakes closes, Kevin escalates to founder-led relationship selling rather than leaving objection-handling to the hiring manager, and recommends treating compensation negotiation like a sales conversation — running discovery on the real objection before defaulting to the maximum number. Structurally, Kevin insists that the hiring pipeline never pauses after an offer is accepted, that the quality bar never moves to solve a throughput problem, and that any hire involving a personal relationship includes an objective third-party interviewer to ground the decision in merit.

Summary

Kevin's core conviction is that founders and sales leaders consistently wait too long to act on underperformance, hiding behind PIPs, open-ended timelines, and process rituals that delay inevitable outcomes and damage team momentum. The right framework is to set unambiguous expectations upfront, diagnose quickly whether the issue is coachable (system/process) or terminal (fit/values/character), and then act decisively once the diagnosis is clear. How you exit someone matters as much as the decision itself — framing departures around fit rather than failure preserves dignity, reduces legal risk, and reflects the kind of culture the founder is building.

Methodology

Kevin begins by distinguishing between two fundamentally different underperformance problems: a system or workflow problem (where a rep lacks the right process, tools, or clarity) versus a character, values, or fit problem (where the person is unwilling or constitutionally misaligned). For the former, he prescribes a short, defined evaluation window — roughly one week — with explicit expectations made clear. For the latter, he advises moving immediately, because coaching cannot fix a values mismatch and attempting to do so only erodes the leader's credibility and the team's culture. Kevin is explicitly critical of PIPs, characterizing them as a tool that creates false hope, delays the inevitable, and signals to the employee that improvement could save their job when the leader has already concluded it cannot. His preferred alternative is to set clear KPIs and cultural standards upfront, evaluate against them quickly, and act when the threshold is crossed. When executing the exit, Kevin provides tactical guidance: lead with cultural fit language rather than performance language, give the employee conversational on-ramps to arrive at the exit themselves, and position the leader as an ally in the person's next chapter. For legally or emotionally complex situations — including contractors, employees connected to prior terminations, or new hires who've triggered team feedback — he advises compressing the execution timeline and keeping the conversation strictly on documented facts. Across all scenarios, Kevin frames the ability to make and execute termination decisions cleanly as a core leadership competency that founders must deliberately build.

Summary

Kevin's central conviction is that premature sales hiring is one of the most common and costly mistakes early-stage founders make. Founders must personally own and validate the sales motion first — closing real deals, understanding the full cycle, and building a repeatable process — before any delegation to a hire is appropriate. Only once a proven, codified motion exists should founders begin sequencing hires, and even then, the order, profile, and timing of each role matters enormously.

Methodology

Kevin begins every hiring conversation by asking whether the founder has a repeatable, validated sales motion. If not, he redirects them back to founder-led sales regardless of the urgency they feel to add headcount. Once a motion is proven, he applies a sequencing model: the founder sells to roughly 25 customers, then hires the first rep (often an SDR/AE hybrid or a 3-4 year enterprise rep depending on the market), then scales the team to 3 consistent AEs, and only then brings in a Head of Sales. He ties each hire to a revenue event or milestone rather than hiring in anticipation of growth, and builds in redundancy — for example, recommending a third rep hire to hedge against the statistical likelihood that one of two early reps will wash out. For roles beyond sales, he applies the same sequencing logic: founders must do the fieldwork themselves first (e.g. customer success site visits, outbound prospecting) to understand what the role actually requires before defining and filling it. When hiring is appropriate, Kevin is highly specific about profiles — preferring 'hire the buyer' candidates with domain credibility for enterprise roles, scrappy builder-types over polished executives at the 0-$10M stage, and lead hires (e.g. lead SE) before individual contributors so the lead can own subsequent hiring and ramp. He treats coaching the founder as the highest-leverage first investment, ahead of any sales headcount, because a founder who can't sell can't train, manage, or evaluate a rep.

Summary

Kevin's approach to sales hiring is built on structured evaluation across three layers: resume screening for hard disqualifiers, a chronological interview methodology that surfaces character and consistency, and role-specific testing that validates each required trait under real conditions. He treats cultural and motivational fit — especially a candidate's appetite for building in ambiguity — as equally important to quantitative track record, particularly for early-stage companies. Hiring mistakes almost always trace back to skipping one of these layers or letting founder bias (toward likability, charisma, or warmth) substitute for rigorous evaluation.

Methodology

Kevin begins before the interview by using resume screening as a structured filter: frequent short tenures, missing quantifiable achievements, and seniority mismatches are disqualifiers — not concerns to explore later. In the interview itself, he walks chronologically through every role in the candidate's career, probing actual numbers, reasons for leaving, and specific circumstances at each stop; this surfaces inconsistencies, distinguishes genuine performance from accidental success, and reveals how the person behaves under pressure. He then maps each trait on the job profile to a specific evaluation mechanism: a research-and-outreach assignment tests cold pipeline-building ability, attention to detail, and strategic thinking; a mock pitch tests discovery and communication; behavior throughout the process (follow-up, responsiveness, preparation) tests execution discipline without a dedicated test. For early-stage AEs specifically, Kevin requires 6+ years of AE experience — not general sales tenure — and flags founder bias toward likable or charismatic candidates as a structural risk, replacing those traits with self-starter, critical thinker, and curious. Motivational fit is evaluated explicitly: the right first sales hire must actively want to be first, not merely tolerate it, and a candidate's stated reasons for each career move are as diagnostic as their quota attainment. When a submission or interview raises red flags — declining activity over time, warm-network substitution for cold outreach, or vague achievement language — Kevin treats these as signals of role-fit failure, not gaps to coach through.

Summary

Candidates with managed services or MDR selling backgrounds are uniquely positioned for AI-powered SaaS roles because they've already mastered outcome-based value selling — articulating results rather than features. This matters most when a product has software economics but delivers value the way a service does, which is the defining characteristic of many AI-powered platforms. Kevin sees this as an undervalued transferable skill that hiring founders often overlook.

Methodology

Kevin's approach is to identify the structural similarity between the candidate's prior selling motion and the selling motion the new role actually requires. In the case of AI-powered platforms, the product may look like SaaS on a pitch deck but sells like a service — customers are buying a delivered outcome, not a feature set. Kevin names this explicitly for founders and hiring managers who may default to seeking pure SaaS or pure enterprise software backgrounds. He surfaces the transferable skill the candidate may not even have articulated about themselves, using it as a signal of fit. The coaching move is to reframe the evaluation criteria: instead of asking 'have they sold software?' ask 'have they sold outcomes?' — because that's the harder and more relevant skill for this motion.