Finding Clients
Stop Building. Start Talking: The Playbook That Got Me Paying Customers Before the Product Existed
June 17, 2026 · Bradley Jacobs

Here's the dirty secret of building something new in 2026: the building isn't the hard part anymore.
You can spin up a working MVP in an afternoon with Lovable, Base44, or Claude Code. The technical moat that used to separate people with ideas from people who could actually ship has basically evaporated. Which sounds like great news - and it is - until you realize what it exposes. If anyone can build, then building was never the bottleneck. Figuring out what to build, for whom, and whether they'll pay: that's the whole game now.
I want to walk you through the exact process I used to launch a brand-new product about a year ago - the one I run live today. Not a theory from a book: the literal step-by-step that had paying customers on day one, before a single feature was finished. If you're a fractional executive, consultant, or agency owner sitting on an idea you can't stop thinking about, this is the part nobody wants to do - and the part that decides everything.
The Mistake Almost Everyone Makes
You get an idea. You get excited about it. And then you go build it.
You launch, you look around, and you say, "Okay, now I need customers." So you start marketing, talking to people, gathering feedback. The problem is you're getting that feedback after you've poured weeks or months into something. And here's the brutal math: you almost certainly built the wrong thing.
Even if you're solving your own problem - especially then - you're an N of one. One person, one set of frustrations. Your ideal customer is a population, not a mirror. So you build, collect feedback, iterate, iterate again… and you're effectively back at square one, just poorer and more tired. The order of operations is backward, and the order of operations is the whole thing.
Step One: Write Down What You Think Is True
Before you talk to anyone, get your assumptions out of your head and onto a page. Write your hypotheses - what you believe the problem is, and why you believe it's a problem.
Here's mine, in real time. The big-picture problem: B2B founders, agency owners, and fractional consultants struggle to find new clients and fill their pipeline. True - and uselessly broad. So I narrowed. My hypothesis was that these people believe LinkedIn is valuable but have no idea how to leverage it. Then I narrowed again: they don't, because they don't make time for it, don't know what to say, and are terrified of coming across as self-promotional or cringy. The fear of looking cringy means they say nothing, and saying nothing means LinkedIn never works for them.
Notice what happened. One vague problem became a stack of specific, testable claims. That stack is your map. Now you go find out if any of it is real.
Step Two: Talk to Your Customer Before You Build Anything
This is the step everyone skips, because it's genuinely uncomfortable. It's so much easier to sit behind a laptop and build than it is to get a real human on a call and ask what's broken in their world.
Do it anyway. Reach out to people who are actually your ideal customer - not your mom, not your supportive friends, not anyone whose answers will be politely useless. Skewed inputs give you skewed everything. DM people, post that you're having conversations, give something away, whatever it takes to get them talking.
And don't ask "is this a problem?" - people will agree to be nice. Ask open-ended questions. What are you struggling with around this? What have you tried, and how well did it work? How often does it come up? If there were a solution, would you pay - and how much? Then float a direction: what if it looked like this? Tell them flat out: I want your honest answer, you won't hurt my feelings, I am not this product. I talked to 30 people this way, and every conversation either validated or killed one of my hypotheses. That's the point.
Step Three: Build the Smallest Possible Thing - and Charge for It
Once you can see the through-line in their answers, brainstorm the minimum solution to the narrow problem. Then build a no-code or barely-code MVP. Mine was duct-taped together with Notion, Airtable, and Zapier. Today you'd build the same thing in a day with an AI tool.
The cardinal rule: resist scope creep like your life depends on it. No payments system, no notifications, no email sequencing, no login if you can avoid it. Charge through Stripe, send a link, done. Get it live in a single day, because you're almost certainly still wrong and you need to change it instantly.
Then go back to the people you interviewed and make the offer. "I built a solution to the thing we talked about. It's this much. Want in? I'll lock you into beta pricing forever." Of my 30 interviews, six said yes - and they paid over $100 a month for what was, underneath, a Notion-and-Zapier contraption plus a meeting with me every two weeks. Money changes the feedback. People are honest about things they've paid for.
Step Four: Don't Grow Until They'd Be Crushed to Lose It
I put those first customers on a two-week check-in cadence - tight, fast, relentless for the first six weeks. Every session I asked the same things. What do you love? What would you change if you could wave a magic wand? Would you refer this to a friend? And the big one, the Sean Ellis question: how disappointed would you be if I took this away?
That last question is the one that matters most, which is why I saved it for last. The rule of thumb: if 40% of your users say they'd be very disappointed to lose your product, you've found the early shape of product-market fit. Until you hit something like that - until people genuinely love the thing, happily pay, and willingly refer it - you do not grow. No new features, no chasing scale, no pouring fuel on it. Move too early and you'll spend the rest of the company's life pushing a boulder uphill.
That's not a place you want to live. So do the uncomfortable work up front. Talk first. Build last. Let the love come before the growth - because organic, word-of-mouth growth is the most powerful channel there is, and it only shows up when the product is actually worth talking about.
If you're the person waiting for the perfect idea, or quietly building in a corner before you've spoken to a soul, the answer is almost always the same: find your ideal customer, understand their problem in an almost uncomfortably specific way, build the most basic version that solves it, and put it in front of them. The hard part was never the code. It was always the conversation.
Mylance
Your LinkedIn should be working for you, attracting clients, building credibility, and compounding with every post. Mylance makes that happen. See how it works →



