Hire me
Available for the work below.
Availability
Lead time: 2 weeks
How I work
-
Agree what done looks like
One call and a written scope. If neither of us can describe the finished thing in a paragraph, it is too early to start — and that paragraph is what we measure against at the end.
-
Ship something every week
A branch you can pull and an environment you can click, weekly. Redirecting in week two costs an afternoon; redirecting in week ten costs the project.
-
Hand it over properly
Production deploy, a runbook that covers the boring failures, and a recorded walkthrough of the codebase. The test is whether your next developer needs me.
-
Then thirty days of fixes
What happens after go-live, in writing, below — not a conversation we have once something breaks.
After-launch support
Included in every project, not sold back to you afterwards.
- Thirty days of fixes
- Anything broken within thirty days of launch is fixed at no charge, with no argument about whether it was in scope.
- A runbook, not a README
- Architecture notes, environment setup, and the three things most likely to page somebody at 2am.
- A recorded walkthrough
- A screen-recorded tour of the codebase on request. Cheaper than an onboarding call six months later.
- A retainer, if you want one
- Feature work, performance, keeping dependencies current. Monthly or a block of hours — no minimum term.
Tell me what you're building.
A paragraph is enough to start. I reply within 1–2 business days, and I'll say so plainly if it isn't a fit.