Process

From first email
to live in production.

No mystery. No padding. This is exactly how a typical engagement unfolds, week by week.

  1. 01

    First contact

    Day 0

    You send a few sentences about the project. I write back within one business day with either a recommendation or a question. No discovery-call gauntlet.

  2. 02

    Scoping call

    Week 1

    A 45-minute call to understand the real problem, current constraints, and what success looks like. I follow up with a written summary so we agree on what we discussed.

  3. 03

    Proposal & SOW

    Week 1

    Within 3 business days I send a one-page proposal: scope, timeline, milestones, fixed price. No tier ladders, no per-seat upsells.

  4. 04

    Kickoff

    Week 2

    We set up a shared Linear, a Slack channel, and a 30-minute weekly sync. I get access to what I need and start a working repo on day one.

  5. 05

    Build in increments

    Weeks 2–N

    I ship something demoable every week. You see real progress, not status updates. Decisions get written down in the repo, not lost in chat.

  6. 06

    Launch

    Final week

    We cut over with monitoring in place and a rollback plan. I'm on call for the launch window. Nothing ships without an answer to 'how do we undo this'.

  7. 07

    Handoff

    Final week

    You get a runbook, an architecture doc, and a 60-minute walkthrough with your team. The repo is the source of truth — no tribal knowledge.

  8. 08

    Post-launch support

    30 days

    I'm available for fixes, questions, and small tweaks at no extra cost. After that we can switch to a retainer, or you can take it from there.

Ready to start at step one?

Send a first email