Services
Three ways to work together
Most engagements start with a diagnostic audit, then convert into development work once we both know what needs doing. A retainer keeps the relationship going between larger pieces of work. Every tier is scoped and priced per engagement — the shapes are below; the numbers come out of a conversation about your specifics.
Audit / assessment
A fixed-scope diagnostic engagement. I go deep on your codebase and its build and test setup, then hand back a written report: what the real problems are, and a roadmap of what to do about them, in priority order.
This is the on-ramp. It stands on its own as dedicated expert work, and when it makes sense it becomes the plan for a development engagement — you see how I work before committing to anything larger.
Development
A milestone-based development contract, typically running three to six months. Each milestone has acceptance criteria agreed up front — for example, refactoring a specific module and landing a test suite around it — so progress is measured by what actually ships, not by hours logged.
This is where the verification loop gets installed directly in your own codebase, not demonstrated on training code.
Retainer / advisory
A monthly advisory retainer — roughly ten hours a month of ongoing access. Design reviews, second opinions on architectural calls, help when your team hits something outside its usual ground.
It suits teams who have delivery under control and want a steady line to someone who has seen the failure modes before, without standing up a full engagement each time.
Not sure which fits?
If you can describe the problem but not the shape of the fix, start with the audit — that's exactly what it's for. If you already know what needs building, say so and we can scope a development engagement directly. Either way, the first step is the same: tell me what you're dealing with.