Methodology Playbook

Summary

Kevin's core conviction is that most B2B pitches are anchored too low — to operational efficiency, time savings, or headcount reduction — when the real value lives at the strategic level: market share, margin expansion, revenue unlocked, and decisions made with better information. The pitch and the price must both be calibrated to the organizational level of the buyer and the proximity of the product's impact to revenue. A cost-center framing caps deal size and invites commodity comparisons; a revenue or strategic-outcome framing commands premium pricing and creates durable conviction.

Methodology

Kevin uses a layered value architecture where the same product benefit must be re-expressed at each level of the org chart: individual time savings → team efficiency → departmental capacity → competitive positioning and margin expansion. He coaches reps to run dedicated discovery with each stakeholder tier to uncover their specific KPIs, growth constraints, and strategic priorities before introducing any value narrative. For products that don't directly generate revenue, he redirects the ROI case to the cost of the problem the product prevents — bad decisions, missed capacity, leadership blind spots — and asks teams to find a concrete reference moment where the absence of the product caused a measurable failure. Once a strong ROI number is established and validated with operational stakeholders, he advises pricing at 10–25% of that demonstrated value, anchoring high and letting procurement negotiate down rather than leading low out of fear. He also applies a proximity-to-revenue filter: if a product's primary narrative is justifying a cost rather than generating or protecting revenue, that structural weakness in the business case must be addressed before scaling sales efforts.

Summary

At the early stage, the primary goal of sales activity is not to close deals faster or make a single rep more efficient — it is to discover, document, and codify what a repeatable, teachable sales process actually looks like. Kevin treats the sales process as a product that must be engineered before it can be scaled: mapping stage gates, qualifying criteria, objection handling, and closing into a structured playbook. Only once that foundation exists should founders think about hiring, throughput, or channel expansion.

Methodology

Kevin begins by diagnosing whether a company has an explicit or only an implicit sales process — often founders have organic traction (referrals, self-serve conversion, demo-to-POC flows) but no documented methodology underneath it. He then maps whatever is working into a formal, milestone-based funnel with clear definitions of what qualifies a deal to advance from one stage to the next, eliminating internal ambiguity and circular conversations. The playbook is built across four functional areas: qualification, objection handling, closing, and the hiring criteria needed to eventually transfer the process to others. Kevin deliberately reframes the goal at this stage from 'make the current rep more efficient' to 'learn what the optimal process should be' — treating early sales runs as structured experiments whose output is a documented, teachable methodology. Goals set during this phase are framed around learning and validation rather than aggressive pipeline numbers, so founders can distinguish whether the strategy itself is working before blaming execution. Once the process is stable and proven, Kevin positions scaling headcount, entering adjacent markets, or adding inbound motion as sequentially appropriate next steps.

Summary

Kevin teaches that credibility is not a nice-to-have in sales — it is the primary asset that earns the right to ask questions, pitch, and price at a premium. Founders, especially international or early-stage ones, systematically underutilize their real accomplishments out of cultural conditioning, imposter syndrome, or language anxiety, and Kevin's job is to strip away that self-sabotage. Credibility is built through a specific, sequenced combination of personal story, domain expertise, concrete outcomes, social proof, and relationship depth — all deployed before the product conversation begins.

Methodology

Kevin prescribes a sequenced credibility-building architecture that operates across three layers. The first layer is the personal introduction: structured around three pillars — demonstrating intelligence/thoughtfulness, citing a specific impressive accomplishment with a memorable number or outcome, and establishing domain expertise relevant to what is being sold. This introduction should be compact, front-loaded, and delivered before any product discussion. The second layer is psychological: Kevin directly addresses the internal barriers — cultural stigma around self-promotion, imposter syndrome, language anxiety, and discomfort with authority — that cause founders to dilute or hedge their own story. His reframe is simple and repeatable: bragging involves exaggeration; stating facts is truth-telling, and truth-telling serves the customer. The third layer is contextual proof: Kevin coaches founders to deploy the right credibility signal for the right context — prior institutional pedigree (e.g., Amazon, AWS) for enterprise risk-averse buyers, specific client case studies (before/intervention/after) when asked for proof, name-brand customer logos when selling upmarket, mutual network connections to compress trust timelines, community validation (e.g., Bookface) when selling into tight-knit ecosystems, and industry-specific knowledge signals (e.g., name-dropping a relevant trade show) when selling into niche verticals. Across all of these, Kevin is explicit that the sequencing matters: credibility must be established before the ask, and every element of the introduction should be in service of earning the right to the conversation that follows. He models this approach himself — walking through his own background in a way that mirrors the prospect's situation — and uses it to anchor premium pricing before the number is ever discussed.

Summary

Kevin's core view is that competitive positioning must be specific, defensible, and grounded in a real capability or market advantage — not vague claims of being 'better built' or more flexible. Differentiation can come from technology, customer relationships, market knowledge, or go-to-market assets, but it must be articulable and honest. The way a company handles competition — in messaging, in POCs, in negotiations, and in partnership decisions — determines whether it wins deals or loses them to incumbents and well-resourced alternatives.

Methodology

