The minimum tool stack for a new AI services agency

What you need on day one, what to add only when a client needs it, and what to skip.

By AI Service Playbook · Tool details checked September 30, 2026

Disclosure: This guide contains affiliate links for Make, HighLevel and ElevenLabs, each labeled. I may earn a commission if you purchase through my link, at no extra cost to you. I only list a tool where it fits a specific service, and I list free alternatives too.

Most people starting an AI services business buy tools first and look for clients second. It feels productive. You sign up for a CRM, an automation platform, a voice tool and two AI writing apps, and you spend your first month learning dashboards instead of talking to businesses.

This guide takes the opposite approach. It lays out the smallest tool stack that lets you deliver a real service, and says when each extra tool earns its place. It doesn't claim any tool will win you clients. Tools help you deliver the work. Finding clients is still a sales job.

The one rule: the service picks the tools

Before you open any pricing page, write your service in one sentence:

"I deliver ___ for ___ within ___."
For example: "I set up an automatic follow-up message for new web leads for local home-service businesses within five working days."

Now list the steps a client's data goes through in that service. A web form is filled in. The lead lands somewhere. A message goes out. Someone gets notified. Each step tells you what kind of tool you need, and often the client already owns one that can do the job.

If you can't write the sentence yet, you don't need any paid tools yet. Start with the free First AI Service Offer Kit and pick one service first.

Layer 0: what you already have

These cover a surprising amount of early work, and most are free or already on your computer:

  • A separate business email on your own domain or a dedicated free account, so client work doesn't mix with personal mail.
  • A booking link from your calendar app, so prospects can pick a time without back-and-forth.
  • A spreadsheet as your first CRM: business name, contact route, date contacted, reply, next step. It's enough for your first prospects.
  • Two document templates: a one-page proposal and a delivery note that explains what you built, how it works and how to turn it off.
  • A way to send invoices, through your bank, accounting software or payment processor.
  • The AI assistant you already use for drafting. You don't need a separate paid writing app for every task.

None of these are exciting. All of them are needed before the paid tools matter.

Layer 1: automation, when your service connects apps

If your service moves information between apps (form to spreadsheet, spreadsheet to email, missed call to text message), you need something to connect them. This is where an automation platform comes in.

Make

Make (affiliate link, opens in a new tab) is a visual automation builder. You drag modules onto a canvas (for example "watch new form entries", then "add a row", then "send an email") and connect them into what Make calls a scenario. The visual layout makes it easy to show a client exactly what happens to their data, which helps when you hand the work over.

What it costs to start: when I checked Make's pricing page on September 30, 2026, it listed a Free plan with no time limit and up to 1,000 credits a month. Each module action, such as adding a spreadsheet row, counts as one credit. That's enough to build and test a sample scenario before you have a client. Plans and limits change, so check Make's pricing page before you quote a client.

Use it when: your service involves two or more apps that don't talk to each other natively, and the client wants it to run without anyone pressing a button.

Skip it when: the client's existing software already has the automation built in. Many CRMs, booking tools and email platforms include basic "when X happens, do Y" rules. Using what the client owns is cheaper for them and easier to maintain.

Alternatives worth knowing: Zapier (a long-established option with a simpler, step-by-step editor) and n8n (which you can self-host if you're comfortable running a server). Pick whichever your first client already uses, or the one you can explain most clearly.

Layer 2: a CRM or client platform, when you manage pipelines for clients

A spreadsheet stops working when you're running follow-up sequences, calendars and conversations for several client businesses at once. That's the point where an agency platform can make sense.

HighLevel

HighLevel (affiliate link, opens in a new tab) is an all-in-one sales and marketing platform built with agencies in mind. You can set up separate accounts for each client business, with contacts, pipelines, calendars, email and text follow-up, forms and workflows in one place. It comes up constantly in AI and automation agency tutorials and communities, which is why it's worth understanding even if you don't use it yet.

What it costs to start: HighLevel's pricing page (checked September 30, 2026) offers a 14-day free trial. The same page says billing begins automatically at the end of the trial unless you cancel, and that usage-based fees for things like phone and text messaging may apply even during the trial. If you start a trial, put a reminder in your calendar a few days before it ends, and decide on purpose whether to continue. See HighLevel's pricing page for current plans.

Use it when: you're selling a service that lives inside a CRM, like lead follow-up, appointment reminders, missed-call text-back or reactivating an old contact list, and you expect to run it for more than one client.

Skip it when: you only have one client, or your service is a one-off deliverable (a content cleanup, a report, a set of message templates). A platform subscription is a monthly commitment. Take it on when a client need justifies it, not before.

A note on texting: if your service sends text messages for a client, learn the consent and registration rules for business texting in the client's country before you switch anything on. Messages should only go to people who agreed to hear from that business.

Layer 3: AI voice, only if your service includes audio

Voice is the layer most beginners add too early. Only add it if your offer actually includes voiceovers, audio content or voice agents that answer or place calls.

ElevenLabs

ElevenLabs (affiliate link, opens in a new tab) generates natural-sounding speech from text and offers tools for building voice agents. For an agency, the common uses are voiceovers for a client's videos or training material, and voice agents that answer simple questions or take messages.

What it costs to start: ElevenLabs' pricing page (checked September 30, 2026) lists a Free plan, but the commercial license appears from the paid Starter plan upward. If you're producing audio for a paying client, check that your plan covers commercial use. See ElevenLabs' pricing page for current details.

Use it when: the client has asked for audio or a voice agent, and you've agreed in writing what the agent can and can't say.

Skip it when: you're adding voice just because it demos well. A voice agent that gives a wrong answer to a real customer is worse than no agent.

Two trust rules: only clone a voice with the written permission of the person it belongs to, and check the rules on telling callers they're speaking with an AI where your client operates.

Match tools to your service

Here's how common starter services map to the layers above. "Optional" means only if the client doesn't already have something that does the job.

ServiceLayer 0AutomationCRM / platformVoice
Content cleanup and repurposingYesNoNoNo
Lead follow-up message sequences (written only)YesNoNoNo
Automatic follow-up for new web leadsYesYesOptionalNo
Missed-call text-backYesOptionalYesNo
Simple monthly reporting dashboardYesYesNoNo
Video voiceoversYesNoNoYes
Voice agent that takes messagesYesOptionalOptionalYes

Notice how many services need nothing beyond Layer 0. If you're unsure which service to start with, one of those is a low-cost way to get your first delivery done.

A 3-question test before you add any tool

  1. Which client deliverable needs it? Name the client or the signed scope. "Future clients" doesn't count.
  2. Can the client's existing software do this? Ask them what they already pay for. You may be able to build inside it.
  3. Who maintains it after handover? If the answer is "me, forever", price ongoing care into your offer (see the pricing guide) or choose a simpler setup.

If you can't answer all three, wait. You can almost always sign up later, in minutes, when a real need shows up.

Common tool mistakes

  • Building a "stack" before an offer. Tools don't decide what you sell. Your target customer's problem does.
  • Forgetting trial end dates. Trials that convert automatically are a common way to spend money by accident.
  • Putting client data into tools without asking. Get the client's OK before you paste their customer information into any AI tool, and check each tool's data and privacy settings.
  • Owning everything in your own account. Decide up front whether automations and accounts live under your login or the client's, and what happens if the engagement ends. Write it in your agreement.
  • Skipping the quality check. Automations break when an app changes. Test every workflow with sample data before it touches real customers, and recheck it after any change.