Consultation

Technical advisory

Advisory is a short engagement with a written answer. We read the system, talk to the people who run it, and say what we would do differently.

• A written assessment rather than a slide deck
• The tradeoffs named, including the ones that favour doing nothing
• A recommendation a team can disagree with precisely

Architecture review

A review answers one question, which is whether the system you have will carry what you are planning to build on top of it.

• Service and data boundaries, and where they leak
• Failure modes and what happens when a dependency degrades
• The smallest change that removes the largest risk

Technology strategy

Strategy is the longer view: which platforms to commit to, what to build instead of buy, and how to keep a small team effective as the product grows.

• Build against buy decisions with the running cost stated
• Platform and vendor choices a team can reverse later
• A hiring picture that matches the stack it would leave behind

What the work changes

You end up with a decision you can defend, the reasoning written down, and a smaller piece of work to start with.