Shipping fast as a solo builder

Speed is a feature

As a solo builder, speed is your only structural advantage. You can't outspend, out-market, or out-hire anyone. But you can out-ship them. The faster you get something in front of real users, the faster you learn what matters.

My stack for speed

Next.js + Vercel

Zero config deployment. Push to main, it's live in 90 seconds. I don't think about servers, Docker, or CI/CD pipelines. The time savings compound over weeks.

Tailwind CSS

I'm not a designer. Tailwind lets me build interfaces that look professional without agonizing over spacing values. The constraint-based system means I make fewer decisions and move faster.

Claude for scaffolding

I use Claude to generate boilerplate, draft copy, and think through edge cases. It doesn't replace thinking, but it eliminates the blank page problem. Most sessions start with "Here's what I'm building, help me think through the data model."

The workflow

Monday: Validate the idea

Talk to 3-5 potential users. Not surveys — actual conversations. "Would you use this?" is useless. "Show me how you handle this today" is gold.

Tuesday-Thursday: Build the MVP

Core feature only. No auth, no settings page, no dark mode. If the core interaction doesn't work, nothing else matters.

Friday: Ship and share

Deploy it. Post it. Send it to the people I talked to on Monday. Their reactions tell me whether to keep going or move on.

What I've learned

The biggest enemy of shipping is not technical complexity — it's scope creep disguised as "doing it properly." Every feature you add before launch is a bet that you know what users want. You don't. Ship, learn, iterate.