The problem
You have a technical decision to make that will outlive several team members, and nobody to test it against. Choosing a stack, evaluating a proposal that landed on your desk, understanding why your team has slowed down, or knowing whether what you are being quoted makes any sense.
Who it is for
Founders about to invest in software who want an independent opinion, and technical teams who need to test a decision against someone with nothing to sell in that decision.
What it is not
Not an audit to assign blame, nor a generic best-practices report. It is judgment applied to your case, with recommendations you can act on the following week.
How we work
Framing
What decision has to be made, which constraints are real, and which are inherited from how things have always been done.
Proposal and scope
What I will review, at what depth, on what timeline. Consulting is bounded or it becomes an endless conversation.
Analysis
I read the code, the documents, and the proposals. I talk to whoever maintains the system, who almost always knows where the problem is.
Delivery
A document with recommendations ranked by impact and cost, plus a session to discuss them with your team.