For twenty years I've been called in after the build went wrong. It almost never failed on the code. It failed on a decision made in week one - by people who wouldn't be in the room when the cost landed eighteen months later.
I'm the person you bring in before that.
I'd rather talk you out of a project than sell you one you'll regret. That position has cost me revenue. It's also why clients from 2011 still call.
You can hire a dozen people with a similar résumé. What you can't get elsewhere is how someone decides. Here is mine, in the open - before you spend anything.
Every system hard-codes an assumption about how you will grow. Get it wrong and no amount of engineering rescues it - which is why this conversation belongs to the owner, not only the engineers.
By the time a project looks like it is failing, the decision that killed it is six months old. I front-load the uncomfortable questions, because that is the only point where being wrong is still cheap.
Most "AI transformation" pays good money to make waste move faster. First we establish whether the process should exist at all. The cheapest system in your business is the one you deleted.
A system only its builder understands is a liability with a good interface. Handover is a design constraint, not a closing phase. You should be able to fire me without consequence.
Speed is easy to sell and expensive to unwind. Where money, inventory, or patients are involved, fast-and-wrong is the costliest outcome available - and it arrives disguised as progress.
Every recommendation carries three figures: what it costs, what it returns, and what doing nothing costs. An advisor who will not quantify their advice is selling comfort.
"Don't build that." "Buy it off the shelf." "Wait two quarters." I have said all three to paying clients. It is why engagements here become decade-long relationships instead of transactions.
Not marketing lines - the filter every recommendation passes through before it reaches you.
See how each one plays out →Most proposals arrive with the answer already in them - because the answer is what the firm sells. These four questions have reshaped more engagements than any technology I've recommended.
Not "can it scale" - that question is useless. Name the component, the number, and the month.
Whether your growth plan and your systems were designed by people who spoke to each other.
Owners point at the cloud bill. The leak is usually idle time, rework, and deals lost waiting on a report.
The real ROI ceiling - and whether technology is even the right instrument.
Replatform or patch. Build or buy. Keep the vendor or leave. Always the real blocker, never on the brief.
The engagement you actually need - often not the one you asked for.
If the answer is a name, we design for that person. If it is silence, we just found the most important requirement.
Whether we are building an asset or a dependency.
Owners rarely call about technology. They call about a decision they can't un-make cheaply. These three come up most.
Which processes deserve AI - and which to fix, outsource, or kill instead.
A pilot that demos beautifully, never reaches production, and dies in month seven.
A ranked shortlist tied to money, a first build chosen because it is winnable, and a written case for every no.
Replatform, wrap, or replace - and in what order, so trading never stops.
A two-year rewrite sold as inevitable and delivered as a hostage situation.
Phases that each pay for the next. The legacy system runs until it is genuinely unneeded. Stop anywhere without loss.
Spend problem, architecture problem, or a process problem wearing an invoice.
Cloud cost-cutting that saves twelve percent and returns within two quarters.
The actual leak named - often outside the cloud bill - with the structural fix separated from the cosmetic one.
If one of these is on your desk, the conversation is free and the opinion is honest - including the version where you don't need me.
You've read how I think. This is that thinking meeting real budgets and real deadlines. Names withheld under NDA; sectors and outcomes are real.
The rewrite they asked for would have cost eleven months and stopped trading twice.
Kill criteria agreed in writing before the first camera was mounted.
Half the gain arrived before any software shipped, from a process change.
“What stood out was the architecture discussion up front, before anyone wrote code.”
Founder · Healthcare Chain
“Instead of hype, we got a clear assessment, a phased plan, and a partner who stayed hands-on through the build.”
Plant Head · Manufacturing
Pick the shape that fits your situation. The investment is set once we understand the requirement - never before.
Thirty minutes, no deck, no discovery ritual. Bring the decision you've been circling and you'll leave with a straight opinion - including the version where the honest answer is that you don't need to hire anyone.