One developer. The whole stack. Shipped.

I work on a fixed price per project or on an hourly basis, whichever suits you.

Either way, you get a written scope and a delivery date before anything starts, and nothing lands on an invoice that we haven't agreed first.

It depends on the scope, which is why the delivery date is written down before we start rather than guessed at along the way. A focused build is measured in weeks, not quarters.

If something is going to slip, you hear it in that week's update while there's still time to react, not on the day it was due.

A working product deployed on your own infrastructure, with domain, DNS, and SSL configured. Plus the full source code in your repository, handover notes explaining how it fits together, and two weeks of support after launch.

You do, all of it. Everything is built in your repository and deployed to your accounts, so you're never renting your own product back from me.

If you want to bring the work in house or hand it to another developer later, you can, and the handover notes are written so that's a straightforward day rather than a forensic exercise.

Yes, that's a good part of the work I do. I start by auditing what already exists and telling you honestly what's worth keeping, what needs reworking, and what it costs to get to finished.

Sometimes the honest answer is that rebuilding is cheaper than repairing. If that's the case, I'll say so and show you why.

I shift my hours to overlap with yours, and I work with clients across every time zone already.

Beyond calls, you get a live staging link from week one and a written update every week, so progress is something you can check rather than something you have to ask about. Messages get a reply within one working day.

That's normal, and it's what the first conversation is for. Bring the problem you're trying to solve and we'll work out what actually needs building, what can wait for version two, and what you can skip entirely.

You'll get a written scope out of it either way, so even if we don't work together you leave with a clearer plan than you came in with.

Usually React or Next.js and TypeScript on the front end, Node or NestJS with Postgres behind it, and Docker, AWS, or Cloudflare for deployment and infrastructure.

The stack gets picked to fit the project rather than my preferences. I lean towards well established, slightly boring choices, because those are the ones any developer can pick up after me.