Start with a job your team repeats every day, where the right answer is already known and a person can check the result before a customer sees it. For most small teams that is answering the same customer questions, writing first drafts, or moving information from one tool to another. Do not start with pricing, refunds, or anything that goes out without a person looking at it.
This guide is written by RoxxGen. We build AI assistants and automations for founders, so we see where a first project goes well and where it stalls. Nothing here needs a technical background.
The three-question test
Before you pick a tool, pick the job. A job is a good first candidate if you can say yes to all three:
- Does it happen often? Daily or weekly, not once a quarter. Otherwise the time saved will not be worth the setup.
- Is there a known right answer? Your opening hours, your returns policy, the steps to book a call. AI is reliable when it works from information you have given it, and unreliable when it has to guess.
- Can a person check it? Either before it is sent, or by reading a sample every week. If nobody would notice a mistake, do not automate it yet.
Five good places to start
1. The questions customers ask again and again
Every business has ten questions that make up most of its inbox. An assistant on your website that answers them from your own pages, and hands over to a person when it is unsure, saves time from the first week.
We built one for Gurukul AI Academy, an education platform. Parents and students were asking about courses, fees and admissions, often in the evening. The assistant on their website answers those questions straight away and guides families to book a counselling call. It sits inside the page a parent is already reading, so nobody has to go looking for it.
2. First drafts that a person finishes
Replies to enquiries, product descriptions, social posts, follow-up emails. Let AI write the first version from your notes, then have someone on the team correct it and press send. The rule that keeps this safe is simple: AI drafts, a person decides.
3. Moving information between tools
Copying a form submission into a spreadsheet, creating a task from an email, sending a booking confirmation. This is the least glamorous use of AI and often the most valuable, because nobody in a small team has time for it and mistakes creep in when it is done by hand.
4. Summaries
Call notes, long email threads, survey answers, customer reviews. A summary is easy for a person to check against the original, which makes it a low-risk place to begin.
5. Finding things you already have
If your team keeps asking each other where a document is or what was agreed with a client, an assistant that can search your own files and notes pays for itself in interruptions avoided.
Where not to start
- Prices, discounts and refunds. A wrong answer here costs money and trust.
- Legal, medical or financial advice. Keep a qualified person in charge.
- Anything sent to a customer with no review. Add the approval step first and remove it later, if ever.
- A job nobody has written down. If your team cannot explain how it is done today, AI will not work it out for you. Write the steps first.
- Everything at once. One job, done well, teaches you more than five half-finished ones.
How to run a two-week trial
- Pick one job using the three-question test.
- Write down how it is done today, including the awkward cases.
- Count it for a week. How many times does it happen, and roughly how long does each take? This is your before figure.
- Set it up with an approval step, so a person sees every result.
- Count again for a week. Note the time saved and every mistake caught.
- Decide. Keep it, fix it, or drop it. All three are useful answers.
What it costs
There are two costs: the tools, which are usually a monthly subscription, and the time to set them up around your own information. The second is the one founders underestimate. Budget a few focused days for a first project, and expect to adjust it in the first month as real cases come in.
Questions founders ask
What is the best first use of AI for a small business?
Answering the questions customers ask repeatedly, using your own information, with a handover to a person when the assistant is unsure. It happens often, the right answers are known, and results are easy to check.
Should AI reply to customers without a person checking?
Not at first. Start with a person approving each reply. Once you have seen it handle real cases well for several weeks, you can decide which simple replies no longer need review.
Do I need a developer to add AI to my business?
Not for drafting and summaries, which most AI tools do out of the box. Connecting AI to your website, your data and your other tools usually does need someone technical.
How long does a first AI project take?
A first trial on one job can be set up in days and judged in two weeks. Connecting it properly to your website and tools takes longer, depending on what you already use.
What should I not use AI for?
Pricing, refunds, and legal, medical or financial advice, and anything sent to a customer without a person reviewing it.
Last updated 17 November 2026. We review this guide twice a year.
Not sure which job to start with? Tell us what your team repeats most and we will reply within 24 hours with where we would begin.
Tell us what you’re trying to solve
