Earlier notes. Same idea: what is working for small businesses using AI, and what is not.
The questions your callers ask every week are your FAQ, already written.
The questions your callers ask every week are your FAQ, already written.
Most FAQ pages are written from the other end: what the owner thinks people should ask. The phone tells you what they actually ask, in their words.
So start with a list, not a page. For the next week, every time someone calls with a question, write down the question and what you told them. Then paste the list into this prompt from my free library:
"Create an FAQ from these common questions: [PASTE Q&A]. Return as collapsible sections for a website."
Read what comes back before it goes anywhere. The answers still have to be yours.
You can also try it in the live demo on the page. No signup.
Open your own contact page and read it the way a stranger would.
Open your own contact page and read it the way a stranger would.
It is the one page on your site you never use, because you never need to contact yourself. So it is where setup leftovers survive: sample text the template came with, a thank-you message nobody wrote, a form that emails an inbox nobody checks.
None of that is serious on its own. Together it tells a visitor that nobody has looked at this page since it went up.
It matters more once you automate. Whatever runs after that form starts with what the form collects, and somebody has to read it first.
The readiness checklist on my site is five checks. One of them is whether someone on your team can review results.
If the button on your website says "Schedule", the person who clicks it thinks they are booking a time.
Often they are filling in a contact form. Name, email, maybe a box for a preferred date. Then nothing says what happens next, so they wait, and they assume the time is theirs.
Nobody did anything wrong. The label just promises more than the form does.
There are two honest fixes. Put a real calendar behind the button. Or keep the form, call it a request, and say when you will reply.
On my booking page, one button opens the calendar and tells you to look for the booking confirmation. The other lets you ask a question without choosing a calendar slot.
The chat window looks private. It's just you and a text box, so it's easy to paste in a customer's email, a complaint with their name on it, or last month's invoices.
Treat it the other way round. Don't paste anything into ChatGPT, Gemini or Claude that you wouldn't email to a stranger. And on a free tier, check the data settings before customer details go anywhere near it.
None of that makes the tools less useful. Emails, summaries and first drafts work just as well with the names taken out.
A quote request comes in while you're in the middle of something.
A quote request comes in while you're in the middle of something. You'll answer it tonight, once you've had a proper look.
That's the right instinct for the quote. It's the wrong one for the reply. The person who asked can't see that you've read it. All they can see is that nobody has answered, and they may be asking someone else while they wait.
The quote takes as long as it takes. The first reply doesn't have to wait for it.
That's the job of the Quote Request Responder on my services page. It answers the enquiry in minutes, and you still write the quote. $495 for that one workflow.
Most meetings end with everyone agreeing. Fewer end with anyone agreeing who does what by when.
Most meetings end with everyone agreeing. Fewer end with anyone agreeing who does what by when.
There's a prompt in my free library for exactly that gap:
"Turn these meeting notes into next steps with owners and due dates."
Paste your notes in. The useful part isn't the tidy list it hands back. It's the lines where it can't fill in an owner or a date without guessing. Each one is something the meeting talked about and never decided. Don't let it guess. Take those back to the room.
When a software pricing page shows a monthly price, read the line underneath it before you compare anything.
When a software pricing page shows a monthly price, read the line underneath it before you compare anything.
Sometimes the big number assumes you pay for the whole year up front, and the month-to-month price is a different, higher figure in smaller type. Neither is a trick on its own. But put one tool's yearly-billed price next to another's monthly one and you are not comparing prices any more.
Two questions before you sign. What does it cost for the year? And what happens if you want out in month three?
For the first one, across everything you already pay for, there's a free tool on my site that turns your monthly bills into a yearly number. No email, under a minute, nothing saved.
A lot of small businesses I look at aren't short of software.
A lot of small businesses I look at aren't short of software. They have several tools, each doing its one job well, and a person copying things from one to the next.
Bookings in one place. Payments in another. The mailing list in a third. Every one of them works. None of them knows what the others just did.
A new tool rarely fixes that. Joining the ones you already have usually does, which is why what I build sits on the tools you already use.
The copy-and-paste step between your apps is usually the whole job.
Is your website actually yours? Not your name on the page. Your name on the domain, and the login in your hands.
Is your website actually yours? Not your name on the page. Your name on the domain, and the login in your hands.
Last month I looked through a batch of small owner-run businesses in this part of Maryland. A lot of them had no working site of their own: a parked domain, a lead-gen listing, or a site rented from a marketing vendor that would not come with them if they left.
That matters more once you add automation. A booking form or a follow-up message built on rented ground belongs to whoever holds the login.
What I build goes on the tools you already own. No white-label platform underneath, and you keep everything if we ever part ways.
Ask an AI to draft your business plan and you'll get one that reads well.
Ask an AI to draft your business plan and you'll get one that reads well. Revenue by month, a break-even point, a margin. Every line looks like it came from somewhere.
It didn't. Writing is the part these tools are good at. The numbers are the part they can't do for you, and they will produce plausible ones if you let them.
That's the myth worth dropping: that a filled-in number beats an empty cell. A blank tells you what you still need to find out. A plausible number tells you nothing and looks finished.
ChatGPT or Claude will draft the plan. The figures have to come from you.
You're with a customer when the phone rings, so you let it go.
You're with a customer when the phone rings, so you let it go. That's the right call. The trouble is the person on the other end, who now has nothing.
The first build on my services page is for that moment. When a call is missed, the caller gets a reply you approved in advance, and the enquiry is passed to you to pick up. $495 for that one workflow.
Two details matter more than the price. The reply is approved, not improvised: nothing goes to a caller that you haven't signed off. And phone-system compatibility is checked first, so you find out whether your phone can do it before you have paid for anything.
You answer customer emails one at a time. That is the right way to answer them and the wrong way to read them.
You answer customer emails one at a time. That is the right way to answer them and the wrong way to read them.
Ten emails read separately are ten small problems. Read together, they are usually two or three, repeated.
One of the 53 free prompts on my site does that read for you:
"Turn these 10 customer emails into 3 improvement priorities with KPIs."
Take the names out, paste in the last ten, and run it in ChatGPT, Gemini or Claude. The KPIs it suggests are a first guess. The three priorities are the part worth keeping, because they are a list of what your customers keep having to ask you.
If you keep re-explaining your business to an AI assistant, the fix is one document you write once.
If you keep re-explaining your business to an AI assistant, the fix is one document you write once.
The free first part of my DIY guide calls it a Business Brain: 2–4 pages on who you are, what you sell and charge, how you talk, and your policies. It goes into every project, and you update it quarterly instead of retyping it every time.
The two lines I would fill in first are the short ones: "Things we do NOT do" and "Never promise." The rest describes you. Those two set the edges, and the edges are what you want an assistant to know before it writes to a customer.
Three things never go in it: tax ID numbers, bank details, passwords.
When someone tells you how long a build will take, ask what the clock is waiting on.
When someone tells you how long a build will take, ask what the clock is waiting on.
A timeline is only as honest as its conditions. Mine is written down: a single automation is usually ready in about a week, larger workflows typically take 2–3 weeks, and access to your tools and review of sample inputs are checked when we agree the schedule.
That last part is the one worth reading. Two of the things a schedule depends on sit with you, not the builder: getting them into your tools, and showing them what the real inputs look like.
A timeline with no conditions attached is not a faster promise. It just hasn't been checked yet.
One local business website I looked at this week has been taken over.
One local business website I looked at this week has been taken over. Open the home page and you get a gambling site. I doubt the owner knows.
That's the trouble with anything you set up and stop looking at: it keeps running whether it's doing what you meant or not. An automation is no different.
So the question isn't only what it does. It's how you'd find out it stopped doing it, and how you'd switch it off. My FAQ answers that in writing: test cases, exceptions and manual checks are agreed before handoff, and the handoff instructions tell you how to pause a workflow.
This week, open one thing you set up and forgot about. Look at it the way a customer would.