Automation Consultant vs. Agency: Four Doors, Four Incentives

The diagnosis-before-prescription test

There is one test that separates selling from advising, and you can run it in a single round of phone calls. Describe your messiest process to each firm and pay attention to how the conversation ends. If every conversation ends in a quote for a build, you are being sold. If some conversations end with “don’t automate this,” you are being advised.

A doctor who writes the prescription before the exam is not practicing medicine, and the same standard applies here. Suppose you want to automate chasing overdue invoices. A capable builder can wire that workflow in a week: reminder emails, escalation steps, a dashboard. But if the invoices go out late because sales hands jobs to operations without purchase-order numbers, automation just makes the wrong invoice arrive faster and more politely. The real fix was upstream, in a handoff between two departments, and no software subscription was ever going to find it.

Any firm can claim it diagnoses first. The proof is whether the diagnosis is allowed to conclude “this is not an automation problem” — and whether, for past clients, it ever actually has.

Five questions that expose each door in one call

You do not need a procurement process to figure out who is across the table. You need the right questions. Ask these on the first call, and listen less to how polished the answer is than to where it instinctively goes.

• “What would you need to learn about my business before you quote anything?” A vendor steers you to a demo. An agency asks about your funnel. A builder asks which tools you use. A diagnostician asks how work and money actually move through the company — and wants your numbers before your tech stack.
• “Tell me about a time you told a client not to automate something.” This is the sharpest question on the list. A firm paid for judgment has stories. A firm paid for builds has an awkward pause.
• “After the build, who owns it? Who fixes it when it breaks at 7 a.m. on a Saturday, and can my team change it without calling you?” You are listening for whether their business model depends on your permanent dependence.
• “If the bottleneck turns out to be a person or a policy rather than software, what do you do?” Some of the most expensive automation projects are monuments to a process nobody was willing to confront.
• “How will we know this worked?” Workflows shipped is an activity metric. Hours returned to your team, fewer errors, cash arriving sooner — those are outcomes. Notice which kind they reach for first.

When each door is the right choice

A comparison you can trust has to concede the cases it loses, so here they are. Every one of these doors is genuinely the right first knock in the right situation. The expensive mistake is not picking the wrong firm — it is bringing a diagnosis problem to a door that only sells prescriptions.

• Call the vendor when the category is already settled — you know you need a CRM or an accounting system, and the open question is which one. Vendor implementation teams know their own product better than any outsider will.
• Hire the agency when the problem truly is marketing: lead flow, nurture sequences, campaign operations. A good agency runs that machine full time and will out-execute a generalist consultant on it.
• Hire the freelance builder when the work is scoped and contained: one workflow, one team, clear inputs and outputs. For a well-defined build, a capable freelancer is often the fastest and cheapest right answer — and pretending otherwise would be selling, not advising.
• Hire the operations consultancy when you cannot say with confidence what to fix first, when the process crosses departments, when a previous automation project quietly stalled, or when you suspect the real problem might not be software at all.

What diagnose, roadmap, build, advise looks like

The engagement structure that resolves the incentive problem is one where the diagnosis is a product of its own — priced, scheduled, and finished — rather than a free prelude to a build quote. When the diagnosis is paid for directly, it is allowed to reach any conclusion, including the conclusion that you should build nothing yet.

That is how we run it at Lumina. The entry point is The Revenue Review: two weeks, a fixed fee of $4,500, focused on how revenue actually moves through your company from first inquiry to cash in the bank. At the end you are holding documents, not a pitch — a map of where hours and dollars leak out of your current process, and a sequenced roadmap that says what to fix first, what to automate, what to redesign by hand, and what to leave alone.

The roadmap is deliberately portable. You can hand it to your own team, to a freelance builder, or to us. Some owners take it and run. Others have us build the first items and stay on in an advisory role — measuring whether the hours actually came back, adjusting what didn’t land, and training your people until the system is theirs rather than ours. Because the diagnosis is already paid for, we have no reason to pad the build list, and you can check that claim against the roadmap itself: it will contain items marked not worth automating.

Start with twenty minutes

If you are standing in the hallway deciding which door to knock on, that is exactly what the free call is for. Bring your messiest process — the one that runs on a spreadsheet, a group chat, and one indispensable employee’s memory. In 20 minutes we will tell you which door it belongs to, even when the answer is a freelance build or an off-the-shelf tool you can buy tomorrow. You will hear the do-not-automate test applied to your own business before you spend a dollar on anyone, including us.

Book the call and come with the questions from the list above. If we are the wrong door, you will know before the coffee cools — and so will we.