How I work, in seven steps
- Published
- Reading time
- 1 min read
The process I use for client work and my own products: problem first, a live link early, and shipping before it feels finished.
I build client work the way I ship my own products: small, fast and in the open. It starts with one clear problem and the people who have it, and you get a live link early. Here are the seven steps.
1. Problem first
Before any code, I pin down the problem, who has it and what a win looks like. Every decision after that stays tied to the goal we set on day one.
2. Sketch the flow
I map the key screens and how you move between them. Moving a box on a sketch is much cheaper than rewriting a page.
3. Build the core
Next.js and TypeScript, with auth, database, payments and AI wired end to end. The usual pieces are Clerk, Prisma or Convex, Stripe, and OpenAI or Anthropic. They change when the project needs it. SketchMason runs on Convex and bills through Polar.
4. Live from day one
Every push deploys to Vercel, so you click through real progress instead of looking at screenshots.
5. Phone and polish
I check every screen on a phone, then tighten speed and edge cases.
6. Ship early
I launch lean, with a waitlist or a first version in front of real users. For Quickly I shipped the waitlist site first to see if people wanted it. Then I watch how people use it and add only what matters. Shipping early also means being honest about what isn't done. ChronoSeek's playground says plainly that it's a simulation.
7. Keep building
Never give up. The next version is always better.

