Founder-led sales

Applies when developers love your tool and live in the free tier but nobody pays, you have never sold and freeze on the actual conversation, or every deal dies on "let me think about it." Produces a first-deal motion you run yourself, from finding the champion to closing the buyer.

Do the first deals yourself

Nobody can sell it before you can. Your first ten to twenty deals are not a hire, they are how you learn what you are actually selling and to whom. You cannot outsource a motion you have not cracked; a founder who hires a rep at deal one hires someone to fail at a job that does not exist yet. And it is not slimy: selling a developer tool well is discovery plus helping a champion get budget. You find the people who already have the pain and make it easy for them to say yes.

Every real deal has four things

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

• Champion — uses it, loves it, and will fight for it inside their company. Usually the developer who adopted you.
• Buyer — has budget. Often not the champion.
• Pain with a cost — a problem costing money, time, or risk now, not "this is nice."
• Trigger — a reason to act now: an incident, an audit, a deadline, a scaling wall.

The motion

1. Start with who is already engaged. Your first customers hide in your usage: the team with three seats on the free tier, the person who filed four issues, the account that hit a limit. They have shown you the pain. Do not cold-blast strangers.
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 thirty percent, listen seventy. Learn what they use it for, what they did before, what the pain costs, who else feels it, who owns the budget. 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. "Here is your exact problem, solved" beats a feature tour.
5. Frame value for the buyer. The developer feels the hours saved; the buyer approves budget for the outcome — a release cycle back, an incident avoided, a compliance box checked. 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. Hand them the one-paragraph business case, the number, and the answer to "why now," so they can carry it to their boss.
7. Always leave with a specific next step and a date. This kills the stall before it starts.

"Let me think about it"

Not an objection, a missing next step or an unsurfaced concern. 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 address it. A vague yes-later is a no you have not diagnosed.

What good looks like

• You started from your most engaged accounts, not a cold list.
• In discovery, the customer talked more than you did.
• You can name all four (champion, buyer, pain-with-a-cost, trigger) for the deal, and you have spoken to the person with budget, not just the fan.
• The demo showed their problem solved, not a tour of features.
• Every conversation ended with a specific next step and a date.

Rules

• MUST run your first ten to twenty deals yourself before hiring a rep.
• MUST reach the buyer, not only the champion; a deal with only the champion is a fan, not a deal.
• NEVER end a sales conversation without a specific next step and a date.
• NEVER treat "let me think about it" as a yes, or discount out of fear at the first price pushback.