Founder-Led Sales: Build a Process Before You Hire

A founder can have a full calendar and still have no idea how to make the next sale happen.

You get introductions. People like the demo. A few buy. Then you hire someone to repeat what you did, and discover how much of the process lived in your head.

Founder-led sales should leave you with something another person can use: a clear buyer, a way to diagnose their problem, a path to a buying decision, and a record of what worked. Revenue matters, but reaching $1M ARR doesn’t automatically make that process transferable.

This guide is for B2B founders building that process. You can use it while learning who will buy and while preparing to hire. Discovery and selling inform each other; you don’t need a perfect customer profile before you speak to a potential customer.

Start with a buyer you can recognize

“Mid-market companies” tells you very little about who needs you today.

Write down the person’s role, the situation they’re in, the problem they’re trying to solve, and what they’ve already tried. Then name three real people who fit. Three is a useful exercise, not a validation threshold.

For example, imagine you’re selling onboarding software:

Heads of customer success at B2B software companies who are adding implementation staff because new customers keep getting stuck between signing and going live, and who already tried managing the handoff in spreadsheets.

That’s a hypothetical buyer, not evidence that this market wants your product. It gives you something to investigate. Is hiring really happening? Where do customers get stuck? Do spreadsheets cause the problem, or does nobody own the handoff?

If you can’t find people who fit, revise the hypothesis. If you find them but the problem isn’t important to them, revise it again. The startup validation framework can help you structure that work.

Earn a small yes before asking for a meeting

Your first message should make it easy for the person to decide whether the problem is relevant.

Use a reason you can actually support. Don’t imply you know their internal problems because you found a job opening.

A hypothetical message:

Hi Sam. I saw you’re hiring implementation managers. I’m building a tool for customer-success teams dealing with handoffs between signed contracts and customer launches. Is that a problem your team is working on?

This is an opening question. If they say yes, ask how they’re handling it and whether a conversation would be useful. If they say no, you’ve learned something without asking them to sit through a pitch.

Keep outreach relevant, identify yourself honestly, and respect a request to stop. More follow-up doesn’t repair a poor fit. If replies are the problem, use the cold-email diagnostic before adding more volume.

Diagnose before you demo

On the call, find out what is happening before showing what you built.

Ask about a recent example:

• When did this last happen?
• How did your team handle it?
• What did it cost in time, money, or missed work?
• What have you already tried?
• Who would need to agree to a change?
• Is there a reason to fix it now?

“What are you paying for this right now?” is a useful question once you understand the situation. The answer may include software, contractors, or staff time. Existing spending gives you evidence that the problem matters; its absence means you need to investigate willingness to change more carefully.

Don’t turn the questions into an interrogation. Follow the answer. If the buyer describes a problem you can’t solve, say so.

When a demonstration would help, show the part that addresses what you just heard. You can do that on the first call if it’s useful and the buyer wants it. A scheduled demo isn’t a reason to ignore the conversation.

Larger deals also require understanding the people involved. In Enterprise Sales for Hackers, founder Ryan Junee explains why champions, budget holders, and other stakeholders have different concerns. His discussion focuses on complex enterprise deals near or after product-market fit. Use that stakeholder lens when your deal requires it.

Agree on the next action while you’re together

“Great demo, send something over” leaves a lot unresolved.

Ask what the buyer needs to decide, who needs to participate, and what happens next. If they want to evaluate the product, agree on the scope, success criteria, responsibilities, timing, and commercial terms before the work starts.

A next step might sound like this:

You said the handoff is where launches get delayed. Would it help to bring your implementation lead into a call to walk through one recent launch? I can send an outline today. Who should be there, and when would that be useful?

Record what both sides agreed to do and when. If the buyer isn’t ready, find out what’s missing. If there’s no priority or fit, close the loop rather than keeping the deal alive in your imagination.

Follow-up should refer to that conversation: the question you promised to answer, the person who needed to join, or the decision they were considering. A CRM can remind you; it can’t create a reason for the buyer to care.

Build the handoff as you sell

Keep a short working playbook:

• Buyer and trigger: who buys, what changed, and who isn’t a fit.
• Call guide: questions that reveal the problem and examples that explain your solution.
• Decision process: stakeholders, evaluation steps, pricing, and recurring objections.
• Deal record: source, stage, next action, outcome, and reason for a loss or delay.
• Customer handoff: what you promised, who owns delivery, and how the customer reaches their first useful result.

Define stages by something the buyer has done. “Proposal sent” records your activity. “Buyer reviewed the proposal and identified the remaining approval” tells you more about the decision.

Review similar opportunities together. Record counts alongside conversion rates, and separate warm introductions from prospects reached through a channel a new hire can use. A handful of deals can suggest a pattern; it can’t establish a dependable benchmark.

Founding Sales, by founder Pete Kazanjy, describes the transition from selling yourself to packaging that ability and teaching it to others. It also warns about both premature hiring and waiting too long to scale a working process.

Before hiring, ask: Can I explain why these customers bought? Can someone else find similar prospects? Do customers get the value we sold? Can we afford the hire, support their learning, and give them enough opportunities?

A first rep still needs coaching. An experienced seller can help you learn, but make that part of the role explicit. Don’t hire someone to execute a proven playbook when the actual job is discovering one.

What to do this week

Pick one stalled opportunity. Write down the buyer’s problem, current workaround, people involved, and agreed next action. Mark anything you don’t know.

Use the next conversation to fill the most important gap. Then add what you learned to the playbook. That’s how selling becomes a process you can eventually hand over.

If you’re still deciding how to reach potential customers, get the First 1,000 Customers playbook. Use it alongside this guide to choose how you’ll start those conversations.