Web products built to be run, not just shipped.
You have a product idea or a prototype that has outgrown itself. I build the real version, with accounts and payments, and I already run two products of my own.
What a product build includes
- Architecture and data modelThe decisions that are expensive to change later, made deliberately.
- Authentication and tenancyAccounts, roles and data separation between customers.
- Billing and paymentsSubscriptions and payments through Stripe, with the failure cases handled.
- Deployment and monitoringA repeatable release process and enough visibility to run the product.
- TestingAutomated tests and browser tests on the paths that matter.
How I choose a stack
I do not sell a framework. TypeScript across the app where it makes sense, Next.js and Node for the application, Cloudflare Workers, D1, KV, R2 and Queues for edge work, and a SQL database for the data. When a different tool is a better fit, I use that.
AI handles syntax and API detail across all of it. I make the architecture and security decisions, and I read the code.
How design and build work for a product
The same gates apply. You see three visual directions, choose one and refine it before building. Then the product is built in working increments you can see on staging, with your approval at the points that matter.
References
I build and run my own products, ZoneSteward and CookieSteward, on the same approach. They are the clearest evidence of how I work.
Related
Can you work with an existing codebase?
Yes. I start by reading it and writing up what I find, then decide with you whether to extend, refactor or replace parts.
Which stack will you pick?
The one that fits the product and your team. I am comfortable across several, and I will explain the choice in plain terms.
Do you build MVPs?
Yes. A good MVP is a deliberately small product on a foundation that will not need rewriting when it works.