Technical advisory
A decision is due — rebuild or extend, one platform or two, hire or outsource — and the people closest to it disagree. You need an independent read that survives contact with your board.
What we deliver
- Read the code, the infrastructure and the ticket history before forming a view
- Interview the engineers who maintain the system and the people who use it
- Set out the realistic options, including the option of changing nothing
- Cost each option over three years, separating build cost from the cost of running it
- Name the risks that would change the recommendation, and what would confirm each one
- Record the strongest argument against our own recommendation, so the board sees both sides
- Deliver a document your engineers can challenge on the evidence
- Stop there when stopping is the right answer, rather than converting the review into a project
Engagement
Access and scoping
The question to be answered, written in one sentence and agreed in writing
3 days
Evidence gathering
Code and infrastructure review, interviews, cost data, and incident history
1 to 2 weeks
Options and costing
Options with three-year costs, risks, and what would change the answer
1 week
Review and challenge
A working session with your engineers, then the final document with their objections included
3 days
What we need from you
- Read access to the repositories, the infrastructure and the ticket history
- Ninety minutes each with the engineers who maintain the system
- The commercial constraint we are working inside, even approximately
- Permission to write down a recommendation you may not like
After delivery
- The document is yours to circulate, with no watermark and no follow-on engagement attached
- We will present the findings to your board or your investors if that helps
- If you implement it with someone else, we will answer their questions for thirty days
- If the recommendation turns out wrong within a year, we will say so in writing