Founder Involvement in Onboarding Locks Customers In
- Cormac Repman
- 4 days ago
- 3 min read
I realized something uncomfortable during a customer discovery call last month: when a buyer insists on working exclusively with you during onboarding, they're not asking for a favor. They're building a lock-in mechanism you didn't know you were creating.
Here's what happened. A prospect was evaluating our SDR outsourcing service and wanted to negotiate down from our standard $500-per-meeting rate. His internal SDR had been expensive, and he was comparing us against hiring overseas contractors. During our conversation, he made a specific request: he wanted me, the founder, as the sole point of contact for the first 60 to 90 days. No handoff to a contractor. No delegation. Just me, building the process, absorbing the nuances of his business, and creating detailed SOPs so nothing got lost.
His reasoning was practical. He'd been burned by contractor turnover before. Knowledge walked out the door when people did. He'd seen it happen multiple times. By insisting I be the point of contact, he thought he was de-risking the engagement for himself.
What he actually did was create a relationship that couldn't be transferred.
This is the insight: founder involvement during onboarding doesn't just build trust. It creates operational friction that becomes a hidden switching cost for the customer. If he switches vendors later, he doesn't just lose the service. He loses the person who understands his business deeply, who built his playbook from scratch, who knows every edge case in his sales process. Starting over with a new vendor means retraining, rebuilding SOPs, and losing all that accumulated context.
I caught myself about to say yes to exactly this dynamic.
The problem is it's genuinely hard to refuse. A customer asking you to be their primary contact feels like a vote of confidence. It feels like he trusts you. And at a discounted rate, it feels like you're earning his business. But what you're actually doing is taking on a role that scales poorly and creates a business model where the company becomes dependent on your personal involvement.
From his perspective, this is brilliant negotiating. He gets a discount on price while securing you as an unreplaced resource for the critical ramp-up phase. His switching cost just went from low (he can replace a vendor) to high (he'd have to rebuild his entire process with someone new). He's paying less and getting more leverage.
From my perspective, I need to think clearly about what I'm actually offering. The value of the service should be in the process, the methodology, the results. Not in my personal relationship to his business. If the service only works because I'm the one doing it, then I don't have a scalable business. I have a consulting engagement that looks like a SaaS product.
The thing that made me recognize this was the timeline pressure he mentioned. He needed to make a hiring decision within 30 to 90 days. That deadline matters because it's how long he needs me embedded before the relationship becomes transferable. After 90 days, if he's locked in, I could theoretically step back. But until then, he owns me.
Here's what I learned: when a customer insists on founder involvement as a condition of engagement, especially during the critical ramp phase, ask yourself what problem they're actually solving. Usually it's not about you. It's about their fear that the service could be replaced with something generic. They're buying confidence in continuity by making continuity dependent on you.
The smarter move is to build systems that don't require that dependency. Document everything. Create repeatable onboarding. Build SOPs so good that a colleague could hand off the relationship and the customer would barely notice. Then, if a customer still insists on working with you, you've earned the right to charge for that privilege.
Founder involvement should be a premium feature, not the foundation of the product.
Comments