Engineers planning work together

Engagement path

What happens from your first email to a delivered review—and optional refactoring follow-through.

  1. Inquiry and fit call (30 minutes)

    You describe repository size, stack, timeline, and whether you need a full review or architecture session. We confirm conflict of interest and NDA needs.

  2. Scope letter and deposit

    Written boundary: packages included, LOC estimate, deliverables, and calendar dates. Forty percent deposit secures the review window.

  3. Access and kickoff interview

    Read-only Git, CI history, and a 60-minute call with your lead engineer covering incidents, deployments, and known debt.

  4. Deep read (two weeks)

    Principals read code, run tests locally, and trace critical paths. Clarification questions go to a single client contact to limit disruption.

  5. Draft findings checkpoint

    Optional mid-point call if we uncover a critical production risk; otherwise you hear from us at draft delivery.

  6. Report, recording, and backlog

    Final PDF, walkthrough recording, and ranked backlog. Balance invoice issued.

  7. Optional refactoring sprint

    If you book pairing, we align on three modules and daily stand-ups with your squad for ten days.

Typical elapsed time for the review path alone: four weeks. Rush slots occasionally available at a quoted premium.

Start at step one Flagship review scope