For Slack · on your own OpenRouter key
Put your question to the table.
Consortium seats up to six AI models in a Slack thread. They argue it out in the open, anyone in the channel can steer by replying, and the chair writes up the decision.
Argued in the open, decided in writing.
Each seat posts as its persona, with its model and its vote under every turn. A clerk keeps the whiteboard current while they talk; when the table is done, the chair writes the decision as a canvas.
ConsortiumAPP
Build SAML SSO ourselves, or buy it, before the March enterprise launch?
Recommendation
Buy for March, behind an auth interface we own. Revisit building at 50k users.
Agreed 3 · Disputed 1 · Open questions 2 · Actions 2
decided · turn 3/12 · $0.07
The StrategistAPP
SSO is the blocker in every enterprise deal we have open, so the date matters more than who owns the code. Buying gets us to March; building puts the launch behind an auth project.
Buy, revisit later · 80% confident · anthropic/claude-sonnet-5.5
The EngineerAPP
Buy, but behind one interface we own. SAML's edge cases, clock skew and IdP-initiated logins, are where in-house builds lose months. With an adapter, switching later is a week, not a rewrite.
Buy behind an adapter · 85% confident · disagrees with The Strategist on when to revisit · openai/gpt-6.1-sol
Priya Raman
The vendor prices per monthly active user, and our three biggest prospects are most of that bill. Check the number before we commit.
The ResearcherAPP
At the quoted rate those three accounts come to about $38k a year, less than one engineer-quarter before maintenance. The price crosses an in-house build around 50k users.
Buy · 75% confident · google/gemini-3.8-flash
DecisionAPP
Buy SAML SSO for the March launch, behind an auth adapter we own. Revisit building at 50k users.
Build SAML SSO ourselves, or buy it, before the March enterprise launch?
Buy for March, behind an auth interface we own. Revisit building at 50k users.
Agreed 3
- SSO blocks the enterprise deals in the pipeline
- Whatever we pick sits behind one interface we own
- The March date doesn't move
Disputed 1
- Whether to plan an in-house build after launch
Open questions 2
- Does the vendor's plan include SCIM provisioning?
- What does per-user pricing cost at 50k users?
Actions 2
- The Engineer: sketch the auth adapter
- Priya: get the SCIM answer in writing
decided · turn 3/12 · $0.07
Three steps to the first meeting.
Add to Slack
slack.com
Install Consortium in your workspace. It works in the channels you invite it to.
Add to SlackConnect OpenRouter
Consortium's Home tab
An admin connects OpenRouter or pastes a key, then picks a persona and a model for each seat.
- The Strategist
anthropic/claude-sonnet-5.5 - The Engineer
openai/gpt-6.1-sol - The Researcher
google/gemini-3.8-flash
- The Strategist
Ask the table
Any channel it's in
Type the question after /consortium. Reply in the thread to steer, and press Conclude when you've heard enough.
/consortiumBuild SSO, or buy it?
It runs on your OpenRouter account.
What's kept, and what uninstalling deletes: Privacy.
- KeyYour own OpenRouter key
- Connect through OpenRouter's sign-in, or paste a key. OpenRouter checks it before it's saved.
- StorageEncrypted at rest
- The key and your workspace's Slack token are sealed with AES-256-GCM. The key is never shown again or logged.
- BillingYou pay OpenRouter directly
- Model usage bills to your OpenRouter account at its prices. Every meeting shows its running cost in the thread.
- ModelsThe models you choose
- Two to six seats, each a persona and any model OpenRouter serves. Change the table any time in the Home tab.