---

name: founder-led-sales description: "Coach the user through actually selling: finding the champion and the buyer, running the first sales conversations, demoing their use case, handling "let me think about it," and closing the first paying customers yourself. Use when developers love it but nobody pays, you've never sold anything and freeze on the conversation, or deals keep stalling on "we'll think about it.""

Founder-led sales (close your first customers yourself)

Nobody can sell it before you can. The first ten deals are not a hire, they are how you learn what you are actually selling and to whom. Do them yourself, badly at first, until the motion repeats.

Use this when: developers love it and live in the free tier but nobody pays, you have never sold anything and freeze on the actual conversation, every deal dies on "let me think about it," or you are tempted to hire a salesperson to do the part you have not figured out yet.

The core idea

market-to-devs-sell-to-buyers told you who to sell to (the dev adopts, the boss pays). pricing set the number. This is the part nobody warns technical founders about: actually doing it. And it is not slimy. Selling a dev tool well is discovery plus helping a champion get budget. You are not convincing anyone of anything false, you are finding the people who already have the pain and making it easy for them to say yes.

One rule under all of it: do this yourself until it repeats. You cannot outsource a motion you have not cracked. Founders who hire a rep at deal one hire someone to fail at a job that does not exist yet.

Every real deal has four things

If any one is missing, it is not a deal, it is a conversation. Your job is to find out which is missing.

• A champion. Someone who uses it, loves it, and will fight for it inside their company. Usually the developer who adopted you.
• A buyer. Someone with budget. Often not the champion.
• A pain with a cost. Not "this is nice." A problem costing them money, time, or risk right now.
• A trigger. A reason to act now, not next quarter. An incident, an audit, a deadline, a scaling wall.

The motion

1. Start with who is already engaged. Do not cold-blast strangers. Your first customers are hiding in your own usage data: the team with three seats on the free tier, the person who filed four issues, the account that hit a limit. They have already shown you the pain.

2. Reach out like a founder, not a sequence. One short, human message to a real person about a specific thing you noticed. If it could have gone to a thousand people, do not send it.

3. The first call is discovery, not a pitch. Talk 30 percent, listen 70. Learn: what are they using it for, what did they do before, what is the pain costing them, who else feels it, who owns the budget. Founders pitch too early and too much. The person asking the best questions controls the conversation.

4. Demo their use case, not your feature list. Show the product doing their job with their kind of data, and get them to the win (see time-to-first-value). A feature tour is not a demo. "Here is your exact problem, solved" is.

5. Frame value for the buyer, not the dev. The developer feels the hours saved (Chronos). The buyer approves budget for the outcome: a release cycle back, an incident avoided, a compliance box checked, a competitor not winning (Kairos). Translate the dev's love into a business result the boss can defend.

6. Arm the champion to sell internally. You are rarely in the room when the yes happens. Give your champion the one-paragraph business case, the number, and the answer to "why now," so they can walk it to their boss. This is the middle-out motion: an excited dev plus a buyer who sees the ROI.

7. Always leave with a specific next step and a date. This is how you kill the stall before it starts.

"Let me think about it" is not an objection

It is a missing next step, or a concern you did not surface. Do not accept it and leave. Ask, gently: "Totally fair. What would you need to be sure of to move forward?" Then you learn the real blocker (budget, a stakeholder, a missing feature, timing) and can actually address it. A vague yes-later is a no you have not diagnosed.

Thresholds worth knowing

• Do it yourself through roughly your first 10 to 20 paying customers, or until you can write down what works and repeat it. Only then does hiring make sense.
• Multithread. A deal with only the champion is fragile. If you have not spoken to the person with budget, you do not have a deal, you have a fan.
• No next step, no deal. Never end a sales conversation without a specific action and a date.
• Do not discount out of fear. Price pushback is a conversation about value, not a reason to cave (see pricing).
• Talk less. If you are talking more than the customer in discovery, you are pitching, not selling.

Mistakes that look reasonable

• Hiring a salesperson too early. You cannot delegate a motion you have not figured out. The first deals teach you what you are selling.
• Pitching instead of asking. Founders lead with the product. The best sellers lead with questions and let the customer talk themselves into it.
• Selling to the champion and stopping there. They love it and cannot sign. You have to reach the buyer.
• Feature-touring the demo. Showing everything shows nothing. Show their problem solved.
• Treating "think about it" as a yes. It is an undiagnosed no. Surface the real blocker before you leave.
• Confusing usage with revenue. Ten thousand free users and zero conversations with a buyer is not traction, it is a popular free tier.
• Apologizing for charging. If it delivers value, the price is fair. A founder who flinches on price trains the buyer to flinch back.

Your next 30 minutes

• Open your usage data. List the 5 most engaged accounts (most seats, most usage, most issues filed). Those are your first sales calls.
• For your best one, fill in the four: champion, buyer, pain-with-a-cost, trigger. Note which is missing.
• Write one short, human outreach message to that champion about a specific thing you noticed. No template.
• Draft five discovery questions you will ask before you show anything.
• Decide the one business outcome the buyer would pay for, and say it in a single sentence.

---

Built from real dev-tool GTM experience, with frameworks from Adam Frankl (The Developer-Facing Startup) and Jakub Czakon (markepear.dev). If deals keep stalling and you want someone in your corner on the actual calls, reach out to me on LinkedIn.