Two weeks inside your team produce a technical diagnosis with a fixed shape: prioritized risks, estimated costs, and an action roadmap. You compare options with numbers instead of opinions. No continuing commitment comes attached to the contract.
What happens during the two weeks?
Week 1: map the terrain
System walkthroughs with each tech lead, repository and infrastructure review, analysis of the deployment and incident history, attendance at one sprint ceremony per team. The goal is seeing the system as it runs, outside a sales deck.
Week 2: cross and synthesize
Cross-cutting deep dives cover security posture, data architecture, and the delivery process. Interviews with product and business stakeholders complete the context. The final days go to synthesis, drafting findings.
What does the final report contain?
- Risks ranked by likelihood and impact, with dollar estimates wherever data supports the number.
- A 90-day action sequence separating quick wins from structural work.
- A note on organizational and skills gaps inside the team.
- A stakeholder presentation walking through the priorities in order.
What makes a diagnosis honest?
Three conditions: access to real incident logs instead of a curated tour, freedom to interview anyone, and license to publish uncomfortable findings. A sanitized diagnosis burns the money spent on it. A consultant who softens conclusions to protect a future relationship works against the client.
Which decisions does the report feed?
Four choices appear in almost every project: fund refactoring or plan replacement, fix before scaling the team, concentrate next quarter hiring on the right roles, and judge whether technical risk threatens an upcoming raise or sale. A board question such as "can we close this deal without rebuilding authentication?" fits inside the report. Each finding points at one of these calls.
What happens after delivery?
Three paths follow delivery: implement with your own team, bring the author back for specific workstreams, or retain ongoing advisory. A good report stands on its own without its writer present, and that independence doubles as a vendor selection criterion. It is the standard I apply to my own technical consulting engagements.