Engagement model

Advisory work only helps if both sides know what happens each week. This page describes the model we use for firmware delivery advisory and related consultations.

1. Briefing call

   Thirty to forty-five minutes. You share the product class, board generation, firmware team size, and the nearest immovable date. We say plainly whether our advisory fits or whether you need implementation staffing instead.

2. Scoped proposal

   A short written proposal: objectives, session plan, exclusions, fee, and deposit terms. No multi-hundred-page SOW unless your legal team requires it.

3. Access & prep

   NDA as needed, calendars locked, pre-reads exchanged (backlog export, hardware milestones, known risks). We arrive with a draft critical-path sketch, not a blank whiteboard.

4. Working block

   Interviews, joint scheduling sessions, and decision logs. Lab time when boards and fixtures matter. Sponsors join for checkpoint reviews, not every working hour.

5. Closing brief

   Owners, milestones, release criteria, and residual risks in a document your team can maintain. Optional retainer if you want continued office hours.

What we need from you

A sponsor who can assign owners, access to the people who actually flash boards, and honesty about political constraints (sales promises, factory penalties, missing headcount). Without those, an advisory becomes theater.

Natural next actions

Browse consultations or request a briefing with your hard date in the first sentence of the message.