What AI should I use for my business?

Date: 9/21/2026

I’m Mike. I work with small businesses — trades, services, owner-operators who still write the customer emails and still do Friday invoices. People ask me which AI to use because they’re drowning in names.

If you already have a model you like, we can work there. Claude, OpenAI, Gemini, Copilot — at the top end they’re close enough that the logo isn’t what decides whether this pays off. What decides it is where the work lives: in a chat tab you keep copying out of, or in the actual files and tools your business runs on.

If you haven’t picked yet, I’ll save you the comparison shopping. I run Grok as the model, Cursor as the place the work lives, and Grok Bot as the teammate that keeps going when I’m away from the desk. Three tools, one setup. The rest of this page is why each one earns its spot.

1. Cursor is the shop. Grok is who I want at the bench.

Cursor is where the work happens. It sits on your computer, open on a folder of real files — the website, the checklist, the research notes, the little tool you’re building. You’re not pasting a problem into a void and hoping the answer survives until tomorrow. The files stay. The AI can see them. Agents can take a role, write something down, hand it off, and you review the result the way a general contractor checks a sub. That’s the difference between a demo and a shop.

People bounce off Cursor because it looks like a coding tool. It is one — and that’s exactly the point. If the job is “rewrite this email,” a chat window is plenty. If the job is “keep a living set of files for this business and have AI do real work inside them,” a chat window is a toy. I want the second thing, for my own work and for clients.

Grok is the model I want in that room most days. It holds its own next to Claude and OpenAI on the work I actually do. What I like is the temperament: it pushes back, stays specific, and doesn’t perform helpfulness by burying you in extra paragraphs. Grok will argue with me. Good — I’d rather argue with a tool than edit the personality back into every draft. I also want the model close to the work, in the editor where the files are, not in a browser tab I have to go visit.

I do switch when the job calls for it. Claude Opus or Claude Fable when I want the strongest writing or the most careful analysis. Astra when the work is visual — design that has to look current, or something closer to a video game than a quote email. Picking a specialist for one job is just good sense. It isn’t a reason to rebuild your whole setup.

2. The teammates that keep working when I don’t

Grok Bot is a teammate with its own computer. You give it a name and a job, and it keeps its memory, its files, and its browser from one day to the next. It can sign into your tools, keep working while your laptop is closed, and hand a task to another Bot. This is the always-on helper people thought they were buying when they turned on a copilot in their office suite — except this one has its own desk and finishes things.

Cursor cloud agents are the other half. You send a job off to a machine in the cloud, it works on its own copy of your files, and it comes back with a set of changes you approve or reject before anything is final. I use that when the work is a real edit — a page on this site, a small tool, a fix I want reviewed rather than trusted. Grok Bot can start those agents for me. I still read what comes back. The agent doesn’t get to decide.

No chat tab does this. It can’t keep a named teammate, can’t keep working after you close the lid, and can’t hand you a reviewable change to your actual files. That’s the reason I point undecided people here — not because the other models can’t write a good email, but because this is the setup that runs a shop instead of answering questions about one.

3. Why I don’t live in a chat tab

The standard advice is to open whatever you’ve heard of, type a prompt, and copy the result. That’s fine for one email, and the model in that tab may well be excellent. The model isn’t what’s holding you back. The setup is.

Here’s what a chat tab doesn’t do. It doesn’t live in your files. It forgets your business by next week unless you keep re-explaining it. It can’t put a researcher and an editor on the same folder and leave you something you can check line by line. And it defaults to a voice that sounds like every other small-business blog on the internet, which is how owners end up sending customers email that doesn’t sound like them.

I know that last one firsthand — part of this site was written that way, because I let a bot draft “helpful” copy and didn’t fight it hard enough. You can smell it. Your customers can too. A tool tuned to never make anyone uncomfortable will also never tell you the thing you needed to hear.

In a chat tab	In the setup I run
The work lives in a browser window	It lives in a folder of real files, with Grok working in them
Paste in, copy out, start over tomorrow	The files stay put. Grok Bot keeps the context between sessions.
Nothing moves unless you’re typing	Grok Bot and cloud agents keep working. You review what comes back.
One model for everything	Grok by default, Opus or Fable for heavy writing, Astra for visual work

4. What this looks like on a real job

Say you want five local competitors laid out: location, who they sell to, services, years in business, Google Business Profile reviews. Ask a chat tab and you get one confident answer in one sitting, with no way to tell which parts it made up. I hand that job to a Grok Bot with rules about what counts as a source, run an editor pass over the result, and keep the notes as files I can reopen next month. I step in wherever something looks off. That’s not a better search engine. That’s a small crew with me checking the work. I wrote about the wall a single chat runs into in Prompting vs. AI Engineering.

Same shape for the unglamorous Friday work: job notes turned into invoices, a quote that should sound like your shop, the checklist you run on every new job. None of that is won by a clever prompt. It’s won by having somewhere the work can live and a model that doesn’t sand your voice off on the way through.

5. If you want to work this way

Install Cursor and run Grok in it. Stand up a Grok Bot for the jobs that should keep moving without you. Send a cloud agent after the work you want handed back as a reviewable change instead of a wall of text.

Then bring one real job — not “help me with my business.” Brief it the way you’d brief someone at the bench: the goal, who it’s for, a sample of how you actually talk, what to avoid, and what finished looks like. Let it ask you questions first. Look at the files it touched. If the first pass is wrong, say so plainly. You’re still the one running the job.

It will feel like more than a chat, because it is. That first hour is the part I help people through. What I won’t do is help you collect another subscription you never open.

And the line doesn’t move: you own the promise to the customer, including the numbers and anything legal, medical, or financial. Keep payroll and private customer files out of a public chat. Read the terms. Ask where the data goes. That’s true no matter whose logo is on the model.

Conclusion

We can work with any of the top models, and if you already have one, bring it. If you’re still deciding, this is the answer I’d give you over coffee: Cursor, Grok, and Grok Bot, with cloud agents for the work you want handed back as a reviewable change, and a specialist like Opus, Fable, or Astra when a job genuinely calls for one. That’s the setup I’ll put a shop on. For the working habits underneath it — you’re the contractor, iterate, save your playbook — read Set the right mindset for AI next.