What I will not build

If the work has no owner or measurable bar, I cannot write a scope you can approve.

  • Crypto, gambling or adult content
  • A scope nobody on your side can approve
  • An internal system with no written requirements
  • A model trained from scratch
  • A rewrite with no measured problem to fix
  • A project judged only on revenue or rankings

From scope to handoff

  1. Define the scope

    I write the flows, exclusions and acceptance criteria before code.

  2. Approve the bar

    You approve the scope and the method used to check it in writing.

  3. Build in your repo

    I build in your repository against the approved scope.

  4. Check against the bar

    I run the agreed checks and save the results. A miss blocks acceptance.

  5. Hand over the work

    Your team gets the code, setup guide, results and a walkthrough.

What you own

At handover, the code is yours to the last line, with a clean handoff.

Planted faults caught by code tests

Tests they replaced5 of 17
Tests written by my method16 of 17

Code-test benchmark, 2026-10-10

Before you send it

How is the scope agreed?

I review the repository and the problem, then write the flows, exclusions, acceptance bar and handoff. You approve the scope before code.

Can you work in our existing codebase?

Yes. I inspect the repository before scoping. The audit measures your running feature; the sprint builds into your existing stack.

What if the scope changes?

New work gets a written scope change. You approve the revised work and acceptance bar before I build it.

Can my engineers take over?

Yes. I document setup, deploy and operation, then walk your team through it. The checks, results and guides go with the code.

The case studies behind these numbers

Tell me what has to work

Send the demo or describe the product. I write the scope, the acceptance checks and the handoff plan for you to approve before code.

Get your written scope

Also open to a full-time remote role.