When the problem isn't one decision.
Due diligence, an AI strategy, an engineering team to build, a CTO in the room every week. Scoped and quoted — with the ranges published, because you shouldn't have to sit through a call to find out whether you can afford us.
You don't have a question. You have a gap.
The $750 and $2,500 products answer one question, well, and most people who come here need exactly that.
Then there's the other version. Nobody in your company can evaluate a technology decision, so decisions get made by whoever presented last. Engineering spend goes out the door every month and nobody can tell you whether it bought anything.
A buyer or a lender is asking questions you can't answer about a system you depend on. You're about to hire engineers and you have no idea how to tell a good one from an expensive one.
That isn't one decision. That's a missing function — and one memo, however good, won't close it.
We publish every price we can honestly publish.
That's the whole idea here, and we're not walking it back on this page.
A Proposal Review is $2,500 because it's the same job every time: one document, one company, one week. Due diligence on a company with four systems and two hundred customers is not the same job as due diligence on one with forty and none. Quoting that blind would mean padding it — charging everyone for the worst case so we're covered. You'd pay for someone else's complexity.
So instead of a fake fixed price, you get the real ranges, below, and the specific things that move the number. Then you get a fixed quote before anything starts — same discipline as everything else on this site: one number, one scope, one date, agreed in writing before we begin.
What you will never get from us: a number that changes after you've committed, a "discovery process" you pay for, or an hourly meter that runs while we learn your business.
What changes when there's a CTO in the room.
Decisions stop being made by whoever presented last.
Right now the most persuasive vendor wins. With someone independent evaluating options against your actual business, the best option wins instead. Over a year that difference is usually larger than the entire cost of the engagement.
Your technology spend becomes reviewable.
Not "the developers said it would take three months." A number you can question, a plan you can track against, and someone who will tell you plainly when it slips and why.
You can hire engineers without guessing.
Most expensive hiring mistakes in small companies are technical hires made by non-technical founders who had no way to assess the candidate. Someone who has hired and managed engineers writes the role, screens the candidates, and sits in the interviews.
Your systems stop being one person's private knowledge.
The single most common emergency we see: the developer who knows everything leaves. Documentation, access, and continuity are unglamorous and they're what turns a business-ending event into a bad month.
You get answers in the form outsiders accept.
Boards, lenders, insurers, regulators, and acquirers all ask technical questions in a particular shape. A written answer from an independent CTO carries weight that the same answer from your vendor does not.
Nobody profits from the roadmap being bigger.
The usual "fractional CTO" is attached to an agency, and their advice reliably concludes that you need more of what the agency sells. We don't build, so the recommendation to do less — or nothing — is available to us. It's often the right one.
The engagements
Technical due diligence
Buy-side, sell-side, or pre-raise. What the technology is actually worth, what it will cost to run, what breaks at 3x the volume, what the team knows that isn't written down, and what you're inheriting that nobody disclosed. Delivered in the format your investors, lenders, or acquirers expect.
What moves the number: how many systems, whether the target cooperates, whether there's a data room, and how hard the deadline is.
AI feasibility and vendor selection
You've been pitched AI by three vendors and every deck looks the same. We work out which parts of your business actually have an AI-shaped problem, what the honest return is, what your data can and can't support, and which vendor — if any — fits. Frequently the recommendation is to do one small thing well and ignore the rest.
What moves the number: how many use cases, the state of your data, and whether you need a build-versus-buy comparison on top.
Build vs. buy decision brief
A full comparison of building it, buying it, or configuring something that already exists — with real costs over five years, not year one. Includes the option everyone forgets: not doing it.
What moves the number: how many options are in scope and how large the decision is.
Engineering team build-out
Role definition, compensation benchmarks, sourcing strategy, technical screening, and your CTO in the interview loop. For the first hire, or for going from one developer to a team.
What moves the number: how many roles, how senior, and whether you want us running the screens or coaching you through them.
Vendor and platform migration oversight
You're changing ERP, moving off a core platform, or replacing the agency that built everything. Independent oversight of the transition: what to require in the contract, what to verify at each milestone, and what to hold back payment for. We don't do the migration. We make sure the people doing it deliver what you paid for.
What moves the number: project length and how many milestones need verification.
CTO Desk — a block of hours
For clients who've completed an assessment with us and want us on call for what comes next. Questions as they arise, decisions as they land, no meter anxiety — you've already paid, so calling costs you nothing.
Available after a first engagement, because it's only worth your money once we know your systems.
Fractional and interim CTO
Roadmap ownership, vendor and team management, architecture decisions, board and investor communication. Interim coverage — a CTO who left, a crisis, a gap before a permanent hire — is quoted separately and runs near the top of that range.
What moves the number: days per week, how much of it is managing people versus making decisions, and whether it's steady-state or a turnaround.
Four steps, and only one of them is a call.
Tell us what you're facing
A form, ten minutes. What's going on, what's at stake, what the deadline is.
We tell you whether we're the right call
Within one business day. Sometimes the answer is a $750 Second Opinion instead of a $15,000 engagement, and we'll say so — that conversation has cost us real revenue and it's the reason anyone believes the rest of this page.
A scoping call — 29 minutes, free, no pitch
Only for engagements at this level, and only because scope genuinely can't be assessed from a form. You'll speak with the CTO who'd run the work, not a salesperson.
A fixed quote in writing
One number, one scope, one date, within two business days of the call. It doesn't move unless you change the scope, in writing, and agree to the change first.
This fits if:
- Technology is now a real line in your budget and nobody in the building can evaluate it
- You're heading into a transaction, a raise, or an audit and need answers that hold up outside your company
- You're about to make a decision you can't unwind in under a year
- You've been burned by a vendor and you want someone in the room whose incentives aren't tied to the build
This doesn't fit if:
- You need one question answered — start at $750, it's almost certainly enough
- You want us to build or run it; we don't, at any price
- You want a CTO title on a cap table for credibility; we do the work, not the optics
- You need someone on-site full time — at that point hire, and we'll help you do it
Questions
Why is there a call here when the rest of the site says there isn't?
Because the smaller products are the same job every time and these aren't. The scoping call is 29 minutes, free, and it's with the CTO who'd do the work. You'll get a written number two business days later whether or not you go ahead.
Is my industry covered?
The bench runs deepest in banking, fintech, insurance, manufacturing, and consumer products. For work at this level sector knowledge matters a great deal, so if you're outside those five we'll tell you honestly within a day rather than take the engagement and learn on your money.
Can I just start with something small?
Yes, and most people should. A $750 Second Opinion tells you whether we're worth more of your money, and the $750 comes off anything larger you start within 30 days.
Do you sign an NDA?
Yes, before the scoping call if you'd prefer. For due diligence that's standard.
Is there a minimum commitment?
Retainers are three months — below that, nobody learns your business well enough to be worth the money. Project work has no minimum beyond its own scope.
Does the retained CTO build things?
No. Not on a retainer either. They'll define the work, pick the vendor or the hire, manage delivery, and hold them to it — but the no-build rule doesn't relax because the engagement got longer. That's what keeps the advice worth having.
What if we outgrow you?
Then you hire a full-time CTO, and we'll help you write the role and run the search. Talking a client out of a retainer they no longer need is a normal outcome here, not a failure.
Can you work with our existing developers?
Usually that's the point. Most of this work is making sure the people you already pay are building the right thing, and giving you an informed way to hold them to it.
If it's bigger than one decision, tell us what's going on.
One business day for a straight answer on whether we're the right call. A 29-minute scoping conversation if we are. A fixed number in writing two days later.
Tell us what you're facingNot sure it's that big yet? Start with a $750 Second Opinion and decide after.