Loading
I take an unclear problem, work out what should actually get built, and then build the whole of it. Interface, API, database, deployment, and the alert that wakes me when it breaks. That last part is the one most people leave out, and it is the part that decides whether the thing survives contact with real users.
The work I am useful for is the work where the boundary between frontend, backend and infrastructure is the problem. A slow page is rarely a frontend bug. It is usually a query shape, a cache that was never invalidated, or a request doing at deploy time what it should have done at build time. Someone who only owns one of those three ends up filing a ticket against the other two.
So I take the whole path: what gets built, how the data is modelled, what runs where, and what happens when a piece of it fails at three in the morning.
It starts with a conversation about the problem, not the stack. Often the useful outcome of that conversation is that the thing you asked for is not the thing you need, and it is cheaper to find that out in an hour than in a quarter.
After that: a scope we both agree is honest, then the build, in pieces you can see running rather than a single reveal at the end. You get the repository and the deployment. Nothing is held hostage.
Work where nobody can say what success looks like. Rescues of a codebase whose owner wants it defended rather than fixed. Anything sold on a deadline that was set before the scope was. And projects where I would be the only engineer and the only person who understands the system, with no plan for what happens when I am not there.
Saying so up front costs me some enquiries. It costs less than taking one of them.
There is no rate card here, because the number depends on scope, on how much of the thinking is already done, and on whether the work is a fixed piece or an ongoing one. A published figure would be wrong for most of the people reading it in one direction or the other.
Describe the problem and I will tell you what it would take, or that I am not the right person for it. Reduced and pro bono terms exist for non-profits, educational institutions and early-stage teams.
Use the Upwork and say what you are trying to build and what is currently in the way. The more specific the second half, the more useful my reply.
There is no email address and no contact form on this site. Client work runs through Upwork, whose terms restrict exchanging direct contact details off the platform, so the Upwork profile is the way in. The contract and the payment live there too.