A second opinion before the expensive decision
Architecture, stack and build-versus-buy advice from a team that will still be here when it ships.
What you get
- Architecture review and options
- Stack and vendor assessment
- Build-versus-buy analysis
- Delivery estimate and risk register
- Written recommendation
What changes
- A decision made with the trade-offs written down
- The reasoning survives the person who made it leaving
- Buying something is a real option, not a lost sale to us
When teams call us
- A large build about to be committed on a hunch
- Two internal camps disagreeing on the stack
- An investor or board asking for technical due diligence
Process
How the work runs
The same four phases whichever engagement model you pick, each ending in something you can read.
Brief
What decision you are trying to make, and what would change your mind. An audit without a decision behind it is a document nobody reads.
- Decision stated
- Constraints named
- Access arranged
Review
Code, architecture, infrastructure and process, weighted toward the parts that cost money when they fail.
- Code read
- Architecture mapped
- Team interviews
Findings
Written up and prioritised by impact against effort, with the reasoning included so you can disagree with it.
- Prioritised list
- Effort estimates
- Reasoning shown
Handover
A working session with your team. The output is theirs to act on, with or without us.
- Walkthrough
- Q&A
- No lock-in
Technology Consulting, specifically
The questions that come up on this work in particular.
Still have a question? Talk to the team
Not sure which service your project needs?
Most useful projects cross two or three of them. Describe the outcome and we will map it.