May 31, 2026 · 4 min read · Indie Hacking, Side Projects

Sell First, Build Later

Every failed side project has the same origin story: someone built something nobody wanted to pay for. Here's the counter-intuitive fix — find the money before you write a line of code.

The Feature Factory Trap (Weekend Edition)

You get an idea on Friday night. By Saturday morning you've spun up a repo, chosen a stack, and started building. By Sunday you have a login page, a dashboard, and a feature list that would take a team of four a quarter to ship. Monday rolls around and you're burned out on a project that has zero users. Sound familiar?

That's the weekend edition of the feature factory trap — and it's the #1 reason side projects die before they ever see a customer.

The One-Inbox Test

I know a guy who built a SaaS for dental practices. Before writing a single line of code, he found 12 dental offices on Google Maps, called them, and asked one question: "If I built a tool that automatically sends no-show follow-ups via text, would you pay $47/month for it?"

Three said yes on the spot. One asked to beta test. Two said it depended on the integration. He had six warm leads with zero product. He built the MVP in a weekend. First paying customer within two weeks. That product is now doing $4k/mo MRR.

The lesson isn't about dental. It's about sequence. He sold first, built second. Most people do the opposite.

The Weekend Validation Framework

If you have a side project idea right now, here's how to spend your next 48 hours:

Friday Night (2 hours): The Hunt

Find 20 potential customers. LinkedIn, industry directories, Google Maps, wherever your target audience hangs out. Don't build anything yet. Just make a list of 20 real people or businesses who have the problem you want to solve.

Saturday Morning (3 hours): The Outreach

Reach out to those 20 people. Not with a pitch. With a question. "Hey, I'm exploring a tool that does X. Does that pain point resonate with you?" Two outcomes to measure: (1) How many reply, (2) How many say "where do I sign up?" If fewer than 5 reply, your messaging needs work. If zero say they'd pay, your idea needs work.

Sunday (6 hours max): The Build

Now you build. But build the minimum — the ugliest thing that still delivers the core value. One feature. One workflow. One happy path. If your product requires a login page, onboarding flow, and settings panel before it does anything useful, you've already built too much.

Why This Works

The emotional math is simple. If you build for a weekend and nobody cares, you feel like a failure. If you talk to 20 people and 3 say they'd pay, you have rocket fuel for the next two weeks of building. The difference is knowing someone is waiting on the other side.

I've seen this play out dozens of times across the indie hacker community. The projects that ship are rarely the most technically impressive. They're the ones that started with a conversation instead of a commit.

The Tools That Make This Easy

You don't need a full dev setup. For a weekend MVP, use anything that gets you to "works" fastest:

• Bubble / Softr — Drag-and-drop web apps. Genuinely capable for MVPs.
• Lovable / Bolt / v0 — AI code generators that skip the boilerplate.
• Stripe Checkout — The fastest way to get paid. A payment link is a product.
• Typeform + Zapier — A form connected to a spreadsheet is a product for certain use cases.
• WordPress + WooCommerce — Underrated for digital products. Ship in an afternoon.

The tool doesn't matter. The sale does. Find someone who'll pay. Build for them. Everything else is optimization.