May 12, 2026
# Five Calls Before You Write a Line of Code
You know that itch to start coding? The one where you've got the perfect idea, you can see the architecture, maybe you've even sketched out the database schema on a napkin. Stop. Put the laptop down. Pick up the phone instead.
I've shipped products nobody wanted. Built features that solved problems nobody had. Spent months perfecting code that should have been killed in a week. The fix is stupidly simple: talk to five actual customers before you write a single line.
## The Trap Everyone Falls Into
Research feels like customer discovery. It's not. You read blog posts, analyze competitors, maybe run a survey. You convince yourself that "people would pay $50/month for this." But that's a hypothesis dressed up as fact.
Five customers saying "yes, I'd pay that" on a recorded call? That's validation.
The difference matters because one costs you a Google search and the other requires you to put your ego on the line. Most founders pick the Google search. Then they wonder why their product doesn't sell.
## The Four Questions That Actually Matter
You're not having a conversation. You're running an interrogation disguised as coffee chat. These four questions get you everything:
**"How often do you do X?"** Not "do you ever..." or "would you consider..." but how often RIGHT NOW. Daily? Weekly? Once a quarter? Never is a valid answer.
**"How long does it take you?"** Time is money, but most people can't convert between them. Get the time first. If it takes them 2 hours a week, you've got something to work with.
**"What's the most painful part?"** Shut up after you ask this one. Count to ten in your head if you have to. The good stuff comes after the awkward pause when they realize you're actually listening.
**"Would you pay $50/month or $200/month?"** Anchor with real numbers. Both options should feel slightly uncomfortable to say out loud. You want them to push back. Their pushback tells you the real price.
## The Mechanics Nobody Talks About
Send a $50 Amazon gift card after each call. Not before—you want honest feedback, not purchased agreement. Record every call (with permission). Calendar the one-hour follow-up while you're still on the call.
And here's the ratio that matters: Listen 80% of the time. Talk 20%. If you're explaining your vision or defending your idea, you're doing it wrong.
I set up a Calendly link specifically for these calls. Subject line: "Quick question about [their specific problem]—$50 for 30 minutes of your time." Busy people respond to specificity and compensation.
## When They Say No (And Why That's Gold)
"I'd never pay for that."
Your instinct is to argue. To explain why they're wrong. To show them the mockup that would surely change their mind. Don't.
Instead: "That's really helpful—can you tell me why?"
The why is everything. Maybe the price is wrong. Maybe you're solving the wrong layer of the problem. Maybe they've got a hacky workaround that's good enough. You can't fix what you don't understand.
Three calls in, someone told me they'd never pay for my brilliant automation tool because "Excel works fine." Turns out they meant they had an intern manually copying data between spreadsheets for 10 hours a week. Excel wasn't working fine. But I only learned that by shutting up and asking why.
## Reading the Signals
If all five people say no pain, no payment? You just saved three months of your life. Kill the idea. This is the best possible outcome.
But usually the signals are mixed:
**Price Pivot**: "I'd pay $20, not $200." You've got a business model problem, not a product problem.
**Product Pivot**: "Actually, the real pain is Y, not X." Capture everything about Y. That's your new product.
**Timing Pivot**: "Ask me again next quarter when we have budget." They're being polite. It's a no.
The hardest signal to read? Enthusiastic agreement with no specifics. "This sounds amazing! I'd definitely use this!" means nothing without a credit card number.
## Why This Is So Hard to Actually Do
You're scared they'll hate it. You're scared they'll steal it. You're scared you'll sound stupid.
Good. You should be scared. Because if you're not scared, you're not being honest about what you're building and why.
I pitched a monitoring tool to a CTO who laughed at me. Not polite chuckle—actual laughter. "You think I'm going to pay for another dashboard to ignore?"
That stung. It also saved me six months of building the wrong thing. Turns out what he wanted wasn't monitoring—it was automated response to the alerts. Completely different product.
## Start This Week
You don't need a deck. You don't need a prototype. You don't need anything except:
1. A spreadsheet with 20 potential customer names 2. A way to record calls (I use Zoom) 3. $250 in Amazon gift cards 4. The four questions written on a Post-it note
Find those 20 names from your LinkedIn connections, relevant Slack communities, or Twitter. Don't overthink it. The first five who say yes to a call are your validation cohort.
Send this email by Friday:
"Hey [Name], I noticed you work in [specific role] at [company]. I'm researching how people handle [specific problem] and would love 30 minutes of your time to understand your current process. I'll send a $50 Amazon card as a thank you. Are you free next Tuesday or Wednesday?"
That's it. No company name, no product pitch, no vision statement. Just curious research and fair compensation for their time.
By next Friday, you'll know if your idea is worth building. Or you'll have a much better idea to build instead.
Either way, you'll be ahead of every founder who's currently debugging code for a product nobody wants.