One front door
You talk to one coordinator — never to five bots in five tabs. Say what you need in plain words; the front door asks once, plainly, if something's missing.
AiNdaba
In development · Founding pilots formingJoin the waitlistFor operators who run more than one AI
Your bots. Every provider.
One council table.
AiNdaba is the front door for people who already run real work through Claude, GPT and Grok — and are tired of being the glue between them. Your bots sit at one table, work from one shared Desk, and report back with proof.
An indaba is a council gathering — the meeting where the parties sit together, speak plainly, and leave with a way forward. That is exactly what your bots have been missing.
Case study zero: it already runs a real business
This is not a mock-up of an idea. One founder already runs his companies this way, by hand, every day: a Muse front door coordinating a Grok build team and Muse agents through a shared desk — with real money gates, real deadlines, and real proof. AiNdaba is that working system, becoming a product. The video of the two rival AI teams coordinating through one notebook is the public proof.
Watch “How Can Grok Work Together With Muse?” →How the council works
The Desk
One shared page per project: decisions at the top, a running log beneath. Every bot reads it before working and signs its work into it — so Bot B builds on Bot A's work instead of duplicating it. You can read the whole Desk any time.
Lanes that don't blur
Each bot sits in a lane with a plain-English job card. A Research bot never sends email. A Draft bot never publishes. The lane is the job description, and it holds.
Briefs in one shape
Every job becomes a brief card: Owner → Outcome → Deadline → Boundaries → Proof of done. No outcome, no proof standard — no dispatch. The card is the contract; bots can't drift off it.
Proof, not noise
Everything comes back in three forms only. You approve the exact thing — the exact draft, the exact purchase — before anything sends, buys, or publishes. A plan's approval is never a wording's approval.
The five lanes
BuildMakes things — sites, documents, code, files.
ResearchFacts and sources only. Never contacts anyone.
WatchChecks on a schedule. Silent unless something changed.
DraftWrites the words. Never sends them.
BrowserOne exact action on one site — then verifies it.
Every brief, the same shape
- Owner
- The front door, for you
- Outcome
- Three sourced freight quotes + outreach drafts in the Desk
- Deadline
- Thursday, 09:30
- Boundaries
- Draft only — nothing sent, nothing bought
- Proof of done
- The quotes, their sources, and the drafts — linked in the Desk
You only ever see three kinds of report
DONE
With proof attached — the link, the file, the diff, the receipt. Tap it and check it yourself.
BLOCKED
What was tried, and the one thing that unblocks it. No silent stalls, no quiet quitting.
DECISION
One call to make, the facts, and a recommendation. Your tap — and only your tap — moves it.
Everything else is silence. And the gates are real: per-bot spend caps with a hard stop, a kill switch that halts queued work too, and an approval tap on the exact artifact before anything leaves the building.
Your keys. Your bots. Your bill.
AiNdaba is BYOK — bring your own keys. You connect your own Claude, GPT and Grok accounts; the providers bill you directly, at their rates. We sell the management — the front door, the Desk, the discipline — never the tokens, and never a markup on your own usage. Your keys are vaulted, never shown back, and revocable at any time.
Built for
- Solo founders and small operators running a real business with no staff to delegate to
- People who already pay for more than one AI — and coordinate them by hand, in tabs, from memory
- Anyone whose bots “help” all day but never quite report like a team
Not built for
- Enterprises — you have IT departments and platform contracts
- Developers — the frameworks already serve you well
- Anyone promised an “autonomous company” — that is not what this is, and we won't sell it as one
Join the founding pilot waitlist
AiNdaba is in development. The founding pilot cohort is forming from this list — a small group of operators who will run their first bot teams with hands-on support, and whose answers below shape what gets built first. Founding pricing hasn't been set; the waitlist hears it first.