A few weeks ago I finished an online store for a client — a woman-owned self-care brand — and it looked great. Live domain, clean checkout, real product pages, a founder story. Then it sat there. Zero sales. Not because the store was broken, but because I'd made the oldest mistake there is: building the wrong thing first.
The store was ready to sell. The founder wasn't. She was still working on production and didn't feel ready to sell from an online shop yet. I'd built the finish line before the race had started.
The store worked. The timing didn't.
Nothing about the build failed. Everything I could control — pages, payments, shipping, policies — worked exactly as designed. That's what made the lesson sting. A perfect version of the wrong thing is still the wrong thing.
The real constraint was never the website. It was upstream: how much product she could reliably make, and whether she felt ready to put it in front of strangers who'd pay for it. No amount of storefront polish moves either of those.
Why building the wrong thing first is so easy to do
Because the impressive thing and the necessary thing are rarely the same thing.
- The impressive thing is visible — a store, a logo, an app. It feels like progress.
- The necessary thing is often boring — enough inventory, a founder who's ready, one customer who says yes.
- The impressive thing is fun to build. The necessary thing is usually someone else's slow, real-world bottleneck.
So we reach for what we can finish today. I could ship a storefront in a week. I couldn't make her production line faster or make her feel ready. I built what I could build — not what the business needed next.
What should you build first?
Build the thing your customer is actually ready to use — not the thing that looks most finished in a screenshot.
The test I should have run is simple: if this were done today, could the person actually use it? For the store, the honest answer was no. She wasn't ready to fulfill orders or sell from it yet. That single question would have re-ordered everything.
When the answer is no, the real first build is whatever unblocks the yes. Sometimes that's helping the client get production stable. Sometimes it's a single test sale by hand. It's almost never the polished platform.
The fix I'm using now
I now run three checks before I build the visible thing for anyone — a client, or myself.
Ask what they're ready for, not what looks finished
I ask the owner one blunt question: if I hand you this tomorrow, are you ready to use it in front of a real customer? Their answer sets the build order.
Build the smallest thing that proves demand
Before a full store, one product and one buyer. A real yes from a paying customer is worth more than a hundred perfect pages.
Keep the polished build for when it's the bottleneck
The store was good work. It just wasn't the constraint yet. It'll matter — later, when production is steady and she's ready. Good work built too early isn't progress; it's inventory waiting on the real problem.
The honest part: I'm the one who coaches clients on exactly this, and I still did it. Which is why I'm writing it down.
The takeaway: finishing the wrong thing feels like progress and costs like a mistake — before you build what looks done, make sure it's what your customer is actually ready to use.