AI Second Opinion
Make sure your AI delivery is right — before you get burnt.
Bring me what you've got — a build, a vendor's proposal, a plan, or a running system — and get back a straight, independent read: is this right, will it survive a real business, and what would I do about it.
What it is
The independent read, before you commit
An AI Second Opinion is exactly that — an independent read you get before you commit, or before you keep going. You bring what you've got; I tell you whether it's right, whether it'll survive contact with a real business, and what I'd do about it. Buyer-side, always: I'm not the vendor, and I've nothing to sell you but a straight answer.
It's the same seat independent technical advisors have held for decades — the person in the room asking whether this is the right thing to build, whether it's being built right, and whether it'll last. The only thing that's changed is who's doing the building. Anyone can vibe-code a demo now; whether that demo survives an actual org chart is the question almost nobody's asking… yet — but will.
What you bring
A build
Something you've had made, or are having made, that you want checked before it goes any further.
A vendor's proposal
A quote, a statement of work, or a pitch you're being asked to sign — pressure-tested before you do.
A plan
An AI initiative on paper, before anyone writes a line of code — while changing course is still cheap.
A running system
Something already live that's misbehaving, or that you're simply not sure about, and want a second set of eyes on.
What you get back
A straight read: is this right, will it survive, and what would I do next. Outputs vary by scale and topic — I'd rather give you what the decision actually needs than a templated report. Depending on what you bring, that might be:
- A verdict — is this right, and why. The clear yes-or-no you can take to a board.
- A risk map — what's likely to break, and what it'll cost you when it does.
- A recommendation — whether to proceed, who to hire, or what to fix first.
Examples, not a fixed deliverable. We agree the shape in the first conversation.
When to bring me in
Best early — but useful at any point
The seat works across the whole arc of a delivery. It's worth the most at the start — but even a buyer who's already been burnt wants someone in before the next one.
Before
Most valuableShould you build this at all? Is it the right thing? Is the proposal on the table any good, and is the vendor the right one? This is where a second opinion is worth the most — and where most people skip it.
During
It's being built. Is it being built right? Will it survive? Are the builders being kept honest? A steadying hand on the work while it's live — before the problems set like concrete.
After
It went sideways. Now what? I'd rather have caught it earlier — but if you're already here, I'll tell you what's salvageable, what isn't, and the fastest way back to solid ground.
Why an independent read
Eighteen years of scar tissue
The value isn't a model — it's knowing what actually breaks when the demo meets a real business. Expired credentials, skipped tests, the marketing-versus-roadmap war, the integration nobody owned, the angry CEO. Vibe-code influencers can demo an app; they can't fake the decade. That's the part that can't be generated.
And I'm not assuring a discipline I don't practise myself. I govern my own AI delivery — the agent systems and planning pipeline behind this practice — with exactly the discipline I'd bring to assuring yours. The proof isn't an opinion; it's the work. See what I've shipped.
What it costs
No fixed price. This is the first phase of a new service, and the honest answer is that the shape — and the cost — depend on what you bring and how far you want to take it. A one-hour read on a proposal is not a two-week deep dive into a live platform, and I won't pretend otherwise.
So it starts with a conversation. If it's a fit, I'll propose a scope and a fee before any money changes hands. If it isn't, I'll tell you that too — and point you at whoever is.
Bring me what you've got.
A build, a vendor's proposal, a plan, or a running system — book a call and get a straight, independent read before you commit.