Ready to build your own Founder-Led Growth engine? Book a Strategy Call
Frontlines.io | Where B2B Founders Talk GTM.
Strategic Communications Advisory For Visionary Founders
Kevin's pattern across multiple mergers: employees wake up to a call announcing new ownership, new rules, no input. "They didn't ask for this. Right. They did not have the opportunity to vet this opportunity with other opportunities. They didn't get the chance to go and talk about this with their spouse." The mistake: assuming alignment. The fix: immediate heart-to-heart conversations about fit with the new direction, accepting that not everyone will be aligned, and building your bench before announcing. If you don't account for departures, "your first call it three to six months turn out to be less than productive because everybody's trying to figure out the new way of the new organization. And all of a sudden now your head counts down by 25%."
Kevin's team "sliced and diced the data multiple times" to define their new ICP across the merged entity. They discovered certain medical specialties had worse churn profiles and consumed disproportionate onboarding and CS resources despite being technically serviceable. The decision: create a three-tier system where tier 3 (no-fit) segments were completely off-limits to reps. "You're already skeptical about this merger and what it means to them and you're telling them, hey, by the way, we're cutting down some of your addressable market." Result: better performing cohorts and elimination of early churn that triggers commission clawbacks. The lesson: your pre-merger ICPs are irrelevant—the combined entity serves different customers with different economics.
The founder's CTO connection or CEO relationship isn't a sales process. Kevin asks: "How did you find this client?" When the answer involves personal introductions from previous roles, that's not scalable. His filter: "Can this process, do you have a sales process in place that will work without you being involved in it?" Before adding headcount, validate that deals close through repeatable motions, not founder proximity. Kevin saw this across five acquisitions in a PE rollup—founders believing they had ICP clarity when their best clients came through unrepeatable advantages.
Across the PE rollup Kevin worked with, he consistently found misclassified revenue: "This revenue isn't exactly reoccurring, this is not subscription revenue. It really should be, you know, put back into more one time revenue." SaaS revenue multiples significantly outpace service revenue multiples in acquisitions. Founders optimizing for growth often blur these lines, labeling professional services or one-time implementations as recurring. By the time acquirers audit, the damage to enterprise value is done. Get rigorous about revenue classification early—what counts as true SaaS matters more than top-line growth when exit conversations begin.
Kevin watched founders bring in Oracle and Salesforce reps who "have never had to get scrappy for their deals." Large company reps follow established processes with brand recognition doing heavy lifting. Startups require different DNA: "You are wearing all the hats, right? You're not just CRO, you're running sales enablement, you're running some content marketing. You are the one that is going to have to build out collaterals and proposals." His hiring filter: urgency, commitment, and intelligence. Urgency specifically: "The reps that will go out and try it, they don't wait around...The reps that are consistently the top performers are the reps that will come back and follow up with you in about two hours and say, hey, went out, tried that. This work, did it. This didn't work." Urgency isn't trainable—you either see it in the first week or you don't.
Most revenue leaders experience one merger in their career. Kevin Keller has navigated five as CRO. In a recent episode of The Sales Front Lines, Kevin shared the specific frameworks that survive post-merger chaos—and the expensive assumptions that consistently break within ninety days.
Kevin’s pattern holds across every transaction: leadership announces the merger, and 25% of headcount walks within six months. The pipeline built by those reps? Gone. The deals they were working? Reassigned to teams already skeptical about the merger.
“They didn’t ask for this,” Kevin explains. “At the end of the day, they did not have the opportunity to vet this opportunity with other opportunities. They didn’t get the chance to go and talk about this with their spouse. They got woke up, got on a call and were told, hey, this is a new company and there’s some new rules and here you go.”
Most leadership teams present the strategic vision, host an all-hands, answer questions, then return to integration planning. Three months later, they’re scrambling to backfill positions while pipeline conversion craters because nobody accounted for natural attrition from organizational disruption.
Kevin inverts this. Before the announcement, he builds the bench—identifying potential hires, warming relationships, understanding market compensation. Immediately after announcement, he conducts individual conversations with every rep and manager. The goal isn’t retention theater. It’s identifying misalignment before it manifests as quiet quitting or surprise departures during your most critical quarter.
“Not everybody is going to be aligned and really a fit with the new direction of the organization. And that’s okay. You just have to account for that. You better make sure that you’ve got a really good bench and ready to bring people in. So you don’t have your first call it three to six months turn out to be less than productive because everybody’s trying to figure out the new way of the new organization. And all of a sudden now your head counts down by 25% because you weren’t expecting some departures.”
When Yapi merged with DoctorLogic, Kevin’s first major decision made him “public enemy number one” with sales: he eliminated both companies’ existing ICPs completely.
The strategic thesis was sound. Yapi owned patient engagement—appointment booking, communication workflows, post-visit follow-up. DoctorLogic controlled patient acquisition—SEO, local search, getting practices discovered. Separately, each competed in markets where every competitor offered similar feature sets. Combined, they owned something nobody else did: the complete patient journey from discovery through retention.
But the merged ICP wasn’t the union of both customer bases. Kevin’s team analyzed their combined book of business, segmenting by specialty, practice size, patient volume, tech stack, and geographic market. They tracked which segments had strongest retention, fastest time-to-value, highest expansion rates, and lowest support burden.
The data contradicted both companies’ assumptions about their best customers. Certain medical specialties both companies had successfully sold showed significantly worse churn and consumed disproportionate CS resources. “We saw very clearly that there were some medical specialties that yeah, absolutely, we could serve and we could bring our product to. But there were quite a few out there that, you know, they had a worse churn profile. They took up a lot of time from our onboarding and CS team once they got into it.”
Kevin implemented a three-tier framework: Tier 1 (direct fit ICP—actively pursue), Tier 2 (indirect fit—pursue only when they come inbound or under specific conditions), and Tier 3 (no-fit—do not sell regardless of deal size or circumstances).
Then he told sales they couldn’t pursue Tier 3 segments. Period.
“You talk about being public enemy number one. You have some reps coming into the newly found merged organization and you’re telling them straight away, hey, you know, they’re already skeptical about this merger and what it means to them and you’re telling them, hey, by the way, we’re cutting down some of your addressable market because there are some clients I don’t want you to go after.”
The results validated the framework. “Cohorts that we have signed under these Tier 1 and Tier 2 fit ICPs have proven to have better outcomes for them and for the reps as well, because they don’t have to be nearly as concerned about any early churn or anything that’s going to negatively impact them, like clawback of commissions.”
The clawback point matters. Reps optimizing for quarterly quota will close any deal that counts toward their number. When those deals churn in month three or four, commission clawbacks hit during reps’ best-performing quarters. The three-tier system aligned rep incentives with customer success by preventing deals that would trigger clawbacks.
Before Yapi, Kevin worked across founder-led companies in various stages of sales maturity. He consistently observed the same fatal pattern: founders believing they’d validated repeatable sales motions based on successful early customers.
Kevin’s diagnostic cuts through this immediately: “How did you find this client?”
The answer reveals everything. “Well, I found it because I had this introduction for I used to work with the CTO over there or the CEO over there. So they decided to try us out.”
This isn’t product-market fit. It’s founder social capital masquerading as sales process. Kevin saw this across multiple companies in a PE rollup—five founder-led businesses that had all misdiagnosed their go-to-market readiness. Their best customers came through unrepeatable advantages: previous employer relationships, Stanford roommates, YC batchmates, advisory board connections.
His framework for founders: “Can this process, do you have a sales process in place that will work without you being involved in it?”
If outbound sequences, demo frameworks, and objection handling only work when the founder’s on the call, you don’t have a sales process. You have founder-led sales theater. Hiring a VP of Sales to “scale what’s working” will fail because nothing’s actually working without founder proximity.
Kevin’s advice: validate the motion works with a founding AE before scaling headcount. Document what that AE does to close deals without founder involvement. Only then can you confidently hire reps two through ten.
Kevin found identical revenue classification mistakes across the PE rollup he joined. “Defining what truly is interesting to potential acquiring companies. Meaning what is SaaS revenue and what is truly service revenue. And SaaS revenue is a lot more interesting as they are starting to think of exits.”
The mistake follows a predictable pattern. Professional services get bundled into software contracts. One-time implementations become “onboarding fees” tracked with monthly recurring revenue. Quarterly business reviews delivered by CSMs get packaged as “strategic services” within the subscription.
This isn’t intentional misrepresentation. It’s growth-stage companies optimizing dashboards for board meetings, using generous interpretations of what counts as “recurring.”
Acquirers don’t share this generosity. “As I was getting into some of these businesses I was seeing that yeah, this revenue isn’t exactly reoccurring, this is not subscription revenue. It really should be, you know, put back into more one time revenue.”
The valuation impact is structural. True SaaS revenue—software subscriptions that renew automatically with minimal human intervention—trades at significantly higher multiples than services revenue. When due diligence reveals that 30% of “SaaS revenue” is actually professional services, the enterprise value calculation reprices instantly.
Kevin’s recommendation: implement rigorous revenue classification three years before any exit conversations. Build financial reporting that clearly separates software subscriptions, professional services, and one-time fees. Short-term vanity metrics matter less than long-term valuation integrity.
Kevin’s hiring framework prioritizes three traits: urgency, commitment, and intelligence. But only urgency is truly non-negotiable. “The number one trait, it’s in their DNA. I think people either have it or don’t is urgency.”
His diagnostic is elegantly simple. During team meetings or enablement sessions, he shares tactics working in other markets: “Here’s an idea that somebody tried, and maybe it’s from an office, you know, or California office, go try it. See if you have the same success.”
Average performers wait. They want to see results from others first. They’ll test it eventually—next week, when pipeline slows, when they have bandwidth.
Top performers return within two hours. “The reps that are consistently the top performers are the reps that will come back and follow up with you in about two hours and say, hey, went out, tried that. This work, did it. This didn’t work. Hey, have we thought about trying this?”
This pattern has held constant across Kevin’s 25 years leading sales organizations. Urgency isn’t a skill you develop—it’s behavioral DNA that manifests immediately and consistently. You observe it in week one or it doesn’t exist.
This explains why Kevin avoids hiring enterprise reps from Oracle, Salesforce, or similar companies for startup roles. “Although a rep might have been really good at following some of these large organizations processes. At the end of the day, a lot of them have never had to get scrappy for their deals.”
Enterprise sales reps operate within established infrastructure. Marketing generates qualified pipeline. Brand recognition opens doors. Legal provides contract templates. Sales engineering handles technical validation. Success follows process execution.
Startup revenue leaders build that infrastructure while selling. “You are wearing all the hats, right? You’re not just CRO, you’re running sales enablement, you’re running some content marketing. You are the one that is going to have to build out collaterals and proposals and everything else.”
Reps who’ve never built collateral, designed outreach sequences, or closed deals without brand recognition can’t suddenly develop scrappiness when resources disappear. The impressive resume becomes a liability when speed and resourcefulness matter more than process adherence.
Kevin’s filter for evaluating AI sales tools reveals his mental model: “What are we trying to solve, right? And what are we trying to get answers to and what are the metrics we’re going to use to determine if this is a success or not.”
His priority hasn’t changed despite the AI hype cycle: “The number one thing as I look at any tool is what can drive and help me achieve my goals of pipeline.”
The reasoning is structural, not tactical: “A good strong pipeline cures all ills, meaning that if you have a strong pipeline, it cures top of the funnel issues. If you have a strong pipeline, it cures middle of the funnel issues. If you have a strong pipeline, it can cure and mask bottom of the funnel issues.”
For Yapi competing in saturated healthcare technology markets, sustainable pipeline came from positioning rather than outbound optimization. Patient engagement platforms and patient acquisition platforms both competed in crowded markets where feature differentiation was marginal at best. Combined, they owned something structurally different: the complete patient journey from discovery through long-term retention.
“Very saturated markets that they were competing in. Very tough to differentiate yourself from a product standpoint. But when you look at that entire patient journey that these two organizations coming together could bring to the market, there wasn’t really anybody else that at the time was doing this.”
The insight extends beyond healthcare. In mature B2B markets where product parity becomes inevitable, strategic combination often creates more defensible positioning than incremental feature development. Pipeline follows differentiation—and differentiation increasingly comes from solving broader workflows than competitors address.
Kevin’s five transactions taught him post-merger success isn’t about synergy presentations or integration timelines. It’s about planning for 25% attrition before announcement, rebuilding ICP from combined cohort data, classifying revenue for acquirer scrutiny, hiring for demonstrated urgency, and creating positioning that actually differentiates. The frameworks aren’t complex—they’re just consistently ignored until someone’s navigated enough integrations to recognize which variables actually predict outcomes.