Methodology Playbook

Summary

Kevin's core belief is that outbound and inbound are distinct motions with different prerequisites, economics, and sequencing requirements — and conflating them is one of the most common early-stage mistakes. Inbound must be stable and optimized before outbound is layered on, and outbound itself must be validated as an experiment before it is scaled. Both channels serve a purpose, but the decision of when and how to build each is a function of ARR stage, product maturity, team capacity, and whether the ICP is truly known.

Methodology

Kevin begins by diagnosing where the company's current pipeline actually comes from and whether the existing motion — inbound, network, or early outbound — is stable and understood. He applies a sequencing rule: inbound health is a prerequisite gate before outbound investment, and outbound itself must be treated as a structured experiment before it becomes a scaled system. For outbound, he distinguishes between two architectural tracks — high-volume automation-driven prospecting (e.g., Clay-based intent signals) and high-touch account-based selling for strategic targets — and insists these be run as separate plays with different metrics. He calibrates his recommendations tightly to stage: below $1M ARR with strong inbound, he actively discourages outbound infrastructure; above that, he pushes founders to build a repeatable outbound machine as both a revenue lever and proof of scalability for investors. When outbound has failed, his first move is always root-cause analysis — targeting, messaging, or sequence — before any rebuild begins, and he reframes persistent outbound failure not as a tactics problem but as a signal that the ICP hasn't been truly identified.

Summary

Kevin's view is that channel strategy is not about breadth — it's about sequence and concentration. Early-stage companies must first validate customer insight before selecting any channel, then identify the single highest-leverage channel and master it at an elite level before expanding. The instinct to diversify channels is almost always a mistake; doubling down on what's already working produces compounding returns that spreading effort cannot.

Methodology

Kevin's channel methodology operates in four stages. First, he insists on sequencing correctly: customer insight must precede strategy, and strategy must precede channel selection — jumping straight to channel tactics is the most common and costly early GTM mistake. Second, he applies a stage-gate to channel types: high-leverage, low-effort channels (referrals, warm intros, existing networks) must be exhausted before escalating to lower-leverage, higher-effort channels like cold outreach, and channel partnerships or resellers should only be pursued after meaningful product-market fit is established — typically one to two years into the business. Third, when evaluating which channels to prioritize, Kevin listens for concrete early signals — even a single SQL from a new channel — and treats founder-led early wins as proof-of-concept that justifies decisive resource concentration rather than a portfolio approach. Fourth, once a winning channel is identified, Kevin pushes for structural commitment: not just effort concentration but team restructuring so that roles, incentives, and resources are explicitly aligned to the channels driving growth. Throughout, he maintains one consistent counterbalance — before abandoning a previously productive channel entirely, assess whether it has untapped surface area in new verticals or new partner relationships.

Summary

Kevin pushes early-stage founders to make a deliberate, committed choice between enterprise and mid-market rather than pursuing both simultaneously. He frames enterprise not merely as a larger deal size, but as a strategic anchor — the segment that generates stickier revenue, stronger referrals, and compounding long-term opportunity. The longer sales cycle is not a liability to be avoided but a known cost worth paying for the higher-quality customer relationships it produces.

Methodology

Kevin first diagnoses when a founder is diluting sales effort by straddling two distinct customer segments without a clear strategic rationale. He surfaces the hidden cost of this ambiguity: different metrics, different sales motions, and divided attention that weakens execution in both segments. He then reframes the enterprise sales cycle — often seen as a problem — as an investment in higher-contract-value, longer-tenure customers who validate the company and open doors through referrals. He coaches founders to treat enterprise as a separate track with its own pipeline metrics and process, not a scaled-up version of mid-market. The outcome Kevin pushes toward is a clear, documented commitment to enterprise as the primary segment, with mid-market deprioritized or deferred until the enterprise motion is proven.

Summary

