Engagement process from signed scope to handed-off report
This is the default calendar for a flagship architecture review. Roadmaps and dependency audits compress or skip stages as noted in your statement of work.
-
Week 0 — Scope & access
You name repos, environments (read-only), and interviewees. We send an NDA if needed, confirm out-of-scope systems, and schedule kickoff on site or video.
-
Week 1 — Context & interviews
Structured sessions with tech leads, on-call veterans, and one product stakeholder. We collect incident timelines, deployment frequency, and the decisions you already regret.
-
Week 2 — Deep read
Static analysis, dependency graphs, tracing sample flows in code. We validate assumptions from interviews against what the repository actually does.
-
Week 3 — Synthesis & draft
Internal review at Vector Orbit, then a draft findings list to your lead engineer for factual corrections only—not scope renegotiation.
-
Week 3–4 — Readout & delivery
90-minute readout with Q&A, PDF report, optional engineer annex with diagrams. Four hours of office hours within 30 days for clarifying implementation order.
Your preparation checklist
- Architecture sketches or ADRs, even if outdated
- Last three significant incidents or postmortems
- List of “we will fix someday” tickets your team already agrees on
- Named owner who can grant repo access within 48 hours