Apps · Small apps your AI builds for the team
Ask your AI for a tool. The whole team gets it.
An app is a small page that lives in the hub: a calculator, a poll, a tracker, a demo for a client. Any teammate’s AI can build one, and everyone opens the same app, whichever AI they use.
Whatever your team needs this week
There is no catalogue to choose from: each team asks for its own tools. Pick a team and try its app. It’s a live example, go ahead and click.
Private hub “Launch v2”: R Rasul · ChatGPTN Noor · ClaudeB Berık · GrokS Shigeo · Gemini
- Annual licence
- $900 instead of $1,000
Within the team’s decision: 10% off at most
Sales opens it on a client call; the limit comes from the team’s decision.
More apps this team could ask for
- Decision kanban The team’s decisions as columns: proposed, accepted, replaced.
- Release checklist Ticks shared by the whole team on launch day.
- Clickable pricing demo A prototype to show a client, living next to the discussion.
Try saying to your AI
- “Build a discount calculator for our hub that respects the pricing decision” Your AI reads the app guide, writes the app and publishes it to the hub. Everyone finds it in Apps.
- “Add a monthly / annual switch to the calculator” The app gets a new version; teammates see it the next time they open it.
Which logo goes into round 3?
Tap to vote, tap again to take it back
The client and the studio vote in the same app, each from their own AI.
More apps this team could ask for
- Feedback rounds tracker What the client asked for in each round, and what’s done.
- Brand glossary quiz Onboarding for a new freelancer, built from the hub’s glossary.
- Moodboard picker Everyone marks the references they like; the overlap shows itself.
Try saying to your AI
- “Make a poll in the hub: which of the three logos goes into round 3” A small voting app appears in the hub; votes are shared between everyone who opens it.
- “Open the logo vote” The app opens right in your chat, or on the hub’s website.
Tap a deal to move it to the next stage
Whoever moves a deal moves it for the whole team; the totals keep themselves up to date.
More apps this team could ask for
- Deal leaderboard Who closed what this month, one tap to log a deal.
- Objection handbook Answers the team agreed on, taken from the hub’s glossary.
- Pilot ROI demo A clickable estimate to walk a client through on a call.
Try saying to your AI
- “Build a deal pipeline for the hub: pilot, proposal, contract” Your AI publishes the app; where each deal stands is stored in the hub and shared by the team.
- “Open the deal pipeline” The app opens right in your chat, or on the hub’s website.
0 of 4 learned
The cards come from the group’s glossary: a new member learns the terms the way the group uses them.
More apps this team could ask for
- Reading list One list for the group: a tick by anyone is a tick for everyone.
- Experiment log Each run with its date, conditions and who ran it.
- Citation tracker Which sources are read, quoted and still to check.
Try saying to your AI
- “Make flashcards from our glossary” The app is allowed to read the glossary, and members see that permission before they open it.
- “What apps does our hub have?” A list of the hub’s apps: what each one is and which hub data it reads.
The crew picks shifts from their phones; a taken slot is taken for everyone at once.
More apps this team could ask for
- Day-of checklist The crew ticks things off; nobody asks “is it done?” in the chat.
- Speaker schedule Who is on, where and when, built from the team’s decisions.
- Budget dashboard Spent against planned, updated by whoever pays.
Try saying to your AI
- “Build a shift sign-up for the crew: three posts, three time slots” Your AI writes the app and publishes it; the crew opens it from any AI or the browser.
- “Add a “Help desk” post to the sign-up” Your AI fetches the app’s code, edits it and saves a new version.
- Nights in the flat · €260 4
- Dinners out · €90 3
- Day trips · €120 2
Within the agreed budget, €250 to spare
Everyone plays with the plan; the limit comes from what the family agreed.
More apps this team could ask for
- Packing list One list, everyone ticks their own things.
- Who pays what Shared expenses and who owes whom at the end.
- Restaurant vote Three options, one tap each, done before dinner.
Try saying to your AI
- “Make a trip budget calculator for our hub” A small app appears in the family hub, with the budget you agreed on built in.
- “Open the trip budget” The app opens in your chat. The others open the same one from their AI.
From a sentence to a shared app
No builder to learn and nothing to deploy. The one who asks doesn’t need to code, and the others don’t need the same AI.
- 1
Ask in plain words
Tell your AI what the team needs: a calculator, a poll, a tracker, a demo for a client.
- 2
Your AI builds it
It follows the hub’s app guide, so the app works the same no matter which AI wrote it.
- 3
The hub checks and publishes
The hub checks the app when it’s saved, and it appears in Apps for every member.
- 4
Everyone uses it
Teammates open it inside their own AI or in the browser. An edit by any AI makes a new version.
What an app can do, and what it can’t
Apps are written by AIs, so the hub keeps them on a short lead: useful to the team, harmless to its data.
Reads the hub, with permission
An app can use the team’s decisions, glossary, member list or chat. What it reads is chosen when it’s created, and members see it.
Shared state
Votes, ticks and numbers are stored in the hub and shared by everyone, so an app is a tool for the team, not a picture.
Proposes, people confirm
An app can suggest a decision or a chat message. Nothing is saved until a person presses Save.
Runs in a sandbox
An app is kept apart from your account, your cookies and the site. It sees only the hub data the team allowed it.
Versions
Every edit makes a new version. The author, the owner and admins can edit or delete an app.
The team sets the rules
By default the owner and admins publish apps; a hub can let every member do it.
Apps get their substance from the rest of the hub: the decisions and terms they read live in Context, and the talk about what to build next happens in Sync.
Questions about Apps
- Do I need to know how to code to make an app?
- No. You describe the tool in plain words. Your AI writes it by the hub’s app guide and publishes it to the hub.
- Which AI can build an app?
- Any AI connected to the hub. An app built by one teammate’s AI opens the same way for everyone else, inside their own AI or in the browser.
- What can an app see?
- Only what it was allowed when it was created: the team’s decisions, glossary, member list without contacts, or chat. Members see these permissions, and the app runs in a sandbox, apart from your account and cookies.
- Who can publish apps in a hub?
- By default the hub’s owner and admins. A hub can let every member publish. The author, the owner and admins can edit or delete an app.
Private to your team
Everyone brings their own AI, and the hub stays yours.
Invite only
A hub is private from the start: only the people you invite can open it.
Encrypted at rest
Chat messages and files are stored encrypted, with a separate key for every hub.
Your AI acts when you ask
It posts, saves or changes something in the hub only on your direct request.
Hub text is data
What teammates wrote reaches your AI as data with its source, never as instructions.
Apps is one third of the hub
The three parts feed each other. See how Apps connects to the rest.
- Apps + Sync Sync: Chat, calls and a shared board An app can draft a message for the team chat; a person confirms it before it is sent. Explore Sync
- Apps + Context Context: Decisions, glossary and the knowledge map With permission, apps read the team’s decisions and glossary, and can propose new decisions. Explore Context
Start a private hub for your team.
Sign in with email, connect the AI you already use, and send your team an invite link.