You create your first AI tool without coding by writing two short pages, one with the facts the job needs and one with the rules for doing it, then pasting both into the AI you already use. That's the whole tool. It takes about an afternoon.
The one I built answers my customers' questions in my own words, and admits it when it doesn't know. I tested it in Claude, ChatGPT and Gemini, including ChatGPT's free version with no login at all.
Who's answering: RJ Redden, who founded NO BS AI™. She has been coaching people about technology since 1998, creates the AI tools she runs her studio on, and does not code.
I built and tested this exact tool before writing a word of this page. (Still deciding where to learn AI at all? Start with how to get started with AI for your business without the hype. This page is the hands-on part.)
An AI tool is any job you've taught an AI to do your way, so you can hand it over again and again without explaining yourself from scratch.
No app store, no subscription, no code. If you can hand the AI a page that says "here's what you need to know, and here's how I like it done," you own a tool. Most of the good ones start life as a chore you're tired of doing by hand. You'll hear them called assistants, too. Some people call them agents, which is a slightly bigger animal (more on that below).
You'll create an "Ask My Business" helper: a tool that reads a customer's question and drafts the reply from your own facts, ready to paste into a DM or an email.
Picture it: my desk, a Monday afternoon in November 2026. One person in my DMs wants to know whether the free week will trap them into paying. Another wants to know if the class is still for them when Tuesdays are bad. I have answered both of these questions, in writing, more often than I have watered my plants. (The plants would like a word.)
So I created a helper. I paste in the question, it drafts the reply from my own facts, and I read it before it goes anywhere. Then I asked it something my notes didn't cover, a refund question, and it told me so. It also told me exactly which fact to add. That was the moment I trusted it.
The recipe works for any chore with a "here's what you need to know" and a "here's how I like it." Customer questions are just the friendliest place to start. You can create yours this afternoon. Here is exactly how I created mine.
Because you're probably already asking AI to help with your replies, and it doesn't know your business. Ask a plain AI chat about your prices and it has nothing to go on, so the best you'll get is a reply generic enough to fit anyone's business.
Your two pages change that. The tool knows your real prices, dates and links. It sounds like you on a good day, even when you're answering at 9pm on a bad one. And when your notes have a hole, it tells you instead of filling it with something plausible. That's the difference between a reply you rewrite and a reply you send.
A saved-replies document gives you the same answer every time. This tool reads each new question, in whatever words the person used, and writes a reply that fits it, using only your facts.
It earns its keep when the same questions keep landing. If you answer two a month, keep typing. If you've explained your cancel policy for the 88th time, put it on your facts page once and let the tool write explanation number 89.
You need an AI chat tool, your own answers to the questions people keep asking, and an afternoon. No code.
Your tool is only as good as the questions you build it for, so start by collecting the ones you answer over and over.
Scroll back through your emails, DMs and comments. Every question you have answered more than once goes on the list, in the customer's own words. Mine came down to the same handful: what does it cost, how do I cancel, when does it happen, do I need anything first, and how do I reach a human.
Write your real answers in one plain document and give it an honest name, like "my business facts."
Real prices, real dates, real links, real policies. Use the questions as headings so the AI can find things. Here's a slice of mine:
Mine came out to about a page. If yours runs longer, that's fine. If it runs shorter, you just found out why your inbox is so busy.
Write five short rules that tell the AI how to do the job: only from your facts, honest about its gaps and ready to fill them, short, in your voice, and ending with a useful next step.
Here are mine. Borrow them.
Rule 2 is the one that matters most. It's the difference between a tool that invents a policy to be helpful and a tool you can trust with your name on it.
Open a fresh chat, paste in your rules page and your facts page (or attach them as files, if your AI lets you), then add one line: "Follow my rules page and use only my facts page." Then paste in a real customer question.
That's exactly how I tested mine, in Claude first. Three real questions went in. Here's what came back:
"If I try the free week and hate it, am I stuck paying?"
"Nope, not stuck! Cancelling is a couple of clicks on your own cancel page any time before day 8, and you're never charged. If you stay past that, it rolls into the Guild at $97 a month. One heads-up so it doesn't spook you: the card screen says Black Belt Bots, which is my studio."
"Do you offer refunds on the Foundation if I stop going halfway through?"
"I don't have that one in your notes. There's no refund policy for the Foundation anywhere in your facts, and I'm not about to make one up."
It then told me the exact fact to add, and offered a holding reply that pointed the customer to my email.
"I can't code at all and Tuesdays are bad for me. Is the class still for me?"
"Not coding is no problem at all. I don't code either! You tell the AI what you want in plain English and learn how to check its work."
It went on to mention the recordings, then asked me to add whether I actually recommend taking the class mostly from recordings, so it wouldn't oversell them.
Then I ran the same two pages through ChatGPT's free version, logged out, and through Gemini, and asked about refunds again. Same honesty, twice over. ChatGPT: "I don't have that one in your notes... You'll want to add your refund policy." Gemini: "I don't have that one in your notes. To answer this next time, add your refund policy for The Foundation class."
Three different AIs, and not one of them made up a refund policy. I'll take that from any employee.
When your tool doesn't have an answer, it says so and offers to add it. Give it the answer, and it hands back the reply for your customer plus a ready-made line for your facts page. Paste that line in and the gap is closed for good. That's the whole maintenance plan.
I tested exactly this in ChatGPT's free version. It told me it didn't have my refund policy and asked me for it. I typed a sample policy in one messy sentence, and it came back with a warm reply for the customer and a tidy "REFUND POLICY" line for my facts page. Try a few awkward questions of your own before you trust it: one your notes don't cover, one from a cranky customer, and one fishing for a discount.
Once your tool works, save the two pages where you can grab them in a second, so tomorrow starts with a paste instead of a rewrite.
Most AI tools now have a spot that saves instructions and files so they load on their own. Claude calls its spot Projects, and the free plan gets five. The others change their names and their rules often. Gemini is retiring its version for personal accounts this very month. So treat any save spot as a nice shelf, and treat your two pages as the thing you own. They move with you to whichever AI you're using next year.
Paste the question in, read the draft, and send it yourself. Your tool drafts. You decide.
When a price, a date or a policy changes, change your facts page first. A tool reading last spring's prices will quote them with total confidence.
No. This tool lives in your own AI chat, where only you can see it, and you send every reply yourself.
A tool that strangers use on your website is a bigger build with real questions attached: who pays each time it runs, what it's allowed to say, and who notices when it's wrong at 2am. It's very doable without code, and it's what we build in class. Start with the two-page recipe. It sits at the heart of every tool I've built, including the ones on the internet.
It's the first half of one. An AI agent is a tool that's allowed to take steps on its own, like sending the email, booking the call or updating the spreadsheet, without you pressing the button each time.
Every agent starts where this page starts: a page of facts and a page of rules. The agent part is the permission to act, and that's the part I'd hand over last, once the tool has earned it. My helper drafts. I send. That's on purpose.
It can, which is why Rule 2 exists and why you read every draft before it goes out.
In my tests, Claude, ChatGPT and Gemini all refused to invent a refund policy, which is exactly what I wanted. AI can still be wrong with enormous confidence. Your facts page, your rules and your own eyes are the three locks on that door.
Your second tool should be the next chore you catch yourself doing by hand for the 88th time.
The same two pages build almost anything: the welcome note for a new client that never quite sounds like you, the follow-up email you rewrite every week, the event details people keep asking about. Swap the facts, swap the rules, keep the shape.
You learn it properly in NO BS AI™, where creatives and entrepreneurs learn to create their own AI tools, no code required, minus the hype and the doom.
This page gets you one good tool. The class is where you learn to create the next ten, including tools that live on the internet. It starts with a free week, then $97 a month unless you cancel before day 8. Day two of that week is creating one small tool, so you'll be right at home. (Not sure who to learn from yet? Here's how I'd judge any AI teacher, me included: Who teaches AI without the BS?)
Last updated: November 9, 2026. Related: How to get started with AI for your business · Custom AI vs off-the-shelf software · The best AI tools for coaches