Kevin's core view is that segment selection is a strategic decision, not a default — founders must explicitly map the ceiling of their addressable market at each price tier, stress-test customer longevity, and match deal size to sales cycle realities. The mid-market is consistently his recommended proving ground: deals large enough to signal real enterprise value, small enough to close without 12–18 month cycles. Staying in the wrong segment — whether too small (unstable early-stage startups), too large (entrenched enterprise), or too niche (saturating premium verticals) — is a structural ceiling on growth, not a tactical problem.

Methodology

Kevin begins by diagnosing whether a founder's current segment is a strategic choice or an accident of early traction — often it's the latter. He then constructs a quantified view of each viable segment: estimated deal sizes, total addressable customer count, average sales cycle length, and customer survival likelihood. From this, he identifies structural ceilings (e.g., F1 teams are self-sufficient, early-stage hardware startups fail at high rates, education moves through committees) that make certain segments unscalable regardless of execution quality. His default recommendation is to anchor in mid-market first — typically $10K–$100K ACV depending on the vertical — to build lighthouse references and prove unit economics before attempting to move upmarket. When a competitor already owns the top of the market, he prescribes a tiered timing strategy: win mid-market now to build credibility, then re-engage large accounts at renewal windows. For companies with a single low-ACV product, he pushes for a product roadmap that introduces higher-value offerings every 6–9 months, paired with a dedicated sales motion for each segment, to avoid the trap of scaling volume instead of value.

Summary

In a crowded data annotation market, most vendors are self-serve or semi-managed — making a fully managed service offering a rare and powerful differentiator. Kevin coaches teams to map the competitive landscape clearly and own the specific dimensions where they genuinely win: high-touch project management, annotator scale, and pricing. Rather than trying to compete everywhere, the goal is to articulate precisely where you beat Scale AI and where Figure 8's higher price and weaker tooling creates an opening.

Methodology

Kevin draws out the full competitive landscape — in this case Playment, Scale AI, and Figure 8 — to give the team a shared visual of who they are fighting and on what terms. He identifies the structural differentiator first: only four players offer a fully managed solution, which immediately narrows the real competitive set. From there, he coaches the team to lean into high-touch engagement and project management quality as proof points of the managed model, not just a feature claim. Pricing is positioned as a deliberate strength against Figure 8's premium, and against Scale AI the framing shifts to service quality and reliability. The team is coached to be honest about where they don't win — avoiding over-claiming — so that the wins they do assert carry credibility with buyers.

Summary

Kevin views conferences as a high-leverage, non-optional channel for early-stage B2B founders — but only when approached with the right intent and execution. The strategic default for founders who are still validating their go-to-market is to attend, not exhibit: show up, walk the floor, and have targeted conversations without the cost and distraction of running a booth. When the attendee mix doesn't match the ICP, the goal shifts further — from pipeline generation to structured market discovery, relationship seeding, and intelligence gathering.

Methodology

Kevin begins by drawing a hard line between attending and exhibiting, treating them as distinct strategic choices: exhibiting signals a level of market readiness and budget allocation that early-stage companies haven't yet earned. For founders still building pipeline, he positions conference attendance as the higher-leverage, lower-cost mode — one-on-one conversations, floor walks, and targeted relationship-building over booth overhead. When the conference audience doesn't perfectly match the ICP, Kevin reframes the goal entirely: stop expecting to close deals and start treating every conversation as a discovery interview to surface pain points and validate assumptions. On execution, Kevin is concrete and measurable — he pushes founders to pre-book meetings before the event rather than relying on chance encounters, set a daily target of at least 20 meaningful conversations and business card exchanges, and follow up with every contact promptly. At-event differentiation matters too: Kevin advises using visual anchors (bright colors, distinctive attire), memorable giveaways, and participatory demo mechanics — like a live AI challenge — to create sensory and competitive hooks that cut through the blur of back-to-back vendor meetings. The overarching frame is that conferences generate the kind of trust and serendipitous pipeline that cold digital outreach cannot replicate, and avoiding them due to cost is a false economy when other channels are struggling.

Summary

