To be clear from the start: Grok Bot is not another chatbot. You do not ask it questions, you hand it a job. It has its own cloud computer — browser, files, terminal — signs into the tools you already use with your accounts, works the screen the way you would, and comes back when the job is done.
xAI launched it on 11 August 2026, still in beta. Keep three products apart: Grok Bot (AI teammates), Grok Build (a terminal coding agent) and Build Mode (an app builder inside the consumer chat). Most commentary online mixes them up.
How is this different from chatting with ChatGPT or Grok?
The difference is not which model is cleverer. It is the shape of the thing.
Chat: you ask, it writes a paragraph, you copy that paragraph into another system.
Bot: you state the outcome, it works inside your tools, and the result stays in the real system — the CRM record is updated, the invoice is logged, the ticket exists.
And unlike most automation tools, there is no workflow to build first. You message it and it works out the steps. You can also demonstrate a job once and it saves it as a routine.
What it actually does
xAI's own published internal examples:
Sales: update the CRM with call notes and draft the follow-up
Operations: onboard a new hire, process invoices arriving in Gmail
Engineering: reproduce a bug in the product UI, file the ticket, hand it to another Bot
The point is that it finishes. Most AI gets you ninety percent of the way and leaves you the awkward last ten — the part that needs a login, a click, and three different systems.
Where a Hong Kong SME could actually use it
Do not start by trying to replace a person. Start with work that is repetitive, reversible, and checkable:
Website admin: add products, change prices, publish case studies, update opening hours — the clicking you do yourself today
Enquiry triage: collect WhatsApp, form and email enquiries into one sheet each morning, flagged by what needs a reply today
Monthly reconciliation: match bank statements against invoices and list what does not reconcile
Contact cleanup: get business cards and old customer lists into the CRM with company and title filled in
Recurring reports: pull numbers from two or three systems into one page on the same day each month
All five share one property: a mistake can be redone, nothing goes out to the public, and no money moves.
What it costs
There is no standalone Grok Bot subscription; it comes with a Cursor or Grok plan. As of October 2026 the published prices are US$20 per month for Cursor Pro and US$30 per month for SuperGrok, with weekly usage included and overage billed by token; teams are US$40 per seat.
At launch in August it required Cursor Ultra at US$200 per month, and the price fell to these levels within a fortnight. Pricing in this category is still moving — check the vendor page on the day you buy.
Three limits the documentation admits
Leaving these out would make this an advertisement.
All Bots share one computer. The marketing page says “Bots have their own computer”. The documentation says all of your Bots use the same persistent cloud computer, that isolation is per account rather than per Bot, and — verbatim — that you should not use separate Bots as a security boundary. So a file or a login one Bot picks up is reachable by the rest.
Deleting a Bot does not clear its logins. The FAQ describes deletion as soft: files and sessions a Bot established may remain on that shared machine. You have to revoke access at the source.
Passwords, 2FA and payments still need a human. The Bot stops and asks. “24/7 unattended” is therefore not quite right: what it can do while you sleep depends on what you approved in advance.
If you want to try it
Create a dedicated account for the Bot — not your own
Grant only the permissions the job needs, never admin on day one
Pick a first job that is reversible, internal, and does not move money
Keep payments, outbound messages and anything destructive on human approval
Review quarterly: which Bots still earn their place, and what can they still reach
What this has to do with your website
The first thing an AI teammate runs into is whether your systems have a place a human can log into and change things.
With an admin panel and a clear content structure, a Bot moves as fast as your staff. With everything hard-coded into pages and every text change routed through a developer, it cannot help — because you cannot get in either.
That is why we build sites the way we do: the assets should be yours, and changing content should not require asking permission. AI teammates make that more important, not less.
Should you care yet?
Honestly: if your repetitive work takes under an hour a day, there is no rush. These tools pay off on tasks that happen every day, take half an hour or more, and cross two or three systems.
Count how many of those your business has. Three or more, and a one-month trial on real work is worth it — not a demo.
We are not going to sell you “AI transformation”. But if you want a straight answer on which task to hand over first, and whether your site needs fixing before you do (admin, content structure, permissions), book a 30-minute call. If it is not worth doing, we will say so. Our prices are public on the pricing page.