Kevin begins by diagnosing whether the founder has a genuine competitive thesis — probing them to name specific capabilities, workflows, or market assets that competitors cannot easily replicate. He distinguishes between technology moats (hard to build without research or infrastructure), knowledge moats (deep understanding of a specific buyer's problem), and go-to-market moats (customer relationships, association partnerships, first-mover embeddedness, and reputation). When a founder conflates these or relies on vague superiority claims, Kevin pushes them to anchor in the concrete and provable. In competitive sales situations — bake-offs, POCs, renewal cycles — he coaches founders to shape the evaluation criteria proactively, be hands-on during the prospect's exploration, and address competitor strengths honestly rather than strawmanning them, because sophisticated buyers lose trust when every competitor slide shows near-zero capabilities. He also distinguishes between reactive competitive fear (which leads to product pivots) and strategic competitive response (which means accelerating customer capture and deepening embeddedness before a competitor can get a foothold). Finally, Kevin treats competitive dynamics as a sales tool — using acquisition activity, contract renewal timing, or the emergence of new entrants as urgency triggers in the prospect conversation, reframing inaction as the riskier choice.

Summary

Kevin teaches that control in a sales conversation is never passive — it must be actively maintained through strategic questioning, agenda ownership, and prepared recovery techniques. When conversations drift, derail, or turn adversarial, the worst response is to push through; instead, sellers should name what's happening, challenge assumptions rather than conclusions, and use structured verbal techniques to reset the dynamic. Preparation for failure modes is as important as preparation for the pitch itself.

Methodology

Kevin's framework for conversation control starts before the meeting: map the likely friction points (prospect disagrees, question derails the agenda, energy drops) and assign a specific technique to each. In live conversations, control is maintained through strategic questioning — whoever asks the questions leads — combined with a clear agenda held loosely, so the rep can acknowledge tangents, park them explicitly, and steer back without appearing rigid. When a prospect disagrees, Kevin's approach is to never attack the conclusion directly; instead, surface and correct the underlying assumptions ('you think X because of Y, but really it's A because of B'), which keeps the exchange analytical rather than personal. When a conversation goes genuinely off the rails, Kevin coaches a four-step de-escalation sequence: label the observation softly ('It seems like...'), check your read ('Am I wrong about that?'), hand control to the other party ('Can you help me understand?'), and sustain genuine curiosity rather than defensiveness. As a last resort on a completely stalled call, flipping the dynamic by asking the prospect for their advice breaks the stalemate, re-engages them, and often surfaces intelligence that restarts forward momentum.

Summary

Kevin believes demos fail when they become feature tours disconnected from what the prospect actually said they care about. Every demo should be a direct response to discovery — showing only the capabilities that map to surfaced pain points, introduced with a benefit-first narrative that calls back to the prospect's own words. The goal of a demo is never comprehensiveness; it is conviction and a clear next step.

Methodology

Kevin's demo methodology begins before the demo itself: discovery must precede any product showing, and the rep should summarize findings and get explicit confirmation from the prospect before proceeding. The demo is then scoped tightly to discovered pain — each feature is introduced with its benefit first, never the feature first. For complex or multi-stakeholder deals, Kevin prescribes individual discovery with each stakeholder before any group demo, so the presentation can be tailored by role and concern. Where the value proposition is extreme enough to trigger disbelief, Kevin treats a live demo as non-negotiable — run it in real time and let the output land before explaining it. Across formats, Kevin also coaches on the physical and vocal dimensions of delivery: energy, tonality, and the discipline to follow the customer's lead mid-demo rather than rigidly executing a script. The demo ends not with a product tour but with a clear mechanism to advance — a next step the prospect has been moved toward by experiencing the product, not just hearing about it.

Summary

Kevin's view is that sales training fails when it's generic, one-time, or disconnected from measurable outcomes. The right approach segments training by role — SDRs versus AEs — with distinct curricula tied to the specific metrics each role owns. Domain expertise in the target verticals is layered in as a structural advantage, not an afterthought.

Methodology

Kevin begins by diagnosing where revenue is actually leaking: is it a top-of-funnel SDR problem, or an AE-side execution problem like price-dropping and weak negotiation? He separates these failure modes explicitly so training resources aren't misallocated. He then maps core sales competencies — cold calling, discovery, objection handling, negotiation, demoing, closing — to the roles that actually use them, giving SDRs a top-of-funnel curriculum and AEs a deeper, more advanced track. Each track is anchored to distinct success metrics so progress is measurable rather than subjective. Kevin also flags that training without a reinforcement cadence decays quickly, especially on teams without a dedicated sales manager — so he builds an ongoing training rhythm (not just a one-time workshop) into the operating model from the start. Finally, he treats vertical domain expertise — fintech, collections, BPO — as a parallel investment, running structured biweekly learning sessions across the go-to-market team so reps can sell consultatively rather than transactionally.

Summary

Kevin's core methodology insists on a structured assessment phase before any playbook, framework, or process work begins — this means interviewing team members independently, reviewing raw materials firsthand, and experiencing the sales process yourself as a buyer. Playbooks must be built from the ground up based on the company's own context and sequenced correctly relative to the stage of the business: too early and they add overhead without payoff, too late and you're scaling chaos. The right order is always diagnose, then build, then hire, then systematize.

Methodology

Kevin opens every engagement with a structured two-week assessment: he sends a pre-work questionnaire covering existing playbooks, call recordings, and KPIs, while simultaneously scheduling one-on-one intake calls with the founder, co-founder, every sales rep, and revenue operations. He reviews all raw materials — call recordings, email templates, demo scripts — firsthand rather than relying on filtered summaries, and where possible signs up for the product himself to experience the sales funnel as a buyer. Only after this parallel-track assessment does he deliver recommendations on process, CRM, org structure, or messaging. When playbook work begins, he builds it from the ground up based on the company's specific ICP, objection patterns, and stage — never from external templates or competitor documentation. Frameworks like SPICED, MEDDIC, or bowtie are introduced only after reps have proven themselves in months one through three, ensuring that systematization codifies what's actually working rather than imposing structure on an unvalidated motion. Onboarding new reps follows a 30-60-90 day progressive handoff: month one the rep shadows the founder, month two the founder shadows the rep, month three the rep operates independently with a target of two closed deals as the benchmark for self-sufficiency.

Summary

Before optimizing any part of a sales process, founders must first identify exactly where in the funnel deals are breaking down — whether at top-of-funnel volume, mid-funnel conversion, follow-up, or infrastructure gaps like CRM and scheduling. Kevin's core belief is that most early-stage sales problems are process and diagnosis problems, not product or market problems. Only after mapping the full funnel with real conversion data can founders prioritize the highest-leverage fix.

Methodology

Kevin begins every sales diagnostic by walking founders through their funnel sequentially — from first touch to closed customer — documenting conversion rates, dropout reasons, and missing process steps at each stage. He separates symptoms (low revenue, slow growth) from root causes (insufficient top-of-funnel volume, broken follow-up, wrong ICP, disconnected tooling) and resists the impulse to prescribe fixes before the diagnosis is complete. Once the bottleneck is isolated, Kevin uses reverse funnel math — working backwards from a target number of closed deals through each conversion rate to determine the required input volume at the top — so that activity goals are anchored in data rather than guesswork. He also stress-tests founders' assumed conversion benchmarks, pushing back when figures are too conservative or too optimistic. For infrastructure gaps (no CRM, unlogged calls, disconnected tools, no follow-up sequences), Kevin treats these as table-stakes fixes that must be resolved before any outbound scaling or hiring begins, since leaky infrastructure means adding volume only amplifies waste.

Summary

Kevin treats cold outbound not as a fixed playbook but as a diagnostic problem: before optimising volume, copy, or cadence, founders must first identify whether the failure is in targeting, messaging, channel fit, or measurement. The right outbound motion is determined by where prospects actually live — phone, email, LinkedIn, fax, or in-person — and the sequencing of channels matters as much as execution within any single one. Referrals and warm introductions should be exhausted before cold infrastructure is built, and outsourcing should only follow after the founder has personally mastered the conversation.

Methodology

Kevin's outbound diagnostic begins by asking whether the problem is targeting (ICP too broad), messaging (value prop not landing), channel fit (wrong medium for the prospect's world), or measurement (no data to act on). He insists that founders manually validate messaging with a small, personalised sample before automating or scaling — cold email templates can improve results by only 10–15% at best, so volume cannot compensate for a broken hypothesis. Once a channel is instrumented, Kevin evaluates it through a sequential funnel: leads → open rate → response rate → positive response rate → meetings → closes, and he locates the exact stage where drop-off occurs rather than treating underperformance as a single failure. When one channel is clearly outperforming others, Kevin advises concentrating resources on that channel and stopping underperformers rather than running parallel efforts at reduced quality. He sequences outbound maturity deliberately: founders should start with cold calling or referral-led outreach to generate early signal, progress to multi-channel structured cadences (email + LinkedIn + 2–4 call touches) once messaging is validated, and only then consider outsourcing or automation — and only after the founder has internalised what a good qualified conversation sounds like. Speed of response matters once a strong signal-based system is in place, because competitors accessing the same intent signals will reach the same prospects simultaneously.

Summary

Most stalled deals are not product problems — they are symptoms of qualification failures, unstated objections, misidentified decision-makers, or missing stakeholder alignment that compound over time. Kevin treats every stall as a diagnostic signal that points back to something broken earlier in the sales process, whether that is qualification, champion empowerment, stakeholder mapping, or urgency creation. The antidote is almost always a combination of proactive objection surfacing, direct engagement with the real decision-maker, and concrete process intervention rather than passive waiting.

Methodology

Kevin begins every stalled deal conversation by identifying the precise stage where momentum broke down — ghosting after first meeting, stalling in legal, loss after second demo — and uses that inflection point as a diagnostic lens rather than a tactical starting point. He distinguishes between deals worth continuing to pursue and those that should be labeled low-probability and deprioritized, pushing founders to apply an honest internal scoring rather than over-investing in unwinnable situations. For deals worth saving, he prescribes stage-specific interventions: surfacing hidden objections using 'It seems like...' framing, re-engaging original champions to understand stakeholder shifts, bypassing powerless champions via executive back-channeling, or going in person to unblock legal and procurement delays. He insists that champion enthusiasm is never a proxy for deal health — founders must independently verify that every key stakeholder who can kill the deal has been identified, engaged, and given what they need to feel safe saying yes. Throughout, Kevin treats the sales process as a sequence of conviction checkpoints, not a mechanical checklist, and coaches founders to constantly read whether each stakeholder is genuinely convinced before advancing to the next stage.

Summary

Kevin's foundational coaching principle is that most sales problems are misdiagnosed — founders and sales leaders default to tactical fixes when the root cause is often upstream, whether that's product-market fit, a founder's sales identity, a skill gap versus a confidence gap, or a structural team deficiency. Before any coaching or execution begins, Kevin runs a structured diagnostic to identify which layer of the business is actually broken. The right intervention depends entirely on the correct diagnosis.

Methodology

Kevin opens every engagement with a structured assessment phase — reviewing sales calls, interviewing stakeholders, and mapping the founder's background, team composition, deal history, and sales motion — before prescribing anything. He distinguishes between multiple root cause categories: product-market fit misalignment, sales execution gaps, founder identity or fear barriers, sales leader skill versus confidence deficits, and structural team gaps (e.g., all-engineer teams with no sales DNA). He uses concrete benchmarks — deal volume, cycle length, ARR per deal, pipeline hygiene — to surface scalability gaps and anchor diagnostic conversations in math rather than intuition. When a founder's stated problem doesn't match the evidence (e.g., asking to 'build sales' with zero validated pipeline), Kevin redirects rather than accepts the framing. He also evaluates coaching fit itself: if a company's stage, growth model, or team profile doesn't warrant a sales coaching engagement, he says so explicitly rather than forcing a fit. Throughout, he holds multiple hypotheses simultaneously — sales execution and PMF — and coaches founders to do the same before defaulting to tactical fixes.

Summary

Kevin's view is that poor urgency and low conversion rates are almost always symptoms of shallow discovery — not product problems. The job of discovery is not to qualify a lead but to surface unarticulated pain, connect it to something the customer emotionally cares about, and make the cost of inaction concrete. A prospect who intellectually sees value but doesn't move has never been made to feel the gap.

Methodology

Kevin structures discovery as a two-phase process: first, establish credibility briefly, then pivot entirely to inquiry — asking questions designed to surface challenges the prospect hasn't fully named yet. The goal is diagnostic, not presentational. Kevin warns against 'double-education' traps where the founder must both create category awareness and convince the prospect they have a problem — this compounds difficulty and destroys conversion rates. For prospects who have normalized broken workflows, Kevin advises mapping their existing process in granular detail, then reflecting it back to them so they see the dysfunction themselves. Once pain is surfaced, the founder must connect it to something emotionally significant — a CTO's fear of losing visibility, a team's frustration with manual work — not just an ROI calculation. Only after that emotional connection is established should the story of the solution be told, mirroring the customer's own language back to them. Urgency is never manufactured through artificial tactics like limited-time discounts; it is built by making the cost of delay concrete and framing the solution as a genuine risk hedge.

Summary

Discovery is not a checkbox before the pitch — it is the primary trust-building mechanism in any sale and the skill that separates great salespeople from average ones. Done well, discovery surfaces not just known pain points but unknown unknowns: problems the customer hasn't articulated, assumptions they haven't examined, and limitations in their current approach they haven't fully reckoned with. The rep who asks questions the prospect has never thought to ask themselves earns the position of trusted advisor, not vendor — and that positioning is what wins enterprise deals.

Methodology

Kevin's discovery methodology operates on two distinct layers: the first confirms known pain (what the prospect already recognizes as a problem), and the second excavates hidden leverage points — dependencies, workflow inefficiencies, and blind spots the prospect hasn't yet articulated. He coaches reps to map the customer's end-to-end workflow, understand their KPIs and success metrics, learn what solutions they've already tried, and surface the root business objective beneath any stated requirements or feature list. Discovery questions should be 'selfless' — designed to help the customer see their situation differently, not just to fill in a qualification template — and should use 'what' and 'how' framing rather than 'why,' which can feel interrogative. When a prospect resists discovery and pushes for a demo, Kevin's instruction is to lean in rather than retreat: treat resistance as a signal that something important has surfaced, ask one more targeted question anchored in what the prospect just disclosed, and only transition to the pitch once a genuine diagnostic picture has been built. The final step is to reflect the customer's workflow and pain back to them before positioning the solution, which simultaneously validates your understanding and demonstrates that you have genuinely listened.

Summary

Before pitching any AI coding solution, you must first map the prospect's existing AI tooling stack and understand both their wins and frustrations with it. The goal is to get the prospect to articulate the ceiling of their current tools in their own words — where Cursor, Copilot, or others stop delivering — so your solution lands against a real, felt pain rather than a hypothetical one. Positioning built on the prospect's lived frustration is always more compelling than positioning built on a generic value prop.

Methodology

Open discovery by asking how the prospect currently uses AI coding tools like Cursor or Copilot, making it a natural conversation about their workflow rather than an audit. Follow up by anchoring on concrete outcomes they've already experienced — productivity gains, quality improvements, time saved — to establish credibility in the space and warm them up to the topic. Then probe for the ceiling: where do those tools stop working, what still requires heavy human intervention, what problems remain unsolved? The objective is to get the prospect to self-identify and articulate the gap in their own language before any mention of your product. Once they've named the frustration themselves, you can position your solution as the precise answer to what they just described, making the pitch feel inevitable rather than manufactured.

Summary

Kevin's core view is that enterprise pricing is a psychological and structural game, not a math problem — founders who treat it as math give away leverage before the real negotiation begins. The discipline of anchoring high, withholding pricing until value is established, and reading procurement as a predictable adversarial process (not a crisis) is what separates founders who close large deals from those who discount their way to bad terms. Every concession must be strategic and tied to scope or terms, never made reactively under pressure.

Methodology

Kevin's enterprise pricing methodology begins upstream of the negotiation itself: engineer anchoring before the first conversation by displaying high-tier pricing publicly on the website, so buyers arrive pre-calibrated to realistic enterprise spend levels. When pricing does come up in conversation, withhold specifics until the prospect has explicitly engaged with the enterprise model — only then offer a range (mid-to-high five figures scaling to mid six figures depending on scope), never a single number that the founder will immediately negotiate against themselves. For larger deals, proactively propose a 2-3 month paid POC at $10K-$20K to reduce perceived risk without discounting the core contract. Pad initial pricing by 10-20% to absorb procurement's structural mandate to extract concessions — procurement's KPI is cost reduction, not speed, and treating their intervention as a crisis rather than an expected phase is the most common founder mistake. When procurement pushes aggressively, distinguish between genuine deal-breakers and standard negotiation theater; anchor every position in documented facts from prior conversations, present value drivers confidently before the number, and signal openness to flexibility on scope or terms — not on margin. On non-price contract terms like IP ownership, insurance requirements, or exclusivity demands, treat your core red lines as absolute non-negotiables and move contentious legal back-and-forth off email and onto a champion call first, then lawyer-to-lawyer with explicit red lines pre-defined.

Summary

Enterprise sales is a fundamentally different discipline from SMB or product-led growth — it requires deal-size-appropriate motions, dedicated team structures, and realistic timeline expectations. The most common founder mistakes are under-monetizing large accounts, applying velocity tactics to relationship-driven cycles, and misreading enterprise slowness as product or pitch failure. Kevin's core thesis is that getting the structural variables right — deal size, ICP tier, champion quality, and team segmentation — matters more than optimizing execution within a broken model.

Methodology

Kevin begins by diagnosing whether the problem is structural (wrong deal size, wrong motion, wrong ICP tier, mismatched team) or executional — and in the majority of cases at the early stage, it is structural. He uses deal math as a forcing function: at $100K+ ACV, only 8–10 contracts are needed to reach $1–2M ARR, which reframes the problem from volume to precision. He then maps the sales motion to the ACV band — high-touch relationship selling for $120K+ deals, dedicated enterprise reps for strategic whales, and AI-assisted or inbound-only motion for sub-$12K deals — and explicitly warns against mixing these motions within one team. For pipeline prioritization, Kevin ranks deals by internal champion strength over company brand or size, because a senior champion who is actively evangelizing internally is the single most reliable predictor of deal velocity. He normalizes enterprise timelines (6–18 months in most industries, longer in finance and healthcare) and coaches founders to stop interpreting slowness as rejection, instead identifying the next stakeholder to maintain and mapping the approval chain. Finally, he introduces the 'whole product solution' lens — reminding founders that enterprise buyers are purchasing integrations, support, change management, and risk mitigation alongside core functionality, and that gaps in the surrounding solution kill deals even when the core technology is strong.

Summary

Kevin's core conviction is that founder-led sales is not a stopgap — it is a mandatory, deliberate skill-building phase that must precede any sales hire, team build, or delegation. Founders must personally sell until they can diagnose why deals are won or lost, distinguish between PMF gaps and execution problems, and articulate what 'good' looks like in their specific sales motion. Only after that foundation is built — typically around $1–2M ARR or 20–30 customers — does it make sense to transition toward a sales org, and even then, the founder must stay close to customer conversations to keep product and market in alignment.

Methodology

Kevin sequences founder sales involvement into four distinct phases. Phase one is pre-PMF: if the founder has fewer than a handful of paying customers and no repeatable motion, they are not ready for direct sales investment — they need a growth hacker, async funnel, or scrappy self-serve approach. Phase two is zero-to-one: once there is a signal worth chasing, the founder becomes the sole salesperson, personally running every step of the cycle — cold outreach, discovery, objection handling, and close — because only that proximity reveals whether deal losses are caused by product gaps, market selection errors, or execution failures. Phase three is codification: once the founder has closed enough deals to see patterns, Kevin coaches them to install structure — repeatable process, defined ICP, consistent messaging, and a six-step sales cycle that other founding team members can also run. Phase four is transition: only after the motion is proven and the founder has deep sales IQ does Kevin endorse hiring — first an AE or SDR to execute the playbook, then a VP of Sales to scale it — and even then, the founder must remain in customer conversations as a product feedback and market calibration mechanism. Throughout all phases, Kevin flags structural risks: a single founder carrying all sales creates a bottleneck; fragmented ownership across consultants and vendors creates confusion; and delegating too early — before PMF or before the founder has genuine sales competence — is one of the most common and costly early-stage mistakes.

Summary

When prospects claim they can build your solution internally, the worst response is a direct confrontation — it triggers defensiveness and turns into a features debate you can't win. Instead, Kevin's approach is to validate the impulse to build, then systematically make the real cost and timeline visceral through education, evidence, and direct comparison. The goal is to reframe the partnership not as a permanent dependency but as a fast, low-risk on-ramp that runs in parallel while internal capability matures.

Methodology

Kevin's approach to build-vs-buy objections operates in three layers depending on where the prospect is in their internal build journey. For prospects who haven't started yet, lead with the speed asymmetry argument: frontier AI teams move in months, not years, and top AI talent is nearly inaccessible due to competition from OpenAI, Anthropic, and peers paying millions in salaries — position the external partnership as the fastest on-ramp, not a long-term lock-in. For prospects who believe they can build cheaply, never challenge the estimate directly; instead, arm them with a comprehensive breakdown of hidden costs and non-obvious complexities so they arrive at the real number themselves — let the education do the selling. For prospects who have already built internal capabilities, shift away from abstract feature comparisons entirely: build a tailored demo that makes your differentiated value viscerally obvious, then propose a side-by-side pilot so results speak for themselves. Across all three scenarios, a consistent framing anchor is that the engagement can always be cancelled once internal capability is ready — this removes the perceived risk of commitment and reframes the decision as a parallel bet rather than a binary choice. The through-line is that Kevin never positions the vendor as superior in the abstract; he makes the cost, timeline, and quality gap concrete and self-evident.

Summary

The holiday period between Thanksgiving and mid-January is a distinct sales environment that requires deliberate calibration, not a blanket slowdown or a frantic push. Kevin's view is that non-response during this window is a market-wide phenomenon, not a personal rejection signal, and that the same period offers strategic advantages — open calendars for active buyers, natural rest windows for founders, and a historically strong January pipeline fueled by slipped Q4 deals. Founders who understand the seasonality can sequence outreach, recovery, and execution intentionally rather than reacting emotionally to silence.

Methodology

Kevin frames the holiday period as having three distinct phases that require different behaviors. Phase one (pre-holiday and Christmas week): continue outreach targeted at 'hustlers' — action-oriented decision-makers whose calendars are unusually open — while pivoting away from unreachable roles like CEOs toward operational decision-makers still present in their organizations. Phase two (Christmas through New Year's): use this as a genuine recovery window; Kevin treats rest not as weakness but as a strategic input, arguing that founders entering January depleted will underperform in one of the strongest deal-closing months of the year. Phase three (return to market): skip the first week of January entirely for follow-up, as inboxes are flooded and mental bandwidth is low; resume outreach in the second week with mid-day Monday timing for best engagement. Underpinning the whole model is a B2B seasonality framework — January, May, July, and October are strong months; August is weak — which allows founders to make proactive decisions about where to invest energy rather than treating every month identically. For founders who travel or take time off in January, Kevin's prescription is to pre-book follow-up meetings and check-ins before departure so pipeline momentum is protected regardless of physical absence.

Summary

A POC is not a passive technical evaluation — it is an active sales process that requires deliberate stakeholder management, engagement monitoring, and parallel workstream execution. Kevin's view is that most POCs stall or die not because the product fails, but because sellers manage them reactively: waiting for usage, deferring procurement, and neglecting executive sponsors until it's too late. Winning POCs require proactive intervention at every stage, from mapping the full buying committee at kickoff to pulling the executive sponsor back in at the decision point.

Methodology

Kevin structures POC management as a distinct, ongoing sales discipline — separate from pipeline reviews and deserving its own recurring meeting cadence. At kickoff, he pushes sellers to map the full buying committee, segmenting stakeholders into budget owners, technical validators, risk validators, and operational users, so there are no surprises later. Legal and procurement are treated as parallel workstreams, not a post-POC handoff — sellers are coached to initiate those conversations during the technical evaluation, not after it concludes. When product engagement drops, Kevin prescribes immediate proactive intervention: live demos, hands-on working sessions, and guided walkthroughs rather than waiting for the customer to self-serve their way to value. Executive sponsors are managed with deliberate sequencing — aligned early at kickoff, then intentionally re-engaged toward the end of the POC when the decision is being shaped, ensuring they have the context and conviction to champion the purchase internally. In-person meetings during the POC window are treated as a competitive differentiator that builds the personal trust required to convert a trial into a signed deal.

Summary

Kevin's view is that sales performance management requires precision at every layer — distinguishing between activity, process compliance, and outcomes; diagnosing which phase of the sales cycle a rep is struggling with; and designing systems that make expectations explicit and accountability structural. He treats performance gaps not as uniform problems but as diagnostic signals that reveal whether the issue is skills, mindset, process adherence, or fundamental fit. High performers deserve equally deliberate management, and their best behaviors should be codified and spread laterally across the team.

Methodology

Kevin begins by separating the dimensions of performance: activity metrics, process compliance (CRM hygiene, MEDDIC documentation), phase-by-phase sales cycle execution, and cultural fit. He treats each as a distinct diagnostic lens rather than collapsing them into a single quota number. When a rep underperforms, Kevin helps the manager isolate the earliest failure point in the funnel — because inability to book meetings is more fundamental and harder to coach than a closing weakness — and then determines whether the root cause is a skills gap, a process gap, or a fit issue. For compliance and accountability, Kevin favors structural solutions like daily standups and pipeline reviews that surface gaps in a group setting, creating implicit accountability without requiring constant top-down confrontation. For high performers, he recommends matching their diligence with equally deliberate management: frequent feedback loops, explicit week-over-week expectations, and active reinforcement of what they're doing right. Peer coaching is a deliberate tool in Kevin's methodology — having the strongest performer in a given competency coach a peer rather than routing all feedback through leadership, because it lands differently and removes the founder-as-critic dynamic. Finally, Kevin advocates for formal leveling and performance management systems with codified expectations and consequences at each level, treating this not as an HR exercise but as a cultural reset that makes accountability structural and defensible.

Summary

Sales reps who adopt victim narratives — blaming outcomes on external factors while ignoring their own lack of effort — rarely develop into strong performers. Kevin believes this posture must be addressed directly and specifically, not allowed to persist, because it signals a deeper pattern that undermines accountability and long-term growth. The test of ownership is effort, not intent.

Methodology

When a rep surfaces a victim narrative, Kevin's approach is to address it head-on rather than validate or sidestep it. The manager should walk through the specific actions the rep took — and failed to take — in relation to the opportunity or situation they feel wronged by. The goal is to move the rep from outcome-focused grievance to effort-focused accountability. Cherry-picking facts to support a grievance should itself be named as a red flag and addressed directly. If the rep cannot engage with that conversation productively, Kevin treats it as meaningful signal about their long-term potential on the team. Managers should hold the line clearly: effort is what earns ownership, and that standard applies to everyone equally.

Summary

Effective founder-led sales is less about technique and more about internal posture — approaching every conversation as a trusted advisor conducting an evaluation, not a supplicant seeking approval. The most common failure mode is founders leaning in too hard with product conviction, which signals neediness rather than confidence; the lean-back posture creates more psychological pull. Sales is fundamentally interpersonal labor, and its currency is trust, not information delivered or activity completed.

Methodology

Kevin's approach begins with a foundational mindset reframe: sales is not asking for a favor or imposing on someone — it is delivering value to someone who has a real problem. From that base, he coaches founders to adopt an advisor posture over a sales posture, entering calls with genuine curiosity about the customer's situation rather than urgency to pitch. He introduces the lean-back principle — calm confidence rather than high-conviction pushing — as the correct early-stage posture, because leaning in hard is externally indistinguishable from desperation regardless of genuine belief. Once posture is calibrated, Kevin layers in adaptive communication: identifying which of four buyer personality types (innovation, conservation, predictability, value) the prospect operates from and tailoring language, proof points, and framing accordingly. He also coaches founders to remove pressure from the sales motion entirely in stalled situations — reframing outreach as a feedback request or expertise consultation rather than a sales follow-up — so that prospects lean in voluntarily. Finally, Kevin draws a sharp distinction between interpersonal labor and technical labor, arguing that sales success is measured by trust and impact created in the relationship, not by activity metrics, information transferred, or linguistic polish.

Summary

Enterprise deals are not single-buyer conversations — they are political landscapes requiring deliberate identification and management of multiple stakeholders, each with distinct roles, motivations, and veto power. Kevin's core model identifies five functional roles that must all be engaged independently: project budget owner, technical validator, financial validator, risk validator, and operational validator. Relying on a single champion to carry the deal internally is the most common and most fatal mistake in enterprise sales.

Methodology

Kevin opens by reframing enterprise sales as a political organization problem, not a product or pitch problem. The first step is building a formal org chart of the target account, mapping every person involved in the buying decision by their functional role and their underlying mindset or motivation. He applies a five-role framework — project budget owner, technical validator, financial validator, risk validator, and operational validator — and requires that each role be identified, individually engaged, and independently convinced before advancing to procurement. Alongside roles, Kevin introduces a four-personality typology (innovation-minded, conservation-minded, predictability-minded, ROI/value-focused) that governs how messaging must be tailored for each stakeholder, because a founder's default innovation-forward pitch actively fails with conservative or process-oriented buyers. Champions are treated as levers, not proxies — Kevin coaches founders to actively equip their champion with the right internal narrative, anticipate objections on their behalf, and arrange multi-stakeholder meetings rather than delegating internal selling to a document or a single relationship. Finally, Kevin emphasizes proactive objection-pulling: surfacing and resolving each stakeholder's concerns directly strengthens deal security rather than creating risk, because unaddressed objections resurface at the worst possible moment.

Summary

When a founder is constrained by runway or consumed by an active fundraise, pushing for an immediate close is the wrong move. Kevin adapts by either negotiating a concrete checkpoint tied to a fundable trigger event, or reframing his coaching scope to include fundraise preparation — making himself directly relevant to the founder's most urgent priority. Both moves keep the engagement alive without creating pressure that kills the deal.

Methodology

Kevin treats fundraising timing as a real, legitimate constraint rather than an objection to overcome. When a founder has limited runway or is mid-raise, he identifies the specific trigger event that will change their capacity or urgency — such as closing a term sheet or completing an angel round — and negotiates a defined recheck window tied to that event rather than asking for an immediate yes. In parallel, if a founder's attention is about to shift toward a VC raise, Kevin reframes his coaching offering to include pitch preparation and fundraise strategy, making himself relevant to their most pressing problem. This consultative pivot expands the value proposition without abandoning the original engagement — it positions coaching as a lever for the raise itself. The result is a deal that stays warm and a relationship that deepens precisely when the founder needs support most.

Summary

Resistance from stakeholders — whether internal team members, clients, or enterprise gatekeepers — is almost never purely rational; it is rooted in ego, job security anxiety, or a conservation mindset. Kevin's central insight is that founders misdiagnose resistance as a logic problem and try to argue their way through it, when the real work is emotional and political. The antidote is 'Friendly Strength': meeting each stakeholder where their actual fear or mindset lives, holding firm boundaries without aggression, and expanding your internal surface area rather than fighting gatekeepers head-on.

Methodology

Kevin begins by reframing the founder's diagnosis: what looks like disagreement or obstruction is almost always a threat response. He then maps the stakeholder onto two axes — friendly-to-hostile and weak-to-strong — to identify the right posture for engagement. For ego-driven internal resistance, he prescribes structural agency within mandatory guardrails, letting the person feel ownership while non-negotiable standards are preserved. For enterprise gatekeepers with a conservation mindset (IT, security, legal), he coaches founders to abandon the innovation pitch entirely and instead position the product as a risk-reducer that protects the gatekeeper's domain. For hostile external stakeholders — threatening clients or misaligned executives — he uses a calibrated risk-reframing exercise to show founders that the fear of confrontation is disproportionate to the actual reputational risk, then coaches them to hold boundaries warmly and professionally. In complex competitive deals, Kevin adds a stakeholder mapping layer: identify who owns the incumbent solution and loop them in early, because displacement deals have a different political topology than greenfield ones.

Summary

Kevin treats follow-up not as a courtesy but as a systematic, non-negotiable sales discipline. Silence from a prospect is almost never a rejection — it is noise caused by competing priorities, busyness, or an unvoiced objection — and the founder's job is to persist until they receive an explicit 'no.' The method, tone, and channel of follow-up must be calibrated to context: aggressive multi-channel cadences for cold outreach, pattern-interrupting questions for long silences, and confidence-signaling updates for stalled enterprise deals.

Methodology

Kevin's follow-up system begins with a core reframe: non-response is ambiguity, not rejection. He normalises aggressive persistence by anchoring it in personal experience — calling a prospect 43 times over several days before closing a significant deal — to override the founder's fear of appearing pushy. For cold and warm outbound, he prescribes a structured multi-channel escalation cadence: rotate across phone, text, and email in the first two weeks rather than repeating the same channel; send a direct calendar invite without waiting for permission; and escalate to a binary pattern-interrupting question ('Have you given up on this project?') when a prospect has gone fully dark, because that question is socially difficult to ignore and forces a clear outcome. For stalled enterprise deals, Kevin distinguishes between two modes of outreach: desperation-signaling pitches that presume to know the prospect's objections, and confidence-signaling updates — new partnerships, customer signings, funding milestones — that demonstrate execution momentum and invite re-engagement on the prospect's terms. For holiday or timing-sensitive stalls, he recommends a direct binary question that acknowledges the buyer's context ('Are we able to move forward before the holidays or should I follow back up after the first?'), which removes ambiguity while reducing pressure. Across all contexts, Kevin insists that follow-up cadence should increase — not stop — when deals slow down, and that a hard 'no' from the prospect is the only legitimate signal to stand down.

Summary

Kevin treats pipeline management as the central operating system of a sales organization — not an administrative function. Before optimizing any part of the sales process, founders and sales leaders must first establish a clear, honest view of pipeline health by auditing stage-by-stage conversion rates, identifying where deals are stuck and why, and running the math backward from revenue targets to determine whether the current pipeline is even sufficient to close the gap. Pipeline reviews, accountability cadences, and deal-level diagnostics are the tools that turn a list of hopes into a forecastable, manageable business.

Methodology

Kevin begins every engagement with a pipeline triage: he audits the funnel across five core metrics — meetings held, qualified opportunities, active deals, lost deals, and closed deals — and maps where deals are stalling at a systemic level. He then runs backward pipeline math from the revenue target, applying realistic conversion rates (typically 20-33% opportunity-to-close) to determine the minimum pipeline coverage required, and compares that to current reality. Where deals are broadly stagnant, he reframes the diagnosis: if the pattern is widespread low urgency from prospects, he calls it a PMF problem, not a sales execution problem, and redirects energy to the easiest wins rather than pushing harder on stuck deals. For high-growth or fundraising-pressured situations, he identifies non-obvious channels — referrals, international customers, bluebird deal separation — that can fill the gap without requiring a full sales cycle ramp. On an ongoing basis, Kevin prescribes a strict accountability cadence: a daily 15-minute standup covering wins, action items, and blockers, plus a weekly 90-minute pipeline review where reps pull up the CRM live, and deals are analyzed as individual problems to solve rather than checklist items to check off. Pipeline concentration risks — single deals representing an outsized share of a target — are surfaced explicitly and either isolated from quota math or made the team's primary focus with all-hands resourcing, so the team viscerally understands the downside scenario and can mitigate it.

Summary

Kevin teaches that effective B2B pitching is never about listing features — it's about making the prospect feel their pain, then showing them a vivid, concrete picture of the world after that pain is gone. The pitch must lead with the customer's reality, anchor on the product's sharpest differentiator, and use analogy, metaphor, or narrative to make the value gap visceral rather than abstract. Generic or capability-led messaging commoditizes the product before the conversation even begins.

Methodology

Kevin's pitching methodology follows a disciplined narrative arc: (1) Name the specific, painful problem the customer faces in terms they recognise from their own day-to-day — make them feel it before you solve it. (2) Anchor on the product's single most defensible differentiator as the opening frame, not buried mid-pitch or listed alongside table-stakes features. (3) Use analogy or metaphor to make the generational leap from existing tools to your product immediately intuitive — the contrast should do the selling, not a feature list. (4) Apply 'future pacing' to paint a vivid, sequential picture of the customer's transformed workflow after adoption, getting them emotionally invested in the outcome rather than evaluating capabilities. (5) At conferences or cold settings, invert the instinct to pitch: lead with discovery questions, summarise what you've learned back to the prospect, and only then tell the story of how you solve their specific problem. (6) If the conversation stalls or over-pitching occurs, pivot to a concrete, measurable threshold — time-bound or dollar-bound — that defines what success looks like, grounding abstract value in real impact.

Summary

When selling AI products, the default messaging — automation, replacement, innovation — actively damages deals with conservative, risk-averse buyers. Kevin's view is that AI must be positioned around the buyer's existing worldview: protection, efficiency, and proprietary data advantage, not novel capability. The defensible value of AI lies in speed on unique customer data and insights that were previously impossible — not in displacing humans or replacing known software.

Methodology

Kevin begins by diagnosing the specific psychological and institutional profile of the buyer — insurance companies, enterprise procurement, or risk-averse operators each have distinct fear structures that must be mapped before any messaging is built. He then audits the existing pitch for three common failure modes: the 'AI replaces humans' narrative, abstract capability framing disconnected from the buyer's workflows, and pricing anchored to the wrong competitive set. Once those are removed, Kevin coaches founders to reframe around three positive anchors: (1) proprietary data advantage — the AI's value comes from operating on data only the customer has, not from generic intelligence; (2) capability expansion — what was literally impossible before, not just what is now faster; and (3) the 'aha moment' — unexpected, personalized insights the client could not have surfaced themselves. He also addresses downstream risks: AI language like 'agent' must be audited for autonomy concerns, demos must be tightly controlled given buyers' near-zero error tolerance, and data privacy fears must be reframed using the employee-skill analogy before they become objections. Pricing is repositioned away from software comparisons and toward the cost of human labor, making usage-based models rational rather than surprising.

Summary

Kevin holds firm on coaching pricing as a matter of principle — discounting is unfair to existing clients, signals low confidence, and attracts the wrong clients. Instead of defending the number, he reframes every pricing objection around the value of the outcome: if the engagement delivers what the client wants, the fee becomes irrelevant. When resistance is real, he offers structural flexibility (payment splits, session banking, project-first entry points) rather than reducing the rate.

Methodology

Kevin's standard pricing structure runs in two components — an upfront assessment fee plus a monthly retainer — and he presents these sequentially, often without volunteering the combined total upfront to avoid premature sticker shock. When a prospect objects to price, his first move is to anchor to their stated goal (e.g. $1M ARR, first enterprise deal) and ask whether the fee matters if that goal is achieved. If the objection persists, he reframes the risk rather than the cost — using the 'half-priced heart surgeon' and locksmith analogies to shift the conversation from price comparison to downside risk. For genuine budget constraints, he offers structural concessions only: splitting one invoice into two, switching from a retainer to a project model, or offering a money-back guarantee after month one — never a rate reduction. He also qualifies engagement duration before the pricing conversation escalates: if the prospect only wants one or two months, he disqualifies rather than sells, because his pricing model only makes sense in a longer-term context. When competing against cheaper alternatives, he moves his price up and differentiates on accountability and guarantee structure rather than racing to the bottom.

Summary

Kevin believes most early-stage founders systematically underprice their products — not because the market demands it, but because of psychological fear of rejection and a misread of what pricing signals to buyers. Pricing is not just a revenue lever; it is a confidence signal, a qualification tool, and a value communication mechanism. The discipline lies in anchoring to value delivered, sequencing the pricing conversation correctly, and never negotiating against yourself before the prospect has even pushed back.

Methodology

Kevin's pricing methodology begins with a foundational belief: if clients show no concern about price, that is diagnostic data indicating underpricing, not a comfort signal. He coaches founders to anchor pricing to concrete customer outcomes — time saved, volume multiplied, compliance risk eliminated — rather than to cost-of-delivery or competitor benchmarks. Before any pricing conversation, Kevin insists on sequencing: value must be established and ideally proven through a pilot before price is introduced, because a prospect who has experienced measurable outcomes has almost no incentive to negotiate hard. When the pricing moment arrives, Kevin teaches a two-part delivery technique — state the number once, precisely, without qualification, and then stop talking entirely to observe the unfiltered reaction. He prohibits email pricing discussions entirely, arguing that written communication strips the human signals that make pricing conversations legible and manageable. When a prospect counters with a lower number, Kevin's first move is never to concede — it is to diagnose whether the gap reflects unconvinced value, and if a concession is ultimately necessary, to scope the product down rather than drop the price, preserving price integrity for future deals.

Summary

Kevin's core belief is that pricing architecture is a strategic lever, not just a revenue decision — the right model aligns customer incentives with expansion, creates natural upsell triggers, and protects the vendor's negotiating position at every stage. He consistently pushes founders away from flat subscriptions or per-unit models that cap upside or penalize customer success, toward hybrid structures that combine a predictable base fee with usage-based consumption layers tied to volume commitments. The goal is to design pricing so that customer growth automatically drives revenue growth, renegotiation is structured not reactive, and the vendor never has to have the same painful pricing conversation twice.

Methodology

Kevin's pricing design process starts by stress-testing the current model against customer incentive structures: does the pricing punish adoption, cap upside, or obscure demand signals? If yes, he redesigns from the ground up. His preferred architecture has three components — a one-time implementation or onboarding fee that recovers cost and signals enterprise value, a recurring platform or base fee that creates predictable revenue, and a consumption or usage layer (credits, minutes, tokens, seats) priced with tiered volume discounts that improve with annual commitment size. Overage is priced deliberately above the contracted rate to create a financial incentive for customers to upgrade to larger tiers rather than absorb runaway costs. Kevin anchors negotiation conversations to actual usage data — not prior contract amounts — so the customer's own behavior sets the new baseline. He insists that pricing transitions should be designed so thoroughly that the vendor only has the restructuring conversation once: build the model to handle growth through rate adjustments, not contract rewrites. Finally, Kevin treats enterprise pilot pricing as a signal of seriousness — $3,000 pilots attract low-quality buyers, while $15,000–$25,000 pilots with built-in exit clauses reduce friction while qualifying commitment.

Summary

Kevin's core belief is that most pricing objections are not about price — they are about unresolved value perception, fear, or incomplete discovery. Sellers who discount prematurely or negotiate against themselves are signaling a lack of confidence in their product and training buyers to expect more concessions. The goal is to hold price with conviction, diagnose the real objection, and use structural concessions — bundled integrations, deferred payment, free trials, or term-length trades — rather than reducing the number on the page.

Methodology

Before any pricing conversation, invest in discovery to understand the customer's actual budget ceiling and internal approval process — price is rarely the true obstacle, and treating it as such leads to unnecessary concessions. When pricing is introduced, always do it live (phone or in-person) so you can read reactions and handle objections in real time; never send a written quote cold. When a prospect pushes back, resist the instinct to counter immediately — ask an open question ('What number works for you?' or 'What's driving that hesitation?') to surface the real blocker, which is often unresolved value perception rather than genuine budget constraint. If a concession is warranted, structure it as a trade — a discount in exchange for a longer contract, faster signing, or expanded scope — and never express it as a percentage in a contract, which creates a scalable, recurring liability; instead, reframe it as a bounded deliverable (e.g., two included licenses at no additional cost). When the prospect expresses sticker shock without a hard budget floor, reduce the commitment barrier rather than the price — offer a single low-friction next step (one call, a free session, a short trial) that keeps the deal alive without eroding commercial integrity. Finally, treat pushback as a positive signal: a buyer who negotiates is a buyer who wants to find a way to say yes.

Summary

Before investing in demos, proposals, or pricing, founders must rigorously qualify whether a prospect genuinely feels the pain and whether the customer is a true fit — someone who values your core offering, will pay fairly, and doesn't require disproportionate custom work. Skipping this creates downstream churn, operational drag, and broken ROI models. Discovery isn't a courtesy step; it's the structural prerequisite to every meaningful sales motion.

Methodology

Kevin's approach breaks pre-proposal qualification into three sequential gates. First, pain existence: determine whether the prospect is already experiencing the problem — not whether they can imagine it. Prospects who feel the pain now are buyers; those who don't are education projects with uncertain conversion. Second, fit assessment: run three diagnostic checks — does the customer value your core value proposition (not a narrow edge case), are they willing to pay fairly without defaulting to anchoring or demanding pre-commitment feature builds, and will they require disproportionate custom work? A customer who fails two of three is a churn and margin risk regardless of the logo or revenue size. Third, unit economics discovery: before any pricing or ROI conversation, gather the specific operational data that makes your model defensible — job size, reprogramming frequency, cycle times, and margins. Without these inputs, your value story is a guess the customer can dismantle. Kevin treats these not as sequential nice-to-haves but as hard gates: moving forward without clearing each one means the founder is carrying risk that hasn't been priced or acknowledged.

Summary

Kevin teaches that effective B2B sales starts with ruthless qualification — identifying who actually feels the pain, who will resist, and who is simply not a fit yet. Disqualification is not failure; it is signal that sharpens your ICP and protects your product roadmap from noise. Every other element of the sale — ROI framing, stakeholder mapping, objection handling, positioning against incumbents — only works if you have first anchored to the right buyer and the right pain.

Methodology

Kevin's approach begins with anchoring to the primary economic buyer — typically the top-level technical leader (e.g., the CTO) — and pressure-testing whether the pain is acute enough at that level to justify the sale. He then maps the full stakeholder hierarchy to identify not just champions but internal resistors: mid-level managers who may feel threatened by visibility tools lose narrative control, and their resistance will kill adoption post-sale if not addressed during the selling process. Once buyer fit is established, Kevin coaches founders to build explicit disqualification criteria — organizations with already-good visibility, teams satisfied with existing tools, or companies too small to feel the pain — and to treat each disqualified prospect as ICP signal rather than a lost deal. For prospects who do qualify, Kevin reframes objections through root-cause discovery: a data source concern, an integration gap, or a 'I want to stay hands-on' pushback are all invitations to go deeper, not to list features. Against entrenched tools like Jira, he leads with the structural failure mode of the incumbent — stale, manually-updated data — rather than feature comparisons, positioning the new product as a fundamentally different category. Finally, Kevin warns founders to maintain product-market fit discipline when early customers pull the roadmap in multiple directions, treating every feature request through a single filter: does this reinforce the core value proposition, or is it scope creep disguised as customer responsiveness?

Summary

Kevin's core belief is that stalled and lost pipeline is one of the most underutilized assets in any B2B sales motion — these prospects already know you, have been through some discovery, and represent a dramatically lower-cost path to revenue than cold outreach. The failure to re-engage is almost never a lead quality problem; it is a behavioral and process problem, where founders and reps let urgency fade and allow ambiguous pipeline states to persist indefinitely. Re-engagement is not a single tactic but a differentiated playbook that must be calibrated to the specific reason the deal stalled — timing constraint, champion absence, competitor selection, ghosting, or budget freeze.

Methodology

Kevin's re-engagement methodology begins with a forensic audit: review call transcripts and email chains to understand exactly where and why each deal stalled before crafting any outreach. He then segments the dormant pipeline by root cause — timing-locked, champion-gone-cold, competitor-selected, ghosted, or not-yet-ready — and prescribes a distinct re-entry strategy for each. For timing-locked deals, he mandates a concrete calendar task set at the moment of the constraint discovery, not left in an ambiguous pipeline state. For ghosted deals, he pushes multi-threaded outreach to every stakeholder who was in the room, led by a value artifact such as a build-vs-buy analysis or a relevant case study, rather than a single repeated follow-up to the primary contact. For deals where a prospect has returned inbound or re-engaged on their own, Kevin instructs founders to resist relitigating history and instead prioritize in-person meetings and fresh discovery — specifically diagnosing whether the champion's conviction is still intact before moving to pricing or negotiation. Across all re-engagement scenarios, he consistently emphasizes that the first conversation back should prioritize discovery over closing: understand whether the problem still exists, what has changed, and whether new stakeholders need to be brought into the conversation before assuming the original deal thesis still holds.

Summary

When prospects anchor AI pricing to legacy software tools, they create an unfair and misleading comparison that undervalues what AI actually delivers. The correct competitive set for AI is human labor — specifically, the cost of hiring an engineer or specialist to do the same work. Kevin argues that usage-based pricing for AI is not only justified but logical, given the underlying compute and energy costs that traditional software simply doesn't carry.

Methodology

Kevin's approach starts with diagnosing the root cause of a pricing objection: in most AI deals, it's not budget, it's the wrong reference point. When a prospect compares your AI tool to a fixed-price legacy software product (e.g., a $25K database tool), they've miscategorized what they're buying. The prescribed move is a two-step reframe: first, explicitly name and dismantle the false comparison so the prospect understands why it doesn't apply; second, introduce the correct comparison frame — the fully-loaded cost of hiring one or more engineers to produce the same output. This shifts the conversation from 'is this expensive software?' to 'is this cheaper than headcount?' — a question AI almost always wins. Kevin also coaches sellers to proactively justify usage-based pricing by educating buyers on the real cost structure of AI: compute, inference, and energy costs mean that pricing must scale with usage in a way that perpetual-license software never did. Sellers who skip this education leave prospects feeling surprised or misled, which kills deals late in the cycle.

Summary

When a first meeting with a high-value prospect goes poorly, the worst move is to pretend it didn't happen. Kevin believes that directly acknowledging the failure at the top of the re-engagement is itself a differentiating signal — it demonstrates self-awareness, maturity, and the kind of founder quality that enterprise buyers respect. The acknowledgment then becomes a launchpad for a contrast narrative that shows how much the product, team, and company have evolved.

Methodology

Kevin's approach is to lean into the awkwardness of a prior failed meeting rather than sidestep it. The founder should open the follow-up by explicitly referencing what went wrong last time, owning it cleanly, and signaling that they're aware of exactly why it missed. This act of naming neutralizes the elephant in the room and positions the founder as someone with high self-awareness — a trait that builds trust with sophisticated buyers. The rest of the meeting should be structured as a contrast narrative: here is who we were then, here is who we are now, and here is why that delta matters to you specifically. The goal is not to apologize at length but to use the failure as evidence of the company's learning velocity. Done well, a re-engagement handled this way can actually create a stronger foundation than a clean first meeting ever would have.

Summary

Kevin treats compensation design as a strategic architecture problem, not a benchmarking exercise — every plan should align incentives with the specific behaviors and outcomes each role controls. The structure of variable pay (what it's tied to, how it's split, whether it escalates) is the mechanism that either reinforces or undermines the sales motion you're trying to build. Getting comp right means working from OTE outward, applying role-appropriate base-to-variable ratios, and pressure-testing the math with finance before any plan goes live.

Methodology

Kevin designs compensation from first principles by anchoring on OTE and working outward through four variables: base-to-variable ratio, quota multiple, commission rate, and what the variable is tied to. Each role has a distinct philosophy — BDRs and SDRs are paid on activity and pipeline generation (meetings booked), not closed revenue, because they don't control deal outcomes; AEs are full-cycle closers who should have roughly equal skin in the game (50/50 split), with quota set at 5x OTE as a baseline efficiency test; Account Managers are structured 80/20 with variable tied to net dollar retention rather than split renewal/expansion metrics, since expansion logically presupposes retention. For companies in early stages without a proven sales process, Kevin recommends a heavier base weighting (60/40 or 70/30) to attract candidates who aren't dependent on a mature pipeline. Tiered escalator structures — where commission percentages increase at stretch ARR thresholds — are Kevin's preferred mechanism for keeping top performers motivated past base targets without uncapped exposure risk to the company. Before any plan is finalized, Kevin requires cross-functional pressure-testing with finance to confirm that metrics are measurable, attributable, and won't create unintended consequences at scale.

Summary

Kevin's approach to outbound sales capacity is rooted in working backwards from revenue targets to define the exact activity volume required — calls, meetings, and pipeline — before making any hiring or tooling decisions. He treats call volume as the primary leading indicator of SDR health, and uses bottoms-up math to validate whether an outbound motion is worth building or scaling. Technology like predictive dialers is introduced only after the manual workflow is understood, as a multiplier of a proven process rather than a fix for an unclear one.

Methodology

Kevin begins every outbound capacity conversation by reverse-engineering the funnel from the revenue target down to daily activity: desired closed deals → opportunities needed → interested prospects → cold contacts required → dials per rep per day. This math often reveals that fewer reps than assumed are needed to hit the goal, and it anchors the entire hiring and tooling conversation in reality rather than intuition. Before introducing any automation, Kevin insists on observing the manual workflow to identify where time is actually going — only then does he recommend layering in predictive or power dialers to remove friction and multiply throughput. He uses daily call volume as the single most controllable and observable early metric for SDR performance, treating it as the upstream variable that makes all downstream outcomes (meetings, pipeline, revenue) possible. When connect rates decline, Kevin diagnoses it as a structural technology problem — call screening — rather than a skills issue, and prescribes dialer tooling to restore volume without adding headcount. For psychological sustainability in high-volume cold calling, Kevin reframes the success metric entirely: instead of chasing positive responses, reps set a daily rejection quota, making each 'no' a unit of progress toward a concrete goal.

Summary

Kevin's view is that momentum is the most fragile asset in any deal, and it lives or dies at the end of every conversation. Every call, meeting, or demo must close with a concrete, mutually agreed next step — not a vague promise to follow up — because the moment a deal loses forward motion, it begins to die. Leaving a meeting without a confirmed next step is not a neutral outcome; it is an active loss.

Methodology

Kevin treats the close of every conversation as a mini-commitment moment that determines whether a deal advances or drifts. His non-negotiable rule is to book the next meeting before the current one ends — not afterward, not via email, but in the room or on the call while both parties are present and engaged. He pairs this with a temperature-check question ('Is there anything giving you pause?') to surface hidden objections before they become silent deal-killers. For enterprise deals, Kevin introduces the concept of a Mutual Action Plan — a lightweight shared agreement that assigns homework to both sides, creating joint accountability and serving as a litmus test for genuine prospect engagement. When a prospect needs internal deliberation time, Kevin's response is not to wait passively but to immediately offer a specific follow-up call framed as 'Let's discuss your internal feedback together,' converting a vague pause into a scheduled commitment. He also applies this principle to the sequence of touchpoints — structuring discovery interviews, working sessions, and reference calls as a defined progression rather than jumping to a proposal, so each step builds mutual conviction before a number is put on the table.

Summary

Selling AI into conservative industries like insurance or healthcare requires deep alignment with the buyer's psychological worldview — one built on protection, risk reduction, and institutional caution, not innovation or efficiency gains. The 'AI replaces humans' narrative is an active deal-killer in these contexts; the winning frame is augmentation, objectivity, and consistency. Because these buyers are hyper-judgmental and have near-zero error tolerance, every element of the sales process — from messaging to demos to early deployments — must be tightly controlled and expectation-managed.

Methodology

Kevin's approach begins with diagnosing the psychological and institutional profile of the buyer before crafting any message. For conservative buyers — insurance companies, medical clinics — the primary motivation is risk avoidance, not gain-seeking, so FOMO-based or innovation-led narratives fall flat or actively create resistance. The correct entry point is to validate the buyer's existing frustration with inconsistency or opacity in the current process, which builds credibility and opens the door for the product to be positioned as bringing objectivity and reliability — not replacing expertise. Kevin then insists that all references to AI replacing workers be proactively removed from messaging, decks, and demos, replaced with language around augmenting practitioners and protecting the organisation. Finally, Kevin flags that these buyers are hyper-judgmental: a single visible AI error in a demo or pilot can permanently close the door, so sales and product teams must work together to ensure controlled conditions, calibrated expectations, and a deployment environment where early-stage performance matches the promise made in the sale.

Summary

When a company operates two distinct business units — such as a media business and a SaaS platform — treating them as a single sales motion is a strategic mistake. Each unit has different buyer profiles, deal structures, and revenue dynamics that create natural conflicts when shared across the same sales team. Kevin's view is that separation is not optional: it is the structural prerequisite for either unit to scale effectively.

Methodology

Kevin begins by surfacing the full sales landscape during discovery, probing for whether a founder is actually managing multiple distinct sales motions under the assumption they are one. Once he identifies this — often through deal size discrepancies, different buyer types, or uneven rep focus — he names the structural conflict explicitly. In the case of a media business alongside a SaaS platform, Kevin diagnoses the root issue as a prioritization problem baked into the team's incentive structure: reps will default to whichever product closes faster or pays more. His prescription is to treat each unit as a separate coaching engagement with its own go-to-market strategy, hiring plan, and sales process. He recommends hiring dedicated SaaS sales reps rather than retraining media reps, acknowledging the cost but framing it as non-negotiable for platform growth. This separation also allows Kevin to coach the founder on two distinct challenges rather than blending them into a single, diluted strategy.

Summary

Kevin teaches that every B2B sales call must follow a deliberate, non-negotiable sequence — intro, discovery, summary, story/pitch, demo, and questions/objections — where each stage creates the conditions for the next. The summary step is the most commonly skipped and most consequential: reflecting the prospect's own words back to them before pitching transforms a generic presentation into a tailored conversation. For multi-stakeholder deals, this full sequence must be run independently with each stakeholder rather than collapsed into a single group meeting.

Methodology

Kevin prescribes a five-to-six-stage call architecture as the backbone of any repeatable sales motion. Stage one is a short, credibility-dense intro — lead with the most impressive signal fast, not a lengthy biography. Stage two is layered discovery: ask questions that peel back problem layers, surfacing both known pain and unknown unknowns, and never pitch during this phase. Stage three — the most skipped — is the summary: verbally recap what you heard and explicitly ask the prospect if your understanding is correct, inviting corrections and additions; this step builds trust, confirms alignment, and signals genuine listening. Stage four is the story/pitch, which must be built in real-time from discovery findings using the prospect's own language and name, never templated. Stage five is the demo, run as evidence of the story just told — not as a feature tour. Stage six is questions and objections, treated as a second discovery loop rather than a defense exercise. For complex B2B deals with multiple buyers, Kevin requires this full sequence to be repeated independently with each stakeholder, not compressed into a single group session. He also advises extending call slots from 30 to 45 minutes, since compressed calls force a trade-off between discovery depth and demo quality, weakening both.

Summary

Enterprise deals are won or lost in how you structure meetings across multiple stakeholders — not in a single pitch to a single champion. Kevin's view is that every high-stakes meeting requires pre-work to map stakeholder roles and motivations, a sequenced in-meeting structure that leads with discovery before solution, and post-meeting multi-threading to build individual relationships with every decision-maker. The goal of any given meeting is rarely to close — it's to advance shared understanding, surface hidden objections, and expand your internal relationship portfolio.

Methodology

Kevin's approach begins before the meeting: research all attendees, map distinct value propositions to each stakeholder (executives care about margins and board narratives, operators care about efficiency, end users care about workflow), and use your internal champion to surface objections and political dynamics in advance. In the meeting itself, Kevin prescribes a strict sequence: open with a tight personal introduction, then shift immediately to structured listening and discovery — asking what executives have already heard internally, what problems keep them up at night, and what their top organizational priorities are — before any solution or pitch is introduced. For group meetings with multiple stakeholders, run introductions that surface each person's role and concerns, conduct group discovery, summarize what you've learned back to the room, then deliver a pitch framed entirely around what the group just told you. Kevin treats new or expanded stakeholder groups as a fresh first call regardless of how far along the deal is — he never assumes shared context, and always re-validates the problem statement before advancing. After the meeting, Kevin requires personalized individual follow-ups with each attendee, explicit multi-threading to avoid single-champion dependency, and where appropriate, a mutual action plan with clear timelines and deliverables to formalize commitment and demonstrate professionalism.

Summary

Kevin treats the pilot not as a courtesy afforded to hesitant buyers but as a precision instrument — its structure, sequencing, pricing, and success criteria must all be designed deliberately before it begins. A poorly structured pilot leaks leverage: it anchors future pricing at discounted rates, creates ambiguity about what success looks like, and lets deals drift without a clear path to conversion. The goal is to make progression from trial to paid feel inevitable and low-risk to the buyer, while preserving the seller's commercial position throughout.

Methodology

Kevin's pilot framework begins before the contract is signed: confirm genuine product preference over competitors, align verbally on scope, pricing, and structure before any paper is exchanged, and ensure the right commercial counterpart — not just the technical buyer — is involved in the terms conversation. The pilot itself should be tiered to match buyer risk tolerance (free trial → paid pilot with exit clause → annual contract), with each tier designed to screen for a specific customer behavior and advance commitment naturally. At kickoff, lock in objectives, KPIs, timeline, and mutual action plan with assigned owners on both sides — get stakeholders to articulate success criteria in their own words rather than being told what success looks like. During the pilot, maintain a regular check-in cadence and keep executive sponsors engaged, not just day-to-day contacts; a signed contract is a floor, not a ceiling — churn is still possible if the product experience fails. On pricing, never apply group or enterprise-tier discounts during a pilot without an explicit full-rollout commitment attached, as doing so permanently anchors future negotiations at the discounted baseline; instead, charge retail during the pilot and apply tiered discounts retroactively upon expansion. When deals stall or timelines slip, use tactical structures — a single-location pilot, a shifted start date, a month-to-month continuation post-pilot — to maintain momentum and revenue continuity rather than going dark or renegotiating the core deal.

Summary

Kevin treats the POC as a discrete, high-stakes sales stage that must be engineered for conversion before it begins — not a technical evaluation left to drift. The foundation is a co-created success document with measurable KPIs, explicit commitment from the prospect that success leads to a contract, and a commercial path that accounts for budget cycle timing. POCs fail not because products don't work, but because of process failures: vague criteria, scope creep, low customer engagement, and no pre-agreed closing motion.

Methodology

Kevin's POC methodology has four interdependent components. First, define desired outcomes and measurable KPIs collaboratively with the customer before the POC begins — use a shared document that both sides own, so success criteria are unambiguous and not movable at the end. Second, get explicit commitment upfront that a successful POC leads to a contract; if the prospect won't confirm this, treat it as a disqualification signal. Third, establish a mutual action plan with assigned owners, milestones, and a regular check-in cadence so customer engagement stays visible and accountability is shared — low engagement mid-POC is a leading indicator of a deal at risk, not just an operational inconvenience. Fourth, address commercial timing proactively: align the contract start date to the customer's budget cycle rather than the POC end date, and build bridge mechanisms (POC-as-Phase-1 structure, free trial extensions) to prevent deals from dying in the gap between POC completion and budget availability. Across all of this, Kevin also advises proactively layering in additional product capabilities beyond the minimum success criteria during the POC to build appetite for a larger contract, and when running parallel POCs within related entities, to treat each as an independent stakeholder environment with its own scope, KPIs, and decision-makers rather than assuming a win in one transfers automatically.

Summary

Sales compensation and quota design must be deliberately matched to the revenue model — bookings-based comp is the SaaS default, but businesses with payment risk, accrual accounting, or variable spend patterns need more nuanced structures. The core principle is that incentives should reflect the true risk profile and strategic value of each revenue type, not collapse everything into a single number that distorts rep behavior. Simplicity is a virtue: when complexity creates confusion across the sales team, that is a signal to restructure around cleaner, more intuitive targets.

Methodology

Kevin starts by diagnosing the business's payment risk profile, accounting model, and booking cadence before recommending any comp structure — there is no universal answer. He distinguishes between new business bookings (higher weight, higher risk, tied to new logo acquisition) and accrual/expansion revenue (lower weight, more predictable, tied to existing-base growth), and insists these be tracked and compensated separately to avoid perverse incentives. For new business specifically, he anchors the definition to the full 12-month contract value at close — not land-and-expand within the same year — to prevent reps from rushing closes or conflating expansion credit with acquisition credit. He also pushes sales leaders to build a formula estimating what percentage of bookings signed in a given period will actually accrue as revenue within the current fiscal year, enabling more accurate downstream forecasting. On cadence, Kevin advocates for quarterly targets over monthly once a business matures, on the grounds that monthly quotas push reps toward fast-close, smaller deals rather than strategic, higher-value opportunities. Throughout, he treats simplicity as a design constraint: if the team cannot internalize the target structure, it will not drive the behavior it was built to incentivize.

Summary

Kevin's core belief is that most sales team dysfunction is a structural problem, not a people problem. When reps are confused, underperforming, or stepping on each other, the root cause is almost always missing architecture — unclear role separation, mismatched lead supply, or blurred ownership across segments and functions. His coaching consistently moves founders and sales leaders toward explicit design: who sells what, to whom, with what support, and measured how.

Methodology

Kevin begins by diagnosing whether underperformance is structural or individual, using quota attainment rates, lead source audits, and role clarity reviews as diagnostic tools. He then builds explicit segmentation logic — enterprise vs. mid-market, media vs. SaaS, new business vs. renewals vs. account management — so that each function has unambiguous ownership and isn't competing for the same rep bandwidth. Where roles are conflated (e.g., AEs owning renewals, or media reps expected to sell SaaS), he pushes for clean separation and, if necessary, dedicated hires. He provides founders with a foundational management cadence — pipeline review, rep performance review, and standup rhythms — as the operating infrastructure that makes structural clarity durable over time. When founders re-engage directly in sales, he gives them a structured protocol: review target accounts together, align on what good looks like, and be prescriptive rather than passive. Throughout, he treats lead source stability as a critical variable — disrupting a rep's primary pipeline mechanism without transition support is a structural risk, not a performance test.

Summary

Most founders don't fail at follow-up because they lack time — the actions themselves take seconds to minutes — they fail because they lack a system, and without a system, psychological friction (discomfort, procrastination, unclear next steps) wins every time. The fix is structural: a recurring 15-minute weekly calendar block dedicated solely to follow-up removes the decision fatigue that causes avoidance. Every conversation, whether from a conference, demo, or pitch, must exit with a named next step, a named owner, and a named timeframe — or the deal stalls.

Methodology

Kevin diagnoses poor follow-up not as a knowledge or time problem but as a systems and psychology problem — founders know they should follow up but without a dedicated slot, every follow-up requires a fresh decision, and friction compounds until it doesn't happen. His structural fix is a recurring 15-minute weekly calendar block that converts follow-up from an intention into a scheduled behavior. He also reframes the goal of conference and post-meeting follow-up: it is not to close, but to stay top-of-mind and secure the next conversation. Beyond cadence, Kevin coaches founders to exit every call — demos, pitches, discovery calls — with a concrete next step: a named action, a named owner, and a named timeframe, creating a logical sequence that keeps the founder in control of deal momentum. He models this discipline in his own sales process, treating it as proof-of-concept for the methodology he coaches. The compounding failure mode he targets is founders who meet multiple qualified contacts at conferences but follow up with only one or none — not because they don't value the relationships, but because they have no system to activate.

Summary

Kevin's core sales philosophy is that skeptical or price-sensitive prospects should never be pushed to commit — they should be invited to experience value first. The free session, trial engagement, or no-charge deliverable is not a concession; it is a deliberate closing mechanism that shifts the decision from 'do I trust this?' to 'did that work?' Kevin deploys this across a spectrum: free sessions, partial refund guarantees, unbundled pricing, and live deal outcomes used as proof-of-concept.

Methodology

Kevin reads the prospect's resistance signal first — whether it's price sensitivity, distrust, inability to articulate the problem, or fear of a large upfront commitment — and selects the minimum viable entry point that keeps the relationship moving without forcing a premature buy decision. His primary tool is the free coaching session, which he ties to something concrete and time-sensitive in the prospect's world (an upcoming call, an active deal, a pilot to close) so the session has immediate stakes and clear ROI visibility. For cash-constrained founders, he offers a no-charge deliverable (a cold email campaign, a team session) or a refund guarantee after month one, converting a financial risk into a low-stakes trial. When a prospect can't articulate what they'd get value from, Kevin uses the live call itself as the proof — showing, not telling, that value emerges from what the founder doesn't yet know they don't know. He is also honest about fit: when a founder genuinely cannot afford him, Kevin acknowledges it, offers what he can for free (an intro, a referral), and moves on rather than over-investing in a low-probability close. The throughline across all variations is sequencing: demonstrate value first, then ask for the commitment.

Summary

Kevin treats warm introductions and referrals as the highest-leverage growth mechanism available to early-stage founders — far outperforming cold outreach in response rate, trust transfer, and sales cycle speed. He approaches his own network as a coaching tool, proactively making targeted introductions to customers, investors, and operators rather than waiting to be asked. Referrals are not a passive afterthought but a systematic, time-sensitive, and relationship-respecting practice with distinct protocols depending on the context.

Methodology

Kevin's referral methodology operates at three levels. First, timing: the optimal window for a referral ask is 24–72 hours post-close, when the customer feels most validated; waiting even a week dramatically reduces willingness to advocate. Second, format: referral asks should be made on live calls rather than email because real-time conversation forces commitment and eliminates procrastination for both parties. Third, depth: when a contact says they can't think of anyone, Kevin prescribes a sustained two-to-three minute brainstorming exercise — describe the specific target persona in detail and keep the conversation alive, because referral ideas surface only once the brain is primed, similar to how design students only produce truly creative concepts after exhausting the obvious ones. Beyond customer referrals, Kevin maps the full referral ecosystem: investor networks should be approached as referral sources rather than sales targets; advisor relationships should be formalized with equity so they become publicized, credible sales channels; and complementary vendors already selling into target segments should be cultivated as partnership introduction pipelines. Critically, Kevin protects relationship integrity by never allowing salespeople to approach potential investors for sales introductions without explicit CEO involvement, and he gatekeeps his own introductions until he has personally reviewed a product so that every referral he makes is targeted and reputation-preserving.

Summary

Kevin's view is that AI should be deployed where interactions are transactional, informational, or high-volume and low-complexity — top-of-funnel qualification and long-tail customer coverage — while human reps and CSMs own the high-stakes, nuanced, trust-dependent work. The boundary isn't about cost efficiency alone; it's about matching the capability of the tool to the complexity of the interaction. Misallocating humans to low-value, repetitive coverage is as much a strategic error as misallocating AI to emotionally complex conversations.

Methodology

Kevin starts by validating any skepticism about AI rather than overselling its capabilities, which builds credibility before making the strategic case. He then maps the customer or prospect base into a coverage model — often a bell curve — and asks where human attention genuinely moves outcomes versus where it is being wasted. AI is positioned not as a replacement but as a coverage mechanism for the segments that would otherwise go underserved or consume disproportionate human bandwidth. He connects tooling recommendations (such as Hook for CS churn and upsell signals) directly to the coverage strategy, so the tool choice follows the model rather than driving it. The result is a clear operating principle: humans focus on complexity and relationship depth, AI handles volume and signal detection. This framing also gives the team a defensible internal narrative — they are not cutting corners, they are optimizing where human judgment actually compounds.

Summary

Enterprise deals — whether late-stage contracts or competitive RFPs — are rarely won on merit alone. Kevin's core view is that every high-stakes deal requires two parallel tracks: a formal operational track (persistent follow-up, compliant submissions, specialist support) and an informal influence track (executive sponsors, investor networks, backchannel relationships). Startups that rely only on the formal process will consistently lose to incumbents who own the relationships.

Methodology

Kevin's enterprise deal framework starts with ruthless qualification: for RFPs, review the questions first to assess whether a realistic path to winning exists before committing resources — most RFPs are written around a preferred vendor and cannot be won without prior relationship. If you proceed, the formal track must be competitive on its own terms: use specialist firms that know the RFP process, answer conditional questions with formula-based pricing where needed, and ensure the written submission is airtight. Simultaneously, run an informal track built on backchannel development with key decision-makers — identify who influences the final call and open relationship lines outside the formal process. For late-stage contracts that stall, layer in top-down pressure by activating investor relationships: having a firm like Andreessen Horowitz reach out directly to a CTO or executive is a legitimate and powerful acceleration tool. Operational persistence matters throughout — weekly direct follow-ups with the SVP-level owner, including around holidays when deals most commonly slip into the next quarter. The two tracks are not optional — the formal track gets you in the room, the informal track wins the deal.