Let’s talk about the problem

The work I do best starts as a complaint, not a ticket — the last-mile task that never gets budget yet quietly costs your team hours every week. Tell me what that is where you work. If I can help, I’ll tell you how I’d approach it. If I can’t, I’ll tell you that too, and point you somewhere better.

This is usually a good fit when

  • There is an internal tool or manual hand-off that people have quietly built a workaround for.
  • The work is real but small enough to finish — weeks, not an open-ended engagement.
  • You want the reasoning and the specs handed over, not just a repository you cannot change.

Reach me

I read everything and reply within two business days.

What happens next

  1. A short call

    Thirty minutes on the problem itself — what it costs, who it touches, and what a fix would have to do to count.

  2. A written spec, before any code

    Requirements, design and a task list you approve. Nothing gets built from a conversation neither of us can go back and read.

  3. Shipped, and verified on staging

    Implementation against that task list, proven on a preview environment, and released deliberately — never by accident.

If you would rather see the whole loop before you write, walk through how I ship software.