Service 01
Freelance web development,
schema to production.
I build full-stack web products on my own — the database, the API, the interface, the deploy pipeline. No handoffs between three contractors, no "that's a backend problem." One person who carries the thing from first schema to the deploy that puts it in front of users.
Start a project ↗What I build
- SaaS platforms
- Multi-tenant apps with auth, teams, billing and role-based access. The unglamorous plumbing that every product needs and nobody wants to scope.
- E-commerce
- Storefronts and checkout flows with Stripe, inventory, and the SSR work that makes product pages actually rank.
- Internal tools & dashboards
- Admin panels, ops dashboards and approval flows — custom, or in Retool where speed matters more than bespoke UI. I spent two years building Retool apps for client after client and will tell you honestly which one your case wants.
- Real-time features
- Live updates, collaborative editing, notifications — WebSockets and server-sent events, done so they survive reconnects.
- Rescue work
- Inheriting a codebase someone else left. Auditing it, stabilising it, then moving it forward without a rewrite you can't afford.
Stack
- Frontend
- Next.js · React · TypeScript · Tailwind
- Backend
- Node · Go · Python · REST / GraphQL / WebSockets
- Data
- Postgres · MongoDB · Prisma · Redis
- Internal tools
- Retool · admin panels · ops dashboards
- Infra
- Vercel · AWS · Docker · CI/CD
Whether this is a fit
A good fit if
- You need one person accountable for the whole build, not a team to manage
- The product is real and needs to ship, not a prototype to demo
- You want SEO and performance handled during the build, not bolted on after
Probably not if
- You need a team of five starting Monday — I take a few projects at a time
- You are choosing purely on lowest bid rather than on the work
- The scope is genuinely undefined and nobody wants to define it
Questions I get asked
How do you charge?
Three ways, whichever suits the project: an hourly rate, a monthly contract for ongoing work, or milestone-based payments tied to agreed deliverables. We settle which one on the scoping call, before any work starts.
How long does it take?
A focused MVP is usually 4–8 weeks. A larger platform runs 2–4 months. I give a real estimate after a scoping call, not before.
Do you work with existing codebases?
Yes, and often. I'll audit it first and tell you honestly whether it's worth building on or whether you're better off rewriting a piece of it.
What timezone do you work in?
I'm a digital nomad, usually somewhere in Southeast Asia. I keep overlap hours with US and European clients and have done so for years — it's a solved problem, not a risk.
Do you build in Retool?
Yes. I built Retool apps for a stream of different clients over about two years — ops dashboards, admin panels, approval flows. It's the right call for internal tools with a countable number of users, and the wrong call once customers touch it. I'll tell you which one you have before you commit.
Who owns the code?
You do, completely, on final payment. Everything lives in your repository from day one.
Related writing
- Retool for Internal Tools — What Building for a Dozen Clients Taught MeTwo years of shipping Retool apps for client after client — where it genuinely beats writing a custom app, where it quietly falls apart, and how to decide before you commit.
- Next.js vs React for Startups — Which Should You Actually Start With?A no-hype breakdown of Next.js vs plain React for early-stage startups — SEO, speed to market, hiring, and cost — with a clear default and the cases where it flips.
- Postgres vs MongoDB — Which Should Your SaaS Actually Use?A practical comparison of Postgres and MongoDB for SaaS products — schema, queries, scaling, and cost — with a clear default and the specific cases where the default flips.