Engagement flow

A predictable path from your first email to a findings document your engineers can act on—without handing us production keys or customer data fields.

Hands adjusting probes on an embedded test setup
  1. Intake

    You share MCU family, approximate LOC, toolchain, and deadline via contact. We reply with clarifying questions—usually about which directories matter and whether assembly is in scope.

  2. Scope letter

    We send a written scope: directories included, out-of-scope items (web portals, mobile apps), deliverable format, reviewer names, and calendar hold. You sign NDA and pay deposit to confirm.

  3. Repository access

    Read-only access to a tagged commit or encrypted archive. We do not require VPN into your factory network unless you explicitly arrange it for on-site days.

  4. Review window

    Reviewers work sequentially through drivers, startup, and application layers, logging findings in a shared severity rubric. Mid-window questions go through a single technical contact on your side.

  5. Delivery & readout

    PDF and spreadsheet exports land before the readout call. We walk through severity-1 and disputed items, then destroy working copies unless extended retention is agreed.

  6. Optional follow-up

    After you merge fixes, a shorter pass verifies closures. See rates for follow-up day pricing.

Read the flagship offering