How do you make the case for AI automation to a founder, not a CFO?

Why isn’t “prove the ROI” the real objection?

It sounds like a request for a number. Usually it isn’t. A thread on r/dataanalysis describes exactly this: a boss asking someone to “prove” automation ROI, with honest estimates for the underlying task swinging anywhere from about 5 minutes to over an hour, depending on which assumptions you plug in. That swing is the tell. When the same facts support two estimates twelve times apart, the person asking usually isn’t trying to reach a precise figure. They’re checking whether you can defend the decision when someone pushes back on it.

A separate thread on r/CustomerSuccess gets at what actually kills a business case once it reaches whoever controls the budget: not that the math is wrong, but that the case doesn’t survive the first real objection asked of it.

For a founder with no CFO and no finance function sitting between them and the decision, that objection is almost never “your model’s discount rate is off.” It’s simpler, and it doesn’t have a line item to attack: “just do it manually” or “we’ll build it in-house.”

What’s actually different about pitching a founder instead of a CFO?

A CFO’s job is to evaluate a model. Hand them defensible assumptions and a sensitivity range, and they can do the rest of the analysis themselves, inside a process built for exactly that.

A founder deciding personally doesn’t have that process to hand it to. They’re moving fast, weighing the proposal against two alternatives a CFO would rarely reach for: staying manual a while longer, or having someone build it in-house instead of buying it done. An ROI model built for enterprise procurement answers a question this buyer isn’t holding. It doesn’t move the two objections that are actually in the room.

The three-part argument that actually works

Skip the calculator. Make three claims, each checkable in one sentence.

1. Name the manual cost in hours, this month, not a five-year projection. Not “over three years this saves $180,000.” Instead: “this is eating roughly 12 hours a week from someone whose time is worth doing something else with, starting now.” A founder can check that number against what they already see happening on the team. They can’t check a discounted cash flow.

2. Name the in-house alternative honestly, and show what it doesn’t remove. “We’ll build it ourselves” sounds free because the platform genuinely is cheap: Zapier, Make, and n8n all start under $70 a month. What it doesn’t answer is who owns it in six months, and what happens the week that person is out sick, promoted, or gone. The in-house option doesn’t remove the work. It moves it onto someone’s calendar, indefinitely, usually without anyone deciding that on purpose.

3. Make the ask small enough to approve without a finance process. A founder without a CFO is personally on the hook for every dollar they approve. Asking for a build before anyone has mapped the actual workflow is asking them to approve your estimate. Asking for a small, fixed, refundable amount to get a written plan first is a different, much smaller decision, and it’s the one that actually gets a yes.

How do you name the manual cost without sounding like you’re guessing?

Be specific about the task, not the department. “Automate support” is a guess dressed up as a number. “Someone spends roughly 45 minutes a day manually copying ticket data from Zendesk into the CRM” is checkable: you can watch it happen, time it once, and multiply. The credibility of this whole pitch rides on the first number being one the founder could verify themselves in an afternoon, not one that only survives if they trust your model.

How do you handle “we’ll just build it ourselves”?

Ask two questions out loud, in the pitch, rather than arguing against the idea in the abstract: who owns this a year from now, by name, and what’s the plan for the week they’re not available. If there’s a real, specific answer, the in-house option might genuinely be right, and it’s worth saying so. Zapier, Make, and n8n are the correct answer for workflows that are simple, stable, and have someone willing to maintain them indefinitely. Most of the time, though, the honest answer to “who owns this” is “whoever has time,” and that’s not an owner. That gap, not the build cost, is what a founder is actually being asked to accept if they choose the in-house path without naming who’s responsible for it.

How do you make the ask small enough to approve on the spot?

Anchor it against the two things a founder is comparing you to: hiring someone (roughly $120K a year, plus three to six months to ramp) and an enterprise vendor ($50K and up, over roughly six months). Against either of those, a $1,500 discovery step that turns into a written, prioritized blueprint for the highest-ROI workflow reads as small, not as the sales pitch. And it’s structured so the ask stays reversible: if the founder proceeds to a build within 30 days, the $1,500 is credited in full toward the $10K–$20K Sprint. If they don’t, they keep the blueprint and owe nothing further.

That’s the version of “prove the ROI” that actually resolves the objection: not a bigger spreadsheet, but a smaller, checkable, refundable first step.

What does this pitch look like end to end?

Put the three parts in order and it reads like this: “This is costing us about 12 hours a week right now, on a task we can watch and time. Building it ourselves on Zapier looks cheap, but nobody on the team is signed up to own it past the first six months. I want to spend $1,500 on a written plan for our highest-impact workflow, credited in full toward the build if we go ahead, and we walk away with a blueprint either way.”

That’s a decision a founder can make without a finance team, because every claim in it is something they could check themselves.