Guide
How to land your first AI automation clients: a guide for builders
Updated · by Rosh Perera
Builders usually land their first AI automation clients through people they already know, by offering one small, drafts-first job for a business they understand rather than a big agent project. Get a written brief before the first call, agree one job you can show working, and let the owner approve every draft. This guide is for people who build agents and automations and want their first few paying clients. It pairs with our free client discovery kit for builders, which has the brief prompt, the four client levels and a printable call sheet. No income claims here: just the steps. Grok Bot facts here come from xAI's Grok Bot docs and Use cases page and Cursor's Grok Bot help, checked 20 Oct 2026. Want a first job for a client's business in five questions? Try our free What should my bot do? planner. We're an independent site, not part of xAI.
Pick your first 3 bots in 5 quick questions →What to hand to an agent first
Start with people you already know
Your first clients are rarely strangers. List past employers, businesses you buy from and friends who run something. Pick one type of business you understand, so you speak their language and can reuse what you build.
Sell one job, not "AI"
Owners don't buy agents; they buy an afternoon back. Offer one job they recognize: sorting the inbox and drafting replies, appointment reminders, quote follow-ups or invoice reminders. Our free What should my bot do? planner suggests a first job for a given business.
Get the brief before the first call
Send the owner the brief prompt from our client discovery kit for builders, or our business brief tool, and ask them to send back the answer. You walk in knowing their prices, tone and what must never be said, and the call is about one job, not a tour of AI.
Show it working, safely
Build a demo on made-up data before you ask for access. A test run performs real work (xAI's Skills and routines docs), so never test on a client's live customers. xAI's advice: "Start with a one-time task. Make it reliable, save the method as a skill, and only then automate it."
Set it up in their accounts, not yours
Have the owner sign in to their own accounts; for passwords, two-factor codes, CAPTCHAs and payment confirmations, "the Bot should hand you control of the computer" (xAI's Approvals docs). A connected app "can do only what that account can already do in that service" (Grok Bot help: Connect apps), so ask for an account with only the access the job needs. For a team, "To give the team one Bot they all talk to, publish a Team Bot" (xAI's Bots docs).
Agree how the work gets checked
Have the Bot hold its drafts, and add our daily approval list template so you approve, edit or reject them in one numbered list. An approval raised by a routine expires after about 10 minutes, and the action doesn't run (xAI's Approvals docs), so a list you check at a set time beats cards you might miss. Owners trust what they can see and approve. Our Grok Bot approvals guide covers the settings.
Turn one job into a relationship
Check in weekly for the first month. Add job two only once the owner has stopped editing the drafts, and ask for an introduction to one other owner when they're happy. Skip mass cold messages: our AI agent cold outreach guide explains why drafts-first, personal outreach works better.
Start from a template, not a blank page
xAI's Use cases page lists 56 jobs and its official Marketplace lists 90 public templates, as of 20 Oct 2026 (our Grok Bot template stats page). Our templates page has drafts-first versions with copy-ready prompts, and our free What should my bot do? planner picks a first job for a business.
Not sure which jobs fit your business?
Build my free AI plan →Or get every routine pre-written in the pack →$29 one-time, plus local tax where it applies.
Ready-made use cases
- 01Inbox triage with drafted replies
The agent sorts your inbox into reply / FYI / ignore and drafts replies in your voice for you to approve.
~5h/week · estimate - 02Appointment reminders that cut no-shows, with your OK on each day's list
Each afternoon the agent drafts reminders for tomorrow's appointments. You approve the list in one go (approve all, edit or remove), then it sends. Reschedule replies wait for your OK too. Sending without review is an optional upgrade.
~3h/week · estimate - 03Quote follow-up for unanswered estimates, with your OK on every send
Keeps the quotes you've sent and drafts a polite follow-up for each one still waiting. You approve every message before it goes out.
~3h/week · estimate - 04Invoice chaser, with your OK on every reminder
Every Monday the agent lists unpaid invoices and drafts polite, escalating reminders. You approve each one before it sends. Sending friendly first reminders without review is an optional upgrade.
~2h/week · estimate - 05One daily list of drafts to approve
Your bots hold every email, message and post they write as a draft. Once a day (or once a week) you get one numbered list and answer approve, edit or reject for each. Nothing goes out unapproved.
~1h/week · estimate
Example: Grok Bot setup
Grok Bot routine: Inbox triage with drafted replies Schedule: Twice daily 9:00 and 15:00 Twice a day, go through new emails. Label each as Reply, FYI or Ignore. For Reply, write a draft in my voice (short, friendly, direct) and save it as a draft, never send. Send me a list of drafts to approve and any FYIs worth knowing. Rules: draft first, never send or post anything external without my approval. Keep summaries short.
Grok Bot, ChatGPT, Claude and n8n versions: all templates
Setup steps
- List people you already know who run a business, and pick one type you understand.
- Choose one drafts-first job for that business, or let the planner suggest one.
- Send the brief prompt from the builder kit before the first call.
- Show a demo on made-up data, then set the job up in the owner's accounts with the owner signing in.
- Run it through one daily approval list, check in weekly and add job two only once they stop editing drafts.
Keep these human
- Don't promise time saved or results you can't show. Show a working draft instead.
- Keep clients' logins off your own Bot's computer, and set jobs up in their accounts.
- Customer calls, complaints, refunds and anything urgent stay with the owner.
- Personal Bots no longer have a description, so lasting rules go in chat: ask the Bot to remember them, like "From now on, ask before sending any email" (Grok Bot help: Edit a Bot).
- Never paste a password or one-time code in chat. Sign in yourself with Take over, then choose I'm done (xAI's Approvals docs).
- Start in draft mode: the agent prepares, you approve, then you loosen the leash routine by routine.
Want the whole system pre-written?
The One-Person AI Business Pack: CEO agent + workers, all 46 routines in 4 formats, your role pack.
$29 one-time, plus local tax where it applies.
Next: Whop checkout. $29 one-time, plus local tax where it applies, paid by card on Whop. Files arrive by email.
14-day money-back guarantee: reply to your receipt within 14 days for a full refund.
Built by Rosh Perera, who has set up AI automations for more than 40 businesses over about 3 years.
FAQ
"What is the best way to get your first few n8n automation clients?"
Start with people you already know, offer one small drafts-first job for a business you understand, get a written brief before the call and show it working on made-up data. The same steps work whatever tool you build with.
How do I get clients without a portfolio?
Build one demo on made-up data for a business type you know, and show it to an owner you already know. One working draft beats a deck.
What should I offer first?
One job the owner recognizes, such as inbox triage, appointment reminders, quote follow-ups or invoice reminders. Not "an AI agent".
How should I price it?
We don't give figures. Price one clearly described job, and agree in writing what's included and how the owner approves the work.
Should I build in my account or the client's?
The client's. Have them sign in themselves with Take over (xAI's Approvals docs), and keep their logins off your own Bot's computer.
Do I need to know how to code?
Not for Grok Bot jobs like these: you set them up in chat, connect apps and add routines without code (Grok Bot help: Onboarding).