You're probably asking this after a bad week. Someone spent Friday afternoon copying numbers between tools. A new hire asked where the client files live. And an ad in the sidebar promised AI would fix all of it by Monday.

Sometimes the honest answer is "do it yourself this weekend." Sometimes it's "don't touch it until someone maps it." Here is how to tell which one you're looking at, if you own a firm with 5 to 100 people.

When can you set it up yourself?

Do it yourself when every one of these is true:

  • The work lives in one tool. Turning on meeting summaries in your video tool is a settings change, not a project. So is asking your email tool to draft replies.
  • One person runs it. Say the person who set it up is the only one who relies on it. Then a mistake costs that person an hour, not the whole team a week.
  • No client or employee data is involved. Drafting a blog outline is low risk. Pasting a client's tax return into a chatbot is not.
  • Failure is cheap and visible. If it breaks, someone notices the same day and the fix is "do it by hand like last month."

If that describes your situation, skip the consultant. Spend the money on a paid plan for the tool, and block two hours to learn it properly.

When does paying someone save money?

Bring in help when any one of these is true:

  • It crosses three or more systems. A web form, an inbox, and a practice management system. A CRM, a spreadsheet, and an accounting tool. Every handoff between tools is a place where records get dropped, duplicated, or overwritten.
  • It touches client, patient, or employee data. Before anything gets built, you need to know where that data goes and who can see it. You also need to know your obligations.
  • Several people depend on it. When a team relies on a workflow, a silent failure gets discovered late, usually by a client.
  • It already broke once. A half-built automation that "mostly works" is the most expensive kind. People stop trusting it and start doing the work twice.
  • Nobody owns it. Ask "who maintains this?" If the honest answer is "the person who set it up, and she left," you need documentation as much as automation.

What does an AI consultant actually do that you can't?

Not much that's magic. A good consultant does three unglamorous things:

  1. Maps the workflow before touching it. Most automation goes wrong because the real process has exceptions nobody wrote down. The map surfaces them.
  2. Measures the before number. Without a baseline, nobody can say whether the build saved anything, and the tool becomes another subscription you're not sure about.
  3. Puts a person where judgment belongs. Drafting can be automated. Sending to a client, approving a payment, or deciding a legal question should stay with a human.

If a consultant skips any of those three, you are paying for a build, not for advice.

What should you ask before hiring any AI consultant?

These questions work no matter who you talk to:

  • What will you measure before you build, and how will we know it worked?
  • Where does our data go at each step, and who can see it?
  • Which step stays with a person, and why?
  • What happens when it breaks, and who fixes it?
  • Who owns the build, the accounts, and the documentation when you're done?
  • Do you earn commissions on any tool you recommend?

Vague answers to the first and last questions are the biggest warning signs.

What does it cost either way?

Doing it yourself costs your time plus the software. Treat your time as real money: four evenings of trial and error is a project, even if no invoice arrives.

Raquel publishes her prices so you can compare. At launch pricing:

Every offer and timeline is on the services page.

When would Raquel tell you not to hire her?

When the work fits the do-it-yourself list above. When the workflow runs a few times a year. When the data is so inconsistent that cleanup has to come first, which is a smaller and cheaper job. And when nobody on your side can approve decisions. A build without an owner stalls.

The free diagnostic ends with a recommended first move. Sometimes that move is "nothing yet."

Still not sure?

Describe one workflow that eats your team's week. The free workflow diagnostic takes about four minutes. Raquel reads every one herself. Within two business days, you get a one-page scored read, including whether you need outside help at all.