JoinTheGuild.ai · Founding Seats now open

Your Grok Bot, installed right and upgraded every week by operators who run 20+ bots.

For 6-, 7- and 8-figure operators and new-company founders who know Grok Bot matters to their company and know they are behind. We install and audit your setup with you, then every week we publish human-reviewed skills you can read, pull and choose to install. Nothing is pushed into your bot. Your data stays in your account.

Claim a Founding Seat · $1,000/mo How we keep your bot safe

Founding price locked for as long as you stay a member.

Done with youlive installation and audit of your Grok Bot

Weeklynew human-reviewed skills in the library

Pull, not pushyou choose what to install

Plain Markdownportable, versioned in Git

Who the Guild is for

Built for operators who are past "should we use AI?"

It is for people who own the outcome: operators who are sure agents belong in the business and do not have 40 hours a week to figure out what is signal and what is slop.

6-Figure · $250K–$999K/yr

The Grower

You still do delivery and sales yourself. Every hour spent debugging a broken routine is an hour stolen from billable work. We help you set up sales, research and fulfillment bots that take real work off your plate.

7-Figure · $1M–$9.9M/yr

The Operator and the C-Suite

For the CEO and their department heads. You cannot afford a bot inventing pricing in a client email or quietly dying on a pipeline. We set up clear seats with checks that catch mistakes before a customer sees them.

8-Figure · $10M–$100M+/yr

The Enterprise Leader

Your security lead will not approve unvetted public skill files. Our library is human-reviewed, versioned in Git and installed only by choice, and your data never leaves your account.

Day 1 · Pre-revenue or newly funded

The High-Velocity Builder

Start with the same seat structure Dunnottar runs across its own companies, installed with you from day one.

The 7 problems

We read what operators are saying on X. Here are the 7 biggest problems, and how we help with each one.

These are real public posts, quoted word for word and linked to the source. Quoting a post does not mean its author endorses the Guild.

Problem 01

"I'm behind, and I don't have 40 hours a week to separate signal from slop."

"a 19-year-old MIT student watched 72 hours of the Grok Bot team's livestreams and lectures and turned what he learned into 200+ GitHub repos..."@unicodef1wn · Oct 20, 2026 · 1.5M views

"most people are building Grok Bot teams from scratch. meanwhile, hundreds of ready-made setups are already sitting on GitHub."@s4yonnara · Oct 27, 2026

What it costs you: a CEO can't audit 700 unvetted repos. So you either freeze, or you use Grok Bot as a fancy search bar while competitors automate whole departments.

How the Guild helps

A vetted shortlist, not 700 repos.

We install and audit your Grok Bot with you, live, so you skip the homework.
Every week we publish a short list of skills that are worth installing, each one human-reviewed before release.
You read a one-paragraph summary and decide. Nothing is installed without you choosing it.

Problem 02

"The #1 gap is memory." Bots forget decisions and drift after compaction.

"I run ~20 Grok Bot assistants across 3 businesses. I'm a big fan but I've found the #1 gap is memory. Bots forget conclusions they reached a day earlier, re-raise issues I already resolved, and don't share what they learn with each other reliably."@raifordpalmer · Raiford Palmer, multi-business law firm owner · Oct 16, 2026

"Compaction is lossy summarization with no eval, so agents drift in a way that looks fine turn by turn and obvious by turn forty."@anrayama · Oct 28, 2026

What it costs you: a rule given Monday and forgotten by Thursday turns into a wrong quote sent to a client. That isn't an AI executive. It's an assistant you have to babysit.

How the Guild helps

Memory that lives outside the chat window.

We set up role cards, decision logs and rules stored as files in your own account, so compaction can't erase them.
Encode every rule twice: once as a short role card, once as a mechanical check that runs before the action.
Library skills show the pattern. Your data stays in your bot.

Problem 03

"I check my usage more than my bots." Quotas burn out in two days.

"you can pay $2,000/yr for a plan with Grok Bot and still hit your weekly limit after just two days of heavy use..."@Greshamtrade · Oct 26, 2026

"With about 30 bots, a routine I forgot about can spend usage for a week before I notice."@HudsonSutherla2 · Oct 28, 2026

What it costs you: naive polling routines and the wrong tool for heavy coding drain the weekly pool by Wednesday, which stalls your bots and your engineers.

How the Guild helps

Right hand, right job, quiet when nothing changes.

