A second-opinion engagement is a single piece of senior judgment on a single decision, delivered in writing, without a retainer. The team that asks for it already has an in-house engineering function it trusts. What it lacks, on the specific decision in front of it, is an independent senior reader who has seen the same shape of decision elsewhere and can name what the in-house team cannot easily see from inside the room. The engagement begins, ends, and is over. The deliverable is a short memo. The relationship does not have to continue.
When a second opinion is the right shape
Three situations ask for it cleanly.
The first is the architectural decision that will harden in the next four to six weeks and is hard to revisit later. A choice of message bus. A choice of vector store. A choice between building and buying a piece of the AI stack. The team has a recommendation. The recommendation may well be right. The cost of being wrong is high enough that an external senior read is cheap insurance.
The second is the post-incident review where the in-house team is either too close to the failure to read it cleanly or too senior in the room for anyone to push back on their reconstruction. An external read produces a document the team can attach to its own incident record without having to defend it against itself.
The third is the vendor selection where the principal has been pitched by two or three credible vendors and the differentiation is technical rather than commercial. An hour of senior judgment on the specific architectural trade-offs, in writing, often resolves the choice faster than another round of vendor calls.
What the engagement is not
It is not a fractional CTO engagement. It is not the start of a retainer. It is not a pitch to take over the work. The studio does not propose itself for the next phase unless the client asks; the cleanest second opinion is one where the reader has no interest in the subsequent build.
It is also not a rubber stamp. If the in-house team is hoping for confirmation, the engagement will sometimes return a different answer than the one expected. That is the reason for asking.
A second opinion that always confirms is not a second opinion. It is a courtesy.
How it runs
The engagement has two formats.
The single-call format is one to two hours, fixed fee, on a specific documented decision. The team sends, in advance: the decision, the alternatives considered, the reasoning, and the artefacts the in-house team has produced so far. The call is not a discovery session. It is a conversation between two senior readers who have both already done the homework. A short written memo follows within two business days.
The scoped engagement format is one to three weeks, fixed fee, for an architecture review or an incident review where the read requires reading code, tracing data flow, or interviewing more than one engineer. The deliverable is a written document the team can attach to its own decision record. The format is the same as a Counsel diligence — short, specific, defensible.
Either format is closed at the end. The studio does not stay. The studio does not invoice for follow-on time without a fresh engagement letter. The team owns the memo and decides what to do with it.
What the team gets out of it
Three things, in order.
A defensible artefact for the decision record. The next senior engineer who joins the team — six months from now, eighteen months from now — will be able to read the memo and understand the decision without having to reconstruct it from a Slack archive.
A named list of failure modes the in-house team would not have seen from inside. Not because the in-house team is not good. Because the failure modes the studio has seen are, by definition, the ones the in-house team has not yet had to live through.
A second pair of senior eyes on the engagement, with no interest in the next phase. The cleanest read available.
If a specific decision is in front of an in-house team and the team would benefit from one defensible second opinion before the decision hardens, write to the studio. Tell us the decision, the alternatives, and what the team has already documented. We will reply within two business days with whether the engagement is one we can answer well.