For early-stage startups selling physical or tactile technology, the product itself is the most powerful sales asset — and most founders dramatically underleverage it by defaulting to digital outreach. Kevin's view is that in-person demonstrations create a qualitative shift in buyer conviction that no email sequence can replicate. The go-to-market motion should be built around getting the product in front of prospects physically, not scaling top-of-funnel volume.

Methodology

Kevin diagnosed Vern Robotics as under-leveraging their most differentiated asset: a physical, visually compelling product that skeptics can be converted by in real time. His recommended GTM shift was to move the primary outbound motion from email sequences to presence-based selling — either bringing a demonstration robot arm directly to prospect sites or organizing local showcase events where potential customers can see the technology operate. The core logic is that physical proof of concept eliminates the skepticism that written or virtual communication cannot overcome, compressing the sales cycle by removing a layer of uncertainty. This approach also generates higher-quality pipeline because prospects who engage after a live demo are already meaningfully qualified. Kevin framed this not as a temporary tactic but as the foundational GTM motion for the early stage, before the company has the brand equity or case studies to sell without presence.

Summary

A scalable revenue org requires clearly separated, dedicated functions — Sales, CS, BDR, RevOps, Solutions Engineering, and Product Marketing — with explicit ownership and aligned reporting. The single most dangerous structural mistake is misaligning Sales and Customer Success under different leadership, which creates handoff failures and conflicting incentives. Org design should follow ICP clarity and functional logic, not just headcount availability.

Methodology

Kevin begins by running a structured diagnostic: he has founders or revenue leaders walk through each person's current responsibilities, then surfaces the symptoms — role overlap, split accountability, and leadership gaps — and names them explicitly as scalability risks before proposing any redesign. He then maps the org against a canonical B2B revenue structure with discrete functions (enterprise AEs for net-new, AMs for expansion, CS for value delivery, RevOps for process and data, and marketing owning growth channels), using concrete examples from his own experience at companies like Fleet and Close to make the model tangible. On the CS side, Kevin separates retention and expansion into distinct roles with distinct metrics, arguing that blending them creates the wrong behavior — CS managers over-investing in churning accounts while underselling into healthy ones. For reporting structure, his rule is to align teams around the outcome they most directly influence: CS and Sales under the same CRO, growth product under marketing when SEO or inbound is the primary lead channel. When structural changes have revenue-wide implications — comp design, headcount sequencing, team splits — Kevin insists the CRO is a co-creator of the decision, not a recipient of the finished recommendation. Finally, he sequences the build correctly: establish the senior leadership layer first, then hire underneath it, so strategy precedes execution at every stage of growth.

Summary

Kevin treats design partnerships not as informal pilots or discounted sales, but as a structured, intentional program that converts early-stage vulnerability (unfinished product, uncertain value) into a legitimate value proposition. The design partner is recruited as a co-developer and advisor, not closed as a customer — which lowers friction, accelerates product-market fit, and builds durable commercial relationships before a full sales motion is warranted. The program must be scoped carefully: right number of partners (2–6), right qualification criteria, right commercial structure, and the right sequencing between operational and aspirational clients.

Methodology

Kevin's design partnership approach operates in distinct phases. First, before a product exists, founders should offer free design partnerships in exchange for deep access to workflows, usage data, and honest feedback — framing this as a trade, not a favor. Once something is built, even partially, the program should be rebranded as a formal R&D Partnership with defined partner obligations (providing parts, facilities, dedicated staff, feedback cycles) in exchange for discounted pricing, preferential roadmap influence, and exclusivity. Kevin advises maintaining a small portfolio of 2–6 partners rather than over-investing in one, with geographic clustering where possible to make on-site presence economically viable across multiple accounts simultaneously. Partner qualification is a two-way assessment: the right partner demonstrates enthusiasm, internal resource availability, and a track record of pioneering — the wrong partner drains the team. Commercial structures should stay clean for VC-backed companies: no equity to customers, no revenue sharing — instead use referral commissions or SAFE investments. Finally, Kevin emphasizes sequencing: at least one design partner must be an operational, revenue-generating business, not just a capital-raising early-stage firm, to generate credible MVP validation signals.

Summary

