I lost a $12,000 project because I wouldn’t shut up.
Forty-five minutes on a discovery call. I spent 40 of them talking about what I could build, the tools I’d use, the plugins I’d chosen, the timeline I’d mapped out. The prospect said “we’ll think about it” and never replied again. I sent two follow-up emails. Nothing.
The next month, I tried something different. I asked five questions. I listened for 30 minutes. Then I recorded a 10-minute Loom video walking through a custom proposal instead of sending a PDF. That deal closed at $15,000. Same skills. Completely different approach.
The thing nobody tells developers is that the problem isn’t your ability to sell. It’s that you’re selling the wrong way.
Why Developers Struggle at Sales (and Why That’s Actually Fine)
Developers think selling means persuading. It doesn’t. It means qualifying.
Your job isn’t to convince anyone. It’s to find the people who already need what you build and show them you understand their problem better than they do. That’s a diagnostic skill, not a charisma skill. Most developers are actually good at it once they stop trying to pitch.
The $12K deal I lost? I was pitching. I was listing features and capabilities because I was nervous, and nervous developers talk about their work. The prospect wasn’t looking for a list of features. They were trying to figure out if I understood their specific problem. I was so busy talking about solutions that I never properly heard the problem.
The $15K deal I won? I asked what a successful website would mean for their business in six months. I asked what they’d tried before and why it hadn’t worked. I asked who would be using the site and what action they needed visitors to take. By the end of the call, the prospect felt understood. And when you feel understood, you trust the person who understands you.
Selling for developers isn’t about being charming. It’s about being a good diagnostician.
The Lead Qualification System That Saves You Hours
Before any call happens, you need to know who’s worth talking to.
I use a simple intake form that every prospect fills out before I schedule a discovery call. Seven questions. Takes them about five minutes. Saves me hours.
The questions I ask:
- What type of project are you looking to get done?
- What’s your estimated budget range for this project? (I give ranges: under $1K, $1K-$3K, $3K-$7K, $7K-$15K, $15K+)
- What’s your target completion date?
- Are you the primary decision-maker for this project?
- Have you worked with a developer on this before? What happened?
- How did you hear about us?
- Is there anything specific I should know before our call?
The budget question filters about 70% of tire-kickers automatically. Someone who selects “under $1K” isn’t going to suddenly find $5K because I gave a great pitch. They just can’t afford it yet. That’s fine. Refer them somewhere appropriate and move on.
Decision-maker authority matters more than most developers realize. If the person on the call has to “check with their boss” on everything, your close rate drops dramatically. Not because you’re doing anything wrong, but because you’re selling to someone who can’t say yes.
The “what happened before” question is gold. A prospect who’s fired two previous developers is either the problem or inheriting bad work from the previous developers. Either way, I need to know before I quote.
Honestly, this form alone cut my time on non-converting calls by about half. And the quality of conversations went up at the same time.
The Discovery Call Script for Non-Salespeople
I don’t follow a rigid script, but I follow a consistent sequence. The sequence matters because it controls how information flows.
First five minutes: Confirm what I already know from the intake form. “I see you’re looking for a WooCommerce build with about 500 products and a custom checkout flow. Is that still the right framing?” This tells the prospect I did my homework and saves us from restating basics.
Next fifteen minutes: Let them talk. These are the questions I ask, roughly in this order:
- “What does success look like six months after launch?”
- “What’s the business cost of the current situation?” (If their site isn’t converting, what’s a lost visitor worth?)
- “What have you tried before, and what didn’t work about it?”
- “Who else is involved in making this decision?”
- “Walk me through your timeline. Is there a hard deadline or is this flexible?”
- “What’s your budget range?” (I ask this again, directly, even if they filled it in the form. People’s real number sometimes differs from the form.)
I let them answer fully. I resist the urge to jump in with solutions. When they’re done answering, I summarize what I heard: “So what I’m hearing is you have X situation, and the cost of not solving it is Y, and you need it done by Z. Is that right?”
Nine times out of ten, they say yes, plus they add one more thing they forgot to mention. That extra thing is often the most important detail.
Last ten minutes: I don’t quote on the call. I say “Based on what you’ve told me, I have a clear picture of the scope. I’m going to put together a proposal that I’ll send you by [specific date], and I’ll walk you through it on a short follow-up call.”
Never end with “I’ll send you a quote.” End with a specific next step and a specific date.
The Loom Proposal Method
This is the single biggest change I made to my sales process, and it’s the one that surprised me most.
PDF proposals close at roughly 20-30% for me. Video proposals close at 60-70%. Same information. Completely different medium.
Here’s why video works better: it builds trust in a way that a document can’t. When a prospect watches a 10-minute Loom of me walking through their custom proposal, pointing at their specific requirements, explaining my thinking, they see that I built this for them. A PDF looks the same whether you spent two hours on it or copied it from a template (because you did copy it from a template).
My Loom proposal structure:
Minute 1: Reference the discovery call specifically. “In our call, you mentioned that your current site isn’t capturing leads from mobile users, and that’s costing you roughly $3K a month in missed inquiries. That’s what I built this proposal around.”
Minutes 2-4: Walk through the three options I’m presenting. Don’t read the PDF. Explain the thinking behind each option. Why the starter option exists. Why the professional option is probably the right fit. What the enterprise option includes and when it’s worth it.
Minutes 5-8: Focus on the middle option in detail. Show examples of similar work. Explain the technology choices and why they fit this specific situation.
Minutes 9-10: Clear next steps. “If this looks right, here’s the link to sign the agreement and pay the deposit. If you have questions, here’s my calendar link to schedule a 15-minute call.”
The Loom is hard to forward to a cheaper competitor. A PDF is not. When a prospect has watched you explain your thinking for ten minutes, they’re less likely to take that to someone else and say “build me this for half the price.”
Pricing the Deal: Anchoring, Tiers, and the No-Brainer Package
I always present three options. Always.
The premium option exists to anchor. When someone sees a $15,000 option, $7,000 stops feeling expensive. It’s basic psychology, and it works whether or not you think it should.
The middle option is where you want most clients to land. Price it at the intersection of what delivers real value to them and what makes the work worthwhile for you.
The starter option gives clients a way to say yes to something if the middle tier is genuinely out of reach. Some of my best long-term client relationships started with starter tier projects that eventually grew into $20K+ relationships over two or three years.
A real three-tier WooCommerce proposal I used last year:
Starter ($3,500): 50-product WooCommerce setup, standard checkout, Stripe payment integration, mobile responsive, basic analytics.
Professional ($6,500): 500-product WooCommerce setup, custom checkout flow, Stripe + PayPal, filtered product search, performance optimization targeting sub-2-second load time, 60-day support.
Enterprise ($12,000): Everything in Professional, plus custom wholesale pricing rules, integration with their existing ERP system, staff training sessions, 90-day support, first maintenance quarter included.
The prospect chose Professional. The anchoring of Enterprise made the $6,500 feel like a smart, reasonable choice rather than a significant investment.
For managing your proposal pipeline and client relationships, Close CRM is what I use for tracking where each deal is in the process. Simple, built for small teams, doesn’t have the bloat of enterprise CRM tools. And Google Workspace handles proposals, contracts, and the professional email presence that tells prospects they’re dealing with an established operation.
The Follow-Up Sequence That Doesn’t Feel Desperate
80% of deals close after follow-up. Not after the pitch.
Most developers send one follow-up email and give up. They don’t want to seem pushy. So they lose deals to competitors who were persistent enough to follow up three times.
A three-touch follow-up sequence over two weeks:
Day 3 after sending the proposal: “Just checking in to see if you had a chance to review the proposal. Happy to jump on a 15-minute call if you have questions about the scope or the options.”
Day 8: Send something new. An article you wrote that’s relevant to their project. A case study from a similar client. A technical insight from your current work. The key is adding value, not just restating “have you made a decision yet.” This one is the hardest to write, but it’s also the most effective.
Day 14: The honest close. “I have two project slots opening up at the end of next month and I’m finalizing my schedule. Let me know if you’d like to move forward or if the timing isn’t right. Either way, I appreciate the conversation.” This message gives them a reason to respond even if the answer is no.
Most prospects who go quiet aren’t avoiding you. They got busy. A thoughtful follow-up at the right time pulls them back. I’ve closed deals on the day 14 message that I’d written off.
Building a Referral Engine That Replaces Cold Outreach
The best source of $5K+ leads isn’t cold email. It’s clients who already know what you’re worth.
I ask for referrals at project completion, not before. Before the project is done, you haven’t delivered yet. The client doesn’t know enough to recommend you with confidence. After a successful launch, they’re at peak satisfaction and they have something specific to say about your work.
My referral ask is simple: “I’m glad the launch went well. If you know any other business owners who are struggling with [their specific situation], I’d love an introduction. I have capacity for one new project next month.”
The specificity matters. “Know anyone who might need a website” gets a shrug. “Know any other SaaS founders who need a custom onboarding flow built” triggers actual names.
One client in the legal tech space generated four referrals within six months of project completion. Total value: $22,000. And none of those referrals negotiated on price, because they’d been told by someone they trusted exactly what to expect.
I don’t offer referral fees to clients. I’ve tried it. It doesn’t work the way you’d expect. Clients don’t refer for money. They refer because you made them look good, and because they want to help someone they like. Referral fees make it transactional, and transactional referrals get you price-shoppers, not ideal clients.
For the cold email outreach side of lead generation, there are good tools, but referrals should always come first. And for the full picture of running a professional freelance operation, must-have tools for freelancers covers the business infrastructure that makes all of this possible.
You don’t need to overhaul your entire sales process this week. Pick one thing from this article and try it in your next deal cycle. Maybe it’s the intake form that filters before the call. Maybe it’s recording a Loom instead of sending a PDF. One change, tested honestly, over two or three proposal cycles. I went from closing 1 in 10 prospects to closing 3 in 5 by changing these things one at a time over six months. Not a system overhaul. Just sequential improvements.
Frequently Asked Questions
How long should a discovery call last for a $5K+ project?
45-60 minutes. Less than 30 and you haven’t understood the problem. More than 75 and you’re going in circles or the prospect is using your time as free consulting. Schedule 60-minute slots and aim to end at 45. Ending early signals efficiency.
Should I charge for initial consultations or audits?
For generic consultations, no. For specific technical audits that produce a deliverable, yes. Charge $300-$500 for a site audit. About 60% of paid audit clients convert to project clients. The ones who don’t still paid for your time.
What’s the best way to handle prospects who want to think about it?
Ask directly: “Is there anything in the proposal that’s unclear, or are you comparing a few options?” The answer tells you what to do next. “Think about it” usually means they’re comparing competitors, need internal buy-in, or aren’t sold on the value. A direct question beats silence and a follow-up email.
How do I compete against agencies with dedicated sales reps?
You have an advantage agencies don’t: you. When clients buy from a solo developer, they know exactly who they’re getting. Make that explicit: “You’ll work with me directly, not a project manager who passes requests to a junior developer.” For clients who value direct communication, that’s more attractive than an agency pitch.
When should I walk away from a deal?
When the budget is genuinely below your floor and scope-cutting won’t fix it. When they’ve fired multiple developers for unclear reasons. When they want to own all code but won’t pay for documentation. Or when you don’t like the project. A bad-fit client costs more than its revenue in energy and work quality.
Do Loom video proposals really convert better than PDFs?
Dramatically. PDF proposals close at roughly 20-30%. Video proposals close at 60-70%. Same information, completely different medium. Video builds trust because the prospect sees you built the proposal specifically for them. And a Loom is hard to forward to a cheaper competitor.