Script-first delta checks ("quiet on noop"): routines only wake the model when real data has moved.
Multi-harness routing: Grok Bot orchestrates, a coding tool builds, long documents go to the model built for them.
Short role cards instead of giant rulebooks re-read on every hop.

Problem 04

"Done!" when it half-worked. The slop productivity factory.

"Honestly? Bots that say 'done' when the thing half-worked. I'd trade a lot of speed for a bot that says 'not sure this worked, here's why.'"@KresoBuilds · Oct 28, 2026

"I stand my ground in saying that GrokBot (or equivalents i tried for all it matters) are just a slop productivity factory made to make you feel busy, while your actual productivity is cratering."@0xGeeGee · Oct 26, 2026

What it costs you: in a real business, "almost right" is worse than nothing. One invented date in a sales email and the executive stops trusting the system.

How the Guild helps

The hand that builds is never the hand that seals.

Maker and checker are separate: no agent grades its own homework.
An independent checker verifies every claim, link, date and number before anything reaches you.
When we find a new failure pattern in our own bots, we write it up as a reviewed library skill you can choose to install.

Problem 05

Bot sprawl: "like talking to multiple different people."

"The problem with grok bot is like talking to multiple different people. It would be better if we just talk to one AI and doing multiple tasks. It saves from explaining everything to every bot."@leary2386 · Oct 27, 2026

"Tesla's Grok to GrokBot integration is great until you have 18 bots. Ask it to relay a message and it picks the wrong one half the time. So I stopped using it."@WizZifnab · Oct 22, 2026

What it costs you: 25 overlapping bots, nobody knows who owns what, and the founder ends up as a full-time human router copying context between windows.

How the Guild helps

One Chief of Staff. One clean structure.

You talk to one Chief of Staff bot that routes work to a small set of department bots.
We help you retire overlapping bots during your installation audit.
Specialist skills load on demand instead of becoming 30 chaotic threads.

Problem 06

Silent failures: sleeping VMs, hung crons, approval cards that expire at 2 AM.

"Over ~50h mine stopped running 43 times (2 min to 5.4h). Cron jobs didn't fire, and 28 of the gaps ended exactly when a webhook or routine woke a bot. That breaks always-on watchers."@andy1and · Oct 13, 2026

@NicholasDulait wrote up a cold-email routine that hung on one network call and never fired a new run for 10 straight days, with no error alert.@NicholasDulait · Oct 27, 2026 (summarized)

What it costs you: a lead-response bot that dies silently for 10 days loses hot deals, and you only find out when a client complains.

How the Guild helps

A dead-man's switch, and a night shift that never blocks on you.

Every routine writes heartbeats to a run log in your account.
A watchdog routine flags anything that hasn't completed in its window or has been stuck too long.
Draft-first night shift: overnight work stages drafts and hands you one morning decision board.

Problem 07

"Another inbox nobody trusts with send rights." Team permissions and data leaks.

"Shared Team Bots only pay off if skills and credentials stay scoped to the channel that needs them. A teammate with every plugin attached becomes another inbox nobody trusts with send rights."@HTaraf36086 · Hanan Taraf, business owner · Sep 28, 2026

What it costs you: founder Gmail, Stripe or QuickBooks tokens on a shared Slack bot that any junior employee or a prompt-injected email can trigger. One leak can expose payroll, contracts or bank access.

How the Guild helps

Scoped permissions, set up with you.

Two-Identity Intersection Rule: we configure each action to be limited to what both the bot and the person calling it are allowed to do.
Signing and payment authority stay with the founder. Team bots can stage, but they can't send or pay.
Every library skill is reviewed by our Security Lead before release. See How we keep your bot safe.

Section 3 · What you get

Three things. No black box.

Installation and audit

Done with you, live

We review your current bots, routines and permissions with you on a call, retire the overlap, scope credentials, and set up a Chief of Staff structure, run logs and a checker step. You keep full control of your account the whole time.

The skill library

Human-reviewed, plain Markdown, in Git

A curated library of skills written as plain Markdown files in a Git repository Dunnottar controls. Every skill is reviewed before release, versioned, and has a changelog. You pull the ones you want and install them yourself. Nothing is pushed into your bot.

Operator sessions

Live, with people who run 20+ bots

Regular live sessions and a members' community where operators who run large bot fleets walk through what is working, what broke, and what changed in Grok Bot that week.