Kevin's foundational GTM principle is that early-stage B2B founders consistently over-invest in breadth and under-invest in depth. A deliberately small, curated list of target accounts — whether 20, 40, 50, or 100 — produces higher-quality signal, better conversion, and faster learning than any high-volume, generic outbound motion. The constraint is the feature, not the bug: scarcity of targets forces personalization, forces research, and forces the founder to actually understand whether the market exists.

Methodology

Kevin starts by diagnosing the root cause when pipeline is thin: almost always, it is not an outreach volume problem but an ICP definition problem. Until the ideal customer profile is tight enough to produce a named, finite list, more outreach just generates more noise. Once the list is defined, he prescribes outreach intensity that scales inversely with TAM size — the smaller the market, the higher the personalization required per account, up to and including personalized video, physical direct mail, gifts, and in-person visits. He layers in geographic concentration as a force multiplier: by anchoring early efforts in one region (e.g., the Bay Area), founders compound relationship density, earn referrals faster, and build a reputation that spreads organically within a networked community. He also enforces vertical discipline — proactive outbound should target only fast-moving verticals where buyers have authority and appetite, while warm inbound from slower verticals (e.g., insurance) can be pursued opportunistically on the buyer's timeline. When signal emerges that one vertical or segment is outperforming, Kevin treats it as a prescriptive constraint, not just interesting data: collapse the ICP immediately and run a time-boxed sprint (e.g., 2 months, 20 meetings, banking only) to validate or invalidate the thesis before expanding again.

Summary

Founders must remain personally anchored in high-value but slow-burn GTM motions like partnerships and early customer success — but they also need to recognize when their personal involvement is creating a scaling bottleneck. The trap is either delegating too early to an under-resourced generalist, or never delegating at all and starving pipeline development. Kevin's view is that founders must be deliberate about where their presence adds irreplaceable relationship credibility versus where it is consuming capacity that should be redirected to growth.

Methodology

Kevin identifies a recurring early-stage pattern where high-touch, relationship-dependent GTM motions — partnerships and customer success chief among them — get mishandled in one of two ways: fully delegated to a junior or over-extended operator before the relationship foundation is established, or retained entirely by the founder until it creates a capacity crisis. His diagnostic is to pressure-test each function by asking whether it is receiving focused, senior-level attention proportional to its strategic value. For partnerships specifically with enterprise platforms like Snowflake or AWS, Kevin's model is that the founder must anchor the executive relationship while an operator handles coordination and follow-through — not the reverse. For founder-led customer success, he validates the quality signal strong pilot conversion rates while surfacing the structural cost: if the founder is the de facto CSM for every customer, pipeline development is being starved. The resolution is not to abandon high-touch engagement but to sequence the transition explicitly: recognize the bottleneck, plan the handoff, and protect founder time for the activities only the founder can do, particularly prospecting and executive-level relationship development.

Summary

Kevin's view is that outbound channel selection — whether for sales prospecting or recruiting — must be matched to the stage, target, and message quality of the sender. LinkedIn is the right default channel for early-stage founders because it's lower friction and more personal than cold email, but it has a ceiling and must eventually be layered with multi-channel strategies, warm introductions, and credibility-building content. The root cause of most outbound failure is not the channel itself but a deficit in insight, personalization, and genuine value — fixing the message always comes before fixing the volume.

Methodology

Kevin begins by separating channel failure from message failure: when outbound isn't working, the instinct is to blame the channel or increase volume, but Kevin consistently reframes this as a positioning and insight problem. His prescribed sequence is: (1) earn the right to outreach by deeply understanding the prospect's specific context, then (2) lead every message with benefits first and structure it around five components — who you are, what you do, why it's relevant, your credibility, and a clear CTA — with extreme personalization on LinkedIn (quoting prospects' own content or achievements). For channel selection, he recommends LinkedIn connection requests over cold email for early-stage founders without brand recognition, with InMail as an alternative to bypass the connection step entirely, and LinkedIn ads as a retargeting nurture layer for high-ICP prospects who haven't responded. As volume becomes a constraint, Kevin applies outbound sales logic to recruiting — treating candidate sourcing as a proactive outbound motion using LinkedIn — and prescribes calendar-blocking dedicated hours, multi-channel search strategies combining personal networks, board member referrals, contingency headhunters, and public social posting. When LinkedIn alone plateaus (typically around $350k ARR), Kevin signals that the founder must layer in more systematic multi-channel outbound and leverage existing customers for referrals and case studies rather than continuing to rely on a high-effort, non-delegable personal motion.

