Hire a guild, not a chatbot — the finance, legal, people, IT and platform expertise a small company cannot yet hire
Do the expert work.
Keep the expertise.
A guild is one profession's working craft — a term sheet, vendor terms, a compensation band, an AI inventory, a cloud bill — running inside the Claude, ChatGPT, Cursor or Copilot your team already has. It asks what a specialist would ask, computes what a specialist would compute, and cites the dated source behind every figure. Then it writes what it learned about your company into your own files, so the third month is easier than the first.
The hall — … guilds, one subscription
Curated: every guild is written and maintained by Guildhall. Every count on this page — skills, traps, eval cases, dated changes — is computed from the guild's own files by the registry build. A guild cannot list a skill, an eval or a change it doesn't ship.
Reading the registry index…
How a guild works
Four steps. Nothing here runs on our servers, and nothing of yours reaches them.
Install into the assistant you already use
One command in the terminal — guild add contracts — or, with no terminal at all, a file you upload to Claude. No account either way. The guild arrives as a folder you own and starts working inside Claude, ChatGPT, Cursor or Copilot — whichever your team is already in. Nothing of yours is sent to us; installs are counted from downloads, anonymously.
Answer the setup questions once
The guild asks which country's rules apply before it does anything else, then keeps what it learns — your entities, contracts, systems, headcount — as plain files on your side. They are there the next time you open it, and they are yours.
Every figure is computed, never guessed
For each trap the guild knows how to spot it, what it is costing you, how to fix it and — the part a generic answer always misses — when that fix would be the wrong move. Every number in the report is calculated, with its source and the date it was checked printed beside it. The assistant is instructed never to do the arithmetic itself. What you get is a runbook a person reads and runs.
Stay current as the world moves
Term standards move, rates reset, cloud pricing changes. Each one arrives dated, with its source, what it affects and what to re-check in your own numbers. Updating is one command, and a version that fails its own tests is never published. That stream is what the subscription buys; cancel and every file you have stays.
What the guilds leave behind
Every review writes what it learned into a folder you own. By month three you have a knowledge base you did not have — and it stays yours if you leave.
One profile, asked once
Entities, countries, sector, size, which regimes apply. The first guild asks; every other guild reads the answer instead of asking you again.
Vendors joined across guilds
The same supplier is a contract in Contracts, seats in Licences and a data processor in Privacy. One row puts the renewal, the idle seats and the missing DPA in front of you together.
Decisions and deltas, dated
Waivers and approvals with who, when and why. A ledger of every run, so the monthly review opens with new, resolved and persisting instead of rediscovery. Written up as memos an auditor or a new hire can read. No personal data — the book refuses it.
What changes every month
The value is the stream,
not the download.
A download is worth what it knew the day you got it. A guild ships a dated record of what changed in the world — rates, dates, data models — so your assistant's knowledge doesn't rot while the official pages move. The most recent changes across the hall, read from the guilds' own migration files:
- reading the migration files
One plan, per company
or 490 € / year — two months free, one invoice for procurement.
- Every guild in the hall, and every guild published later, for everyone in the company
- Every update: new traps, new calculators, every dated migration with its state actions, every figure promoted to first-party
- The Company Book: the profile, vendor register, decisions log and dated ledger your guilds keep in your own files
- Invoice with your VAT id and a data-processing agreement on request — there is no customer data to process, and the DPA says so
- Installing was never the paid part:
guild addis free, with or without a plan
Card handled by Stripe; we never see it. Stripe collects your company name, billing address and VAT id for the invoice. Cancel any time from the customer portal — you keep every file you have and stop receiving updates.
Try a guild first. Subscribe when the first update you would have missed lands.