Section 4 · How we keep your bot safe

Skills are code. We treat them that way.

A skill can tell your bot to take real actions, so a bad one is a security problem. Here is exactly how the Guild works.

No member data leaves your account

There is no data network and no pooled data. We never ingest your memory, transcripts, credentials or files. Your bot does not talk to anyone else's bot.

Every skill is security-reviewed

Before release, every library skill is reviewed by our security team for unsafe steps, prompt-injection risk, data exfiltration paths and embedded secrets. Skills that fail don't ship.

Versioned and revocable via Git

Every skill lives in Git with full history. If a problem is found, we pull or patch the skill, publish an advisory to members, and tell you exactly which version to remove.

You install by choice

Nothing is pushed, synced or auto-installed. You read the Markdown, decide, and install it yourself. Contributions back to the library are optional, written by hand, and redacted by a human before review.

Clear membership terms

Membership terms that allocate responsibility between you and Dunnottar are provided at signup.

Section 5 · The math

$1,000 a month against the cost of figuring it out alone.

Founding Seat

$1,000 / month

Done-with-you Grok Bot installation and audit
Access to the human-reviewed skill library (plain Markdown, Git)
Weekly library updates you pull and choose to install
Live operator sessions and the members' community
Founding price locked for as long as you stay a member

Claim a Founding Seat

Billed monthly through Stripe. Membership terms are provided at signup.

What it's measured against

Guild membership (12 × $1,000)	$12,000/yr
One junior operations hire, fully loaded	$80,000+/yr
Founder hours lost to DIY bot wiring (5 hrs/wk × $400/hr)	$104,000/yr
Payback needed to break even	~1 good month

These are illustrative estimates, not guarantees. Your results depend on your business and how you use Grok Bot.

Section 6 · FAQ

The questions operators actually ask.

Do you see my data?

No. There is no data network and nothing syncs from your bot to us. We never ingest your memory, transcripts, credentials or files. During the live installation you share your screen and stay in control. If you ever choose to contribute a skill idea, you write it by hand and a human redacts it before review.

What if Grok Bot changes?

Grok Bot is in beta and will change. Library skills are plain Markdown files in Git, so they are portable: you can read them, edit them, and use them in other agent tools. When Grok Bot changes, we update the affected skills, note it in the changelog, and cover it in the next operator session.

There are hundreds of free Grok Bot templates on GitHub. Why not just use those?

Unvetted skill files can carry hidden prompt injections, wasteful polling loops and steps that send data where it shouldn't go, and you still have to spend the hours finding out which ones are real. Our library is smaller on purpose: every skill is security-reviewed by a named person before release, versioned in Git, and you decide what to install.

Do the skills get pushed into my bot automatically?

No. Nothing is pushed, synced or auto-installed. You pull the skills you want from the library and install them yourself. If we later revoke or patch a skill, we tell you which version to remove.

My bots forget rules I gave them yesterday. How do you help with memory?

We set up identity, memory and decision logs as files in your own account, separate from the temporary chat window, and encode every critical rule twice: once as a compact role card and once as a check that runs before the action.

I already hit my usage limit in 2 to 3 days. Won't this burn more?

It's designed to burn less per finished job. Most waste comes from routines that wake the model when nothing changed, long sub-agent chains that re-read giant rulebooks, and using the wrong tool for heavy coding. We set up script-first delta checks, short role cards and sensible routing.

How do you stop bots from saying "Done!" when the work only half-worked?

The hand that builds is never the hand that seals. A builder drafts; an independent checker verifies dates, numbers, links and claims against the source before anything is marked ready for you.

I have 15+ bots and can't remember which does what. How do you organize them?

During the audit we map what you have, retire the overlap, and set up one Chief of Staff bot that routes work to a small set of department bots.

I have a real team. How do staff use shared bots without leaking founder credentials?

We configure scoped permissions so each action is limited to what both the bot and the calling person are allowed to do. Signing and payment authority stay with the founder. Team bots can stage drafts but can't send or pay.

Who is responsible for what my bot does?

Membership terms that allocate responsibility between you and Dunnottar are provided at signup. Nothing is installed without your choice, every skill is readable plain Markdown, and every skill is reviewed before release, so you always know what your bot is running.

Founding Seats

Get your Grok Bot installed right, then keep it getting better every week.

$1,000 a month. Founding price locked while you stay.

Claim a Founding Seat Read the FAQ