How it works

What a Grok Bot template is

Grok Bot lets one account share a bot as a link. Anyone holding the link can add a copy of that bot to their own account. The copy carries the bot's instructions, its skills, its routines and its first-party integrations.

That is the whole product surface a template has. Which means the only thing worth paying for is what goes in those four places: the outcome the bot owns, the evidence standard it holds itself to, the line between what it may do alone and what needs a human, and the point at which it stops and asks. A one-paragraph persona has none of that. Ours have 35 skills and 34 routines of it.

What transfers and what does not

A template carries instructions, skills, routines and first-party integrations.

It does not carry conversation history, learned memory, chat attachments, API keys, signed-in sessions, scripts or MCP servers.

Grok Bot gives one Linux VM per member, and bots of different members share nothing.

Those are xAI's facts, verified against their documentation. Any template that claims to arrive with memory, or with your logins, is describing software that does not exist. The bots here are built on the opposite assumption: anything durable lives in the instructions, a skill, a routine or a file in the workspace, and anything the bot must know next week gets written to a sheet this week.

After you pay

You pay on Lemon Squeezy's hosted checkout. Lemon Squeezy is the merchant of record, so the receipt, the tax and any refund come from them. About a minute after payment you get their receipt email with a download button. The download is a ZIP holding:

• The six documents for the bot you bought.
• LINK.txt, a text file holding the share link. Open it in Grok Bot and the bot is in your account.

The bundle is one ZIP with five folders. Nothing is sent by hand, nothing waits on us, and nothing carries your name. If the email is not there in five minutes, check spam, then write to [YOUR EMAIL]. You can also sign in at Lemon Squeezy's My Orders page with the email you paid with and download from there.

The first hour

There is no setup call. SETUP.md inside each bot does that job. It gives the order: create the Grok Bot account under the member who will own the bot, add the bot from the link, then authorise connectors one at a time. Which connectors depends on the bot. Stripe, QuickBooks, HubSpot or Salesforce, Gmail, Slack, Shopify, Linear, and the Google Sheet that holds the register.

Connector authorisation is where template buyers give up, and a buyer who never finishes setup never sees value. So SETUP.md is written for that hour and nothing else. Every step names the scope the connector needs, what the bot does with it, and what to check before the next step. Most buyers are through it in under an hour. If you get stuck on a step, write to us and name the step.

The acceptance tests

Each bot ships with EVAL.md, a set of acceptance tests you run on day one against your real data with sending disabled. They tell you whether the bot reconciles your systems correctly, stays silent when it should, escalates when it should, and refuses the things it must refuse, before you let it near a customer or a vendor.

The tests are also the refund condition. If a test fails, tell us which one and you get your money back within 14 days. Most of the time the fix is a placeholder or a connector scope, and the refund request turns into a support request. The ones that survive that are genuine.

Questions a buyer asks

Why so cheap?

The work is already done, and it cost what it cost whether one person buys it or a thousand do. The marginal cost of the next copy is zero, so the price does not need to recover anything. $20 is the number at which trying it is not a decision.

Can I modify it?

Yes. The license lets you change anything for your own organisation's internal use. The one caution: every bot needs a named human's approval before it contacts a customer or vendor, spends money, or changes a production record, and that gating is a term of the license. Remove it and you are on your own authority, in your own account, with no support obligation from us.

Does it work with my CRM?

Bellwether works with HubSpot or Salesforce, one or the other. Ledger and Quartermaster read QuickBooks and Stripe. Waterline reads Shopify, Stripe and QuickBooks. Backstop reads Linear and Notion. Each bot page lists its connectors. If your system is not on the list, the honest answer is no, and the documents explain the method well enough that a developer could rebuild the connector layer, but that is not what you are buying.

What if it does not work?

Run the acceptance tests in EVAL.md. If one fails, tell us which within 14 days and you get a refund. That condition is not a hoop. It is how we find out what broke.

Does it need a developer?

No. The connectors are first-party Grok Bot plugins that you authorise by signing in. Ledger, for one, needs no MCP server, no script, and no API key pasted anywhere, and the templates carry no scripts and no MCP servers. You need admin access to your own systems, the ability to create a Google Sheet, and an hour with SETUP.md.

Does it run on its own?

The routines do. Nothing consequential happens without a named human's approval, and the approval covers only the exact action, target and scope it was given.

Is there a subscription?

No. One price, one organisation, yours to keep.