I Do

I take on a small number of engagements — projects where the scope is clear and the fit is right. If that sounds like yours, get in touch.

Product Development

Fixed-scope full-stack builds — web apps, booking platforms, dashboards, internal tools.

  • A working product, not just a prototype — deployed, not just demoed locally
  • Direct access to the person writing the code, not a project manager relaying messages
  • A stack chosen for what the product needs, not defaulted to whatever's trendy

Cloud & Kubernetes Infrastructure

AWS architecture, Terraform/IaC, migrations, self-hosting setups, cost optimization.

  • Infrastructure defined as code, not clicked together in a console no one can reproduce
  • A migration plan with rollback points, not a one-way door
  • Cost and complexity sized to what the project actually needs

Advisory

A focused session on one problem: an architecture review, a stuck migration, a planning decision. Scoped and scheduled case by case.

  • A focused session on one problem — an architecture review, a stuck migration, a planning session
  • Notes and next steps in writing afterward, not just a call that evaporates
  • No lock-in

How engagement works

Same process for every engagement — let's discuss scope before committing to anything.

  1. 01

    Discovery

    A short call or written brief to scope the problem and constraints.

  2. 02

    Proposal

    A written scope, timeline, and approach — no surprises once work starts.

  3. 03

    Milestones

    Work ships in demoable phases, not one long build-and-reveal cycle.