08
Web Development
Not a brochure site — an application. Accounts, data, permissions, payments, and the unglamorous machinery that decides whether it still works with a thousand users on it.
When this is the right fit
- You need software people log into, not pages they read.
- A no-code tool got you started and you’ve hit its ceiling.
- You need something built well enough to show a technical investor.
- Your current site can’t do the one thing the business now depends on.
- You want the frontend, backend and database to be one coherent system.
How I build it
- 01
Start with the data
Most web apps that become painful to change got their data model wrong early. I work that out first — what the things are and how they relate — because it’s the decision everything else inherits.
- 02
Boring, fast choices
React and Next.js, Postgres, a deployment you can reason about. I pick technology you could hand to another developer, not whatever is interesting this quarter.
- 03
Auth and permissions done properly
Not just login — who is allowed to see and change which record. This is the thing most rushed builds get wrong, and it’s the one that turns into an incident rather than a bug.
- 04
Shipped, monitored, handed over
Deployed on infrastructure you own, with error tracking and backups configured, and documentation that means the next developer isn’t starting from nothing.
How long it takes
A first usable version is typically three to six weeks. The honest variable is requirements — integrations with other people’s systems, and anything touching money, take longer than they look. I’d rather give you a real number after a short scoping conversation than an optimistic one now.
Questions about this
Can you build something from scratch?
Yes — mobile, web and AI-powered products. It's a different engagement from a rescue: we start with what the thing actually needs to do, and I'll usually push to get a small version in front of real users before building the rest. If your idea is better served by something simpler than what you're picturing, I'll say so.
Can you work with Node.js?
Yes. Node is one of my primary backend stacks, including APIs, background jobs, integrations and the deployment around them.
Can you help with deployment?
Yes, and it’s one of the most common reasons people get in touch. "It works locally" is almost always an environment, configuration or build problem rather than a code problem, and those are findable.
Your AI-built app doesn’t need another prompt.
Sometimes it needs an engineer.
Send the messy version. That’s usually the useful version.