Summary

Early-stage AI companies should avoid capital-heavy strategies like acquisitions and instead build trust through low-risk, experience-first entry motions — parallel POCs, structured trials, and high-engagement bootcamps. The common thread is that AI buyers are often not price-skeptical but confidence-skeptical, so the GTM motion must generate proof of value through direct experience. When an unconventional entry motion like a bootcamp generates consistent enterprise pipeline, it should be treated as a repeatable playbook, not a one-off tactic.

Methodology

Kevin evaluates each AI founder's GTM approach by first asking whether the proposed motion matches the buyer's risk tolerance and the company's stage — rejecting strategies like acquisitions as premature before Series A/B. For enterprise buyers already using an incumbent vendor, he prescribes a parallel POC that runs alongside the existing solution, generating side-by-side proof of speed and quality rather than asking the buyer to make a disruptive switch. For buyers with trust or confidence gaps around novel AI outputs, he recommends time-boxed trials with limited free credits, reframing the objection from 'the price is too high' to 'the buyer needs to see it work.' When an experimental motion like a live AI bootcamp produces strong, consistent enterprise engagement — as with DeepMind, Unilever, and the FT — Kevin coaches founders to recognise that as validated signal and to immediately systematize it into a repeatable, scalable GTM motion. Across all three motions, the underlying logic is the same: reduce the buyer's perceived risk of the first step, generate comparative or direct proof of value, and convert that experience into commercial confidence.

Summary

Kevin's foundational GTM belief is that early-stage startups must ruthlessly concentrate on a single vertical, use case, and geography before expanding — not because breadth is wrong long-term, but because depth is the only way to build credibility, pattern recognition, and compounding referral leverage. Spreading focus across multiple segments, geographies, or product bets simultaneously is not a growth strategy; it is a disguised form of indecision that prevents a company from winning anywhere. The beachhead is not a limitation — it is the mechanism by which every successful expansion is eventually funded.

Methodology

Kevin diagnoses premature expansion as a psychological problem first and a strategic problem second — founders spread focus because of FOMO, sunk-cost attachment to parallel bets, or discomfort with constraint, not because the market demands it. His corrective framework is to force a binary choice: identify the single segment where the strongest signal already exists (live deal, most traction, clearest pain), then fully divest from everything else, even after prior investment. To validate a new vertical before committing, he prescribes a lightweight test: generate 4–5 vertical hypotheses ranked by criteria including problem severity, buyer urgency, ability to pay, sales cycle length, competitive landscape, and team expertise match, then run 5 discovery conversations per vertical — not to pitch, but to seek advice and establish message-market fit. Once a beachhead is chosen, he applies the bowling alley model: win the first pin completely, earn transferable credibility, then roll into adjacent lanes using the same ball — either deepening within the segment (larger deal sizes, more applications) or expanding laterally to verticals that share structural DNA. Geographic focus follows the same logic: own one city or region until referrals flow naturally and the brand is synonymous with the category there, then expand. The test for when it is safe to expand is simple — can the current beachhead generate multi-million ARR on its own? If yes, there is no strategic justification to dilute focus yet.

Summary

When a startup's core business depends on a dominant platform partner, the power imbalance is real but not insurmountable — the key is to enter every negotiation with explicit leverage, concrete asks, and a rehearsed exit plan. Kevin's view is that large platform partners (Zoom, Microsoft, Salesforce) are not adversaries to appease or benefactors to trust, but strategic actors pursuing their own goals — and founders must understand those goals deeply before walking into any room. The founder's job is to make Recall.ai indispensable to the partner's ambitions while simultaneously protecting against the scenarios where the partner pivots, copies, or acquires.

Methodology

Kevin's approach begins with pre-meeting intelligence: founders must identify the partner's internal motivations and goals before positioning — what Zoom, Microsoft, or Salesforce is optimizing for should determine how Recall.ai shows up, whether as a vendor, a strategic partner, or an acquisition target to reframe as a partnership. He then coaches founders to convert any inbound interest from the partner (e.g., Zoom wanting Recall.ai's desktop SDK) into explicit negotiating currency, anchoring high on pricing, protections, and commitments with the expectation of concession. Contractual clarity is non-negotiable: timeline, roadmap commitments, and pricing floors (especially protections against the partner undercutting the reseller relationship at smaller volume) must be locked before any commitment is made. Kevin treats platform risk as a planning assumption rather than a hypothetical — founders should know exactly how their customers would be routed to alternative solutions if the partnership soured, and that exit plan must exist before signing. Where acquisition interest surfaces, Kevin reframes it toward deep partnership first, preserving founder independence while still delivering the strategic value the acquirer seeks. Finally, he applies basic operational hygiene — don't discuss sensitive negotiation strategy on the platform you are negotiating with.

Summary

The Palantir sales model is widely misunderstood — it is not simply about deploying engineers on-site, but about a disciplined pre-contract sequence: enter through C-suite, build a working prototype in the customer's real environment, and make value undeniable before procurement ever begins. This approach collapses the traditional 18+ month enterprise sales cycle by bypassing middle-management bottlenecks and IT security timelines through executive mandate. When executed correctly, deep on-site embedding creates stakeholder addiction across departments, turning contract expansion into an organic outcome rather than a negotiation.

Methodology

Kevin's approach starts with a hard correction: most founders who cite Palantir as inspiration only copy the surface (on-site engineers) and miss the underlying logic. The real model has three distinct pre-contract phases — executive entry, working prototype delivery, and multi-stakeholder value demonstration — and they must happen in that order. Phase one is securing C-suite sponsorship through warm referrals or direct outreach, which provides the mandate that overrides IT procurement timelines. Phase two is conducting a rapid on-site workshop — ideally one to several days — where engineers build a live, customised prototype using the prospect's actual workflows, not a generic demo deck. Phase three is extending that on-site presence to surface use cases across multiple departments, deliberately creating dependency and addiction before any formal deal is negotiated. The result is that contract size and expansion happen naturally because multiple stakeholders cannot imagine removing the product, rather than through a prolonged commercial negotiation.

Summary

Kevin's central conviction is that early-stage founders systematically confuse revenue targets with business health, and that chasing ARR before genuine product-market fit is confirmed compounds mistakes faster. PMF is not a soft concept — it has measurable signals (conversion rates, sales cycle speed, price premium willingness, retention) that must be validated before aggressive scaling begins. Revenue targets should be derived from a bottoms-up plan stress-tested against real capacity, not set aspirationally and pursued with hope.

Methodology

Kevin begins by diagnosing whether a founder is chasing revenue before PMF is confirmed, treating this as the primary failure mode at the early stage. He introduces concrete PMF signals founders should track: conversion rate from qualified meeting to close, sales cycle speed, willingness to pay without heavy negotiation, and retention quality. When founders present aggressive targets, he stress-tests them by reverse-engineering the math — required net new and expansion revenue, deal count at a realistic ACV, pipeline needed, and meetings required — to surface whether the plan is grounded or aspirational. For founders who have achieved a sufficient PMF threshold, he pushes hard in the opposite direction: using PMF refinement as a reason not to grow is leaving revenue on the table, and the goal is to pursue both in parallel. He uses reframes like 'the clock starts at PMF,' the 'unbaked' strategic posture for early discovery, and Product-Market Alignment (PMA) as a precursor concept to help founders locate themselves accurately on the maturity curve. In investor contexts, he reframes success metrics toward high conversion rates and POC-to-paid conversion as the most compelling Series A narrative — more durable than raw ARR achieved through shallow wins.

Summary

Kevin's core belief is that founders must personally validate product-market fit and close their first cohort of customers through non-scalable, high-touch means before investing in any sales infrastructure, coaching, or headcount. Premature scaling — whether of tools, processes, sales hires, or coaching engagements — doesn't accelerate growth; it amplifies confusion and sets every subsequent investment up to fail. Going deliberately slow through the validation phase is what makes rapid scaling possible afterward.

Methodology

Kevin applies a strict readiness filter before engaging any founder as a coaching client: if ARR is too low, customer count is insufficient, or ICP is unvalidated, he declines and sends the founder back to do manual, non-scalable customer acquisition first. His prescribed sequence is: (1) founder personally closes deals and does all outreach, (2) founder accumulates 10–30 customers through whatever unscalable means necessary, (3) founder extracts patterns — buying triggers, objections, ICP clarity, value prop — from those closed deals, (4) founder codifies a repeatable playbook, and only then (5) layers on sales hires, coaching, tooling, or automation. He draws hard stage boundaries: each major revenue inflection ($1M, $7M, $50M) requires a clean-slate rebuild of sales infrastructure, not iteration on what came before. Tooling and automation are treated as forms of productive procrastination that delay the direct human contact which generates real learning — his minimum viable stack for early-stage is a simple CRM like Close.com and nothing else. The same sequencing logic applies to CS motions, upsell playbooks, and partner channels: prove it works manually before scaling it.

Summary

Kevin treats fundraising milestones — whether a seed announcement, Series A launch, or Demo Day target — not as isolated finance events but as structured go-to-market opportunities that can accelerate pipeline, validate traction, and create urgency across both investor and customer conversations. He applies the same pipeline discipline to investor processes as to sales processes: running conversations in parallel, creating competitive tension, and timing outreach to maximize leverage. Fundraising context also functions as a reframing tool in his own coaching engagements, making his work feel like a critical path item rather than a discretionary spend.

Methodology

Kevin identifies any upcoming fundraising event — a seed announcement, Series A, or Demo Day — as a trigger for structured outbound and inbound activity, not just a PR moment. For announcements and launches, he recommends a concentrated multi-channel push (owned media, earned press, investor-affiliated content, gifting to top accounts) modeled on high-quality precedents like Amanda Jiao's launch. For founders with inbound investor interest, he coaches them to run all investor conversations in parallel on a shared timeline to create competitive tension and close on their own terms. When a founder needs to hit a revenue milestone before raising, Kevin converts the fundraise target into a concrete, time-bound sales goal — such as 35K MRR by Demo Day — that gives both parties a shared definition of 'ready.' He structures his own advisory engagements to begin delivering immediate, tangible value (e.g., a lead list and sales strategy) so founders have something concrete to show cofounders and early investors before the raise closes. Throughout, he resists letting short-term fundraising pressure translate into unrealistic pipeline commitments, framing outbound — especially enterprise — as a long-term investment even when the client's urgency is high.

Summary

Early-stage startups face a structural trap where enterprise customers demand services delivery, but absorbing that internally destroys focus and doesn't scale. Kevin's view is that this demand should be routed through trusted agency and partner networks rather than hired for internally. Done right, the partner layer becomes a revenue channel and a GTM multiplier, not just an outsourcing workaround.

Methodology

Kevin starts by naming the structural tension explicitly: enterprise buyers want outcomes, not just software, which creates services pressure that a small team cannot absorb without losing product focus. His solution is to identify the delivery demand and immediately ask who in the customer's or founder's existing network can fulfil it — whether that's a customer's preferred agency or a warm referral from the founder's own ecosystem. The goal is to route implementation work through partners who already have domain credibility and client trust, so the startup stays in the software seat. This approach also deepens customer relationships, because the agency becomes an advocate embedded in the customer's workflow. Over time, Kevin frames this not as a workaround but as a deliberate channel strategy: partners who deliver on your platform have strong retention incentives and become a source of new pipeline. The founder's job is to enable and curate this ecosystem, not to compete with it by hiring delivery staff.