How you manage and evolve it
Your Hub grows by asking
Change a report, a skill or a routine, or build something new, by saying what you want in plain English. Claude drafts it, one of your people approves it, and it’s live. Your team owns every part.
Build something new
New skills and tools, from an idea to everyday use
When your team spots something the Hub can’t do yet, they ask for it. Claude helps them say what’s missing, your admins build what they can, and anything bigger comes to us as a scoped proposal.
Safe to change
Nothing goes live until its owner says yes
Every change is checked, then approved by the person who owns that knowledge, never by the person who asked for it. Every version is kept, so anything can be undone.
Your developers stay in control
Your tech team owns it. Fully.
Everything lives in your own accounts, as plain files in your GitHub. Your developers see every change before it ships, run their own checks, and decide what goes out.
The roles that run it
New roles, made for this way of working
AI has created job titles that didn’t exist two years ago. Here’s what each one does, and who does it in your Hub.
Next step
Find what’s costing you, and fix it
Start with a conversation about your pain points and manual processes. We’ll help you automate them with AI.