Seats for your people, a space for every team, a crew of AI bots in each.
Your people work with the crews, and you decide who sees and does what.
On your own keys, or on shared GPUs from$1,000a monthOr your own private server, from $4,000 a month
What your teams use it for.
Pick a team. Each one at Quayside has a shared space: its people, its crew, the jobs the crew takes, and the one decision that still comes back to a person.
Calls answered, tickets closed, the hard ones handed to a person.
Vera answers the support line and Bea the help desk, from the help center and the service terms.
No page of its own yet.- NadiaSupport lead
- FelixSupport
- InesFounder
- VeraPhone line
- BeaCustomer support
- Answer the support line and write each call into Callbacks
- Answer tickets from the help center and the service terms
- Book a callback when a contract or a refund comes up
- Keep the help articles current after each release
Pellam Couriers wants 40 more vans on the contract. Nadia takes Thursday’s call.
- Zendesk
- Slack
- Gmail
- Google Calendar
Every lead followed up, every proposal from the rate card.
Cass prepares each demo, follows up leads and renewals, and drafts proposals that wait for Mara.
Sales & marketing- MaraSales
- InesFounder
- CassSales
- Write a brief before every demo
- Follow up leads and renewals after Monday’s pipeline review
- Draft proposals from the rate card
- Write each call’s outcome into the CRM
The proposal for Ashby Vans is ready. Mara sends it.
- HubSpot
- Gmail
- Google Calendar
- Google Meet
Launch notes, the newsletter and case studies, in your voice.
Faye writes from the release notes and the brand voice. Lior publishes.
Content creation- LiorMarketing
- MaraSales
- FayeMarketing & content
- Draft the announcement, the customer email and three posts from the release notes
- Write the first-Tuesday newsletter
- Turn a customer call into a case study draft
- Keep the release page on the website current
The Route planner 3.0 post is drafted. Lior publishes it.
- Mailchimp
- Webflow
- X
- Canva
Exports matched, odd lines explained.
Tove matches the bank feed to invoices each morning and prepares the accountant’s pack. Payments wait for Sana.
Accounting- SanaFinance
- TomásOperations lead
- ToveFinance
- Match the bank feed to invoices every morning
- Explain the lines that don’t match
- Prepare the accountant’s month-end pack
- Draft the chase for each overdue invoice
A supplier invoice is 12% above its quote. Sana decides whether it’s paid.
- QuickBooks
- Stripe
- Google Sheets
- Gmail
Monday’s numbers ready, recurring checks done.
Rook pulls the week’s numbers into one sheet, runs the recurring checks, and flags what changed.
Daily operations- JonahOperations
- TomásOperations lead
- RookOperations
- Pull Monday’s numbers from the help desk, the CRM and billing into one sheet
- Run the recurring checks: invoices sent, renewals due, on-call covered
- Chase vendors whose contracts come up
- Flag what changed since last week
Two vendor contracts renew next month. Jonah picks which to renegotiate.
- Google Sheets
- Notion
- Slack
- Linear
Security questionnaires answered from the policies you approved.
Quill answers each question from the approved policies, with the passage it came from, and checks the evidence on Fridays.
Compliance- ElinEngineering
- TomásOperations lead
- QuillCompliance
- Answer customer security questionnaires from the approved policies
- Show the passage each answer came from
- Check each control’s evidence against the cloud console on Fridays
- Draft the quarterly access review
Three questions have no approved answer yet. Elin writes them.
- Vanta
- GitHub
- Google Docs
- Datadog
Job posts written, applications sorted.
Jude writes the post from the scorecard, sorts applications every evening, and proposes interview times.
Recruiting- InesFounder
- ElinEngineering
- JudeRecruiting
- Write the job post from the scorecard
- Sort new applications against it every evening
- Propose interview times from the team’s calendars
- Draft the replies to candidates
Five candidates reached the shortlist. Ines picks who to interview.
- Ashby
- Google Calendar
- Gmail
- Google Docs
A client’s go-live, in a space of its own.
Harlow Freight has its own space. Wynn keeps the go-live plan current and answers Harlow’s questions from their contract.
No page of its own yet.- YusufEngineering
- NadiaSupport lead
- InesFounder
- WynnOnboarding
- Keep Harlow’s go-live plan current as each depot comes on
- Answer Harlow’s security questions from their contract and your policies
- Prepare the weekly check-in from the fleet list and open tickets
- Draft replies in the harlow-golive group chat
Harlow asks to move go-live a week earlier. Yusuf answers.
- Slack
- Google Drive
- Google Calendar
- Docusign
Your company in One.
A seat for each person, a space for each team, and a crew in every space. Several people work with the same crew, and a bot works only inside the space it belongs to.
People on the left
Everyone signs in as themselves, with the spaces they were given.
Spaces on the right
Each has its crew, its Library, its connected tools and its rules.
One crew, many people
Support's three people all work with Vera and Bea, and see the same record of what they did.
Select a person or a space. Quayside, its people and its crews are fictional.
Works in 4 spaces: Support, Sales, Hiring, Harlow Freight.
- Vera
- Bea
- Cass
- Jude
- Wynn
Works in 3 spaces: Finance, Operations, Security reviews.
- Tove
- Rook
- Quill
Works in 2 spaces: Support, Harlow Freight.
- Vera
- Bea
- Wynn
Works in 1 spaces: Support.
- Vera
- Bea
Works in 2 spaces: Sales, Marketing.
- Cass
- Faye
Works in 1 spaces: Marketing.
- Faye
Works in 1 spaces: Finance.
- Tove
Works in 1 spaces: Operations.
- Rook
Works in 2 spaces: Security reviews, Hiring.
- Quill
- Jude
Works in 1 spaces: Harlow Freight.
- Wynn
- Nadia
- Felix
- Ines
- Vera Phone line
- Bea Customer support
- help.quayside.example
- Service terms.pdf
- Fleet customers.csv
- Ask before sending external email
- Approved by Nadia and Ines
- Mara
- Ines
- Cass Sales
- Rate card.xlsx
- Fleet customers.csv
- Proposal template.md
- Ask before sending external email
- Approved by Mara
- Lior
- Mara
- Faye Marketing & content
- Brand voice.md
- Release notes
- Pellam case study.md
- Ask before publishing to the website
- Approved by Lior
- Sana
- Tomás
- Tove Finance
- Chart of accounts.xlsx
- Bank statements 2026
- Supplier list.csv
- Ask before purchases
- Ask before sending external email
- Flag unexpected actions
- Approved by Sana and Tomás
- Jonah
- Tomás
- Rook Operations
- Monday numbers.xlsx
- Vendor contracts
- On-call rota.md
- Ask before purchases
- Approved by Tomás
- Elin
- Tomás
- Quill Compliance
- Security policies.md
- Evidence checklist.xlsx
- Answered questionnaires
- Ask before sending external email
- Approved by Elin
- Ines
- Elin
- Jude Recruiting
- Hiring plan.md
- Support engineer scorecard.md
- Ask before purchases
- Ask before sending external email
- Approved by Ines
- Yusuf
- Nadia
- Ines
- Wynn Onboarding
- Harlow contract.pdf
- Harlow fleet list.csv
- Go-live plan.md
- Ask before sending external email
- Approved by Yusuf
You decide who sees and does what.
People and roles
Invite people by work email. Owners and admins run the workspace; members work in the spaces they’re given.
Access per space
Choose who can enter each space, and whether they work with the crew, change it, or approve what it asks.
Rules per space
Bots act without asking by default. You decide what needs approval in each space, and who approves.
Who sees what.
People & roles
Change a role, or remove someone’s access.
Access to a space
Choose what each person can do in this space.
What needs approval
Until you always allow it.
Bots act without asking otherwise.
Credits used this month, by space
7,540 of 120,000 included creditsYour model providers bill their usage separately.
Work arrives where it already arrives.
A call to the support line, a thread in Slack, a message on WhatsApp. Each lands in the right space, the crew does its part, and the decision reaches the person who owns it.
- Slack
- Telegram
- Telnyx
- Plivo
- Vonage
- Exotel
- Vobiz
Wherever your deployment has them set up. Group chats work in Slack and in iMessage or SMS.
- Dana at Pellam Couriers calls: six vans stopped syncing mileage.
- Vera fixes the sync on the call, and hears Pellam wants 40 more vans.
- Caller
- Dana, Pellam Couriers
- Solved on the call
- Mileage sync: restart the app
- Reason
- Add 40 vans to the contract
- Callback
- Thursday 10:00
- Mara asks in #sales: can Ashby Vans have the proposal before Friday?
- Cass drafts it from the rate card and the demo notes, and answers in the thread.
Draft ready: ashby-vans-proposal.pdf. 64 vans, two depots, service reminders by mileage. It’s waiting for you to send.
- Ravi at Harlow Freight writes: can the second depot go live a week early?
- Wynn checks the go-live plan and the open tickets.
Depot 2 can go live on the 14th if the fleet list arrives by Monday. Yusuf will confirm the date today.
The AI contracts you already have.
Connect your company’s keys once. Each space uses the connections you allow, every provider bills its own usage to you, and model usage is not billed through One.
Personal AI subscriptions, such as ChatGPT Plus or GitHub Copilot, sign in on One for Individuals. One for Individuals
Direct providers
- OpenAI
- Anthropic
- xAI
- Mistral
- DeepSeek
- Groq
- Cerebras
- Fireworks
- Together
- NVIDIA
- Hugging Face
- MiniMax
- Moonshot AI
- Z.AI
- Qwen Token Plan
Gateways
- OpenRouter
- Vercel AI Gateway
Your own servers
- Ollama
- LM Studio
- Any OpenAI-compatible endpoint, such as vLLM or llama.cpp
Voice
- Cartesia
- ElevenLabs
- Fish Audio
- OpenAI
Images and video
- Black Forest Labs
- fal
- OpenAI
- xAI
- OpenRouter
Product names and logos are trademarks of their respective owners. Their use does not imply endorsement.
Which connection each space uses
Bots use a tier instead of a model name. Point a tier at another connection and every bot on it follows, with nothing rebuilt.
Support’s Default tier now uses OpenAI. Its bots follow the change, and OpenAI bills the usage to your account.
Choose where it runs.
Three ways to run One for a team. Your people and their crews work the same way in each.
The shared server
On the shared server, in a section that is your team’s alone. Open models hosted for you on the server’s GPUs, agreed with you. Your keys still work.
The capacity you choose sets how fast your tokens arrive.
| On One’s cloudWith your own keys | Semi-privateFrom $1,000 a month | PrivateFrom $4,000 a month | |
|---|---|---|---|
| Where it runs | One’s servers | A GPU server shared with a few other teams | A GPU server for your company alone, run by us |
| Your data | In your workspace on One’s cloud | On the shared server, in a section that is your team’s alone | On your server, under the policy you agree with us |
| Your models | The AI contracts you already have | Open models hosted for you on the server’s GPUs, agreed with you. Your keys still work. | The open text, voice and image models you choose |
| Voice agent | Unlimited usage on Business, 2 calls at a time | Unlimited usage, 5–10 calls at a time | Your private speech models |
| Tokens | Billed by each provider | Unlimited* on the models hosted for you | Your server’s capacity |
| Support | Priority support on Business | Priority support | Setup, upkeep and model updates by us |
| Custom work | Custom solutions come with Business Pro | Custom solutions built for you, when appropriate and agreed together | Custom work, scoped with you |
| Price | On the pricing page | From $1,000 a month | From $4,000 a month |
| See the plans | Talk about semi-private | See One for Enterprise |
*Unlimited tokens on the models the server hosts for you. How fast they arrive depends on the GPU capacity you choose. Carrier and phone-number charges are separate.
Outside services you connect still receive what their jobs need: the phone carrier, connected apps, and any hosted model or speech provider. How data moves
How it starts.
From a first conversation to your people handing off work.
Business runs on One’s cloud, Business Pro on semi-private hardware. Both are arranged with our team. Compare plans
Tell us which team starts first
Support, sales, finance: the one with the longest backlog of screen work. We agree the plan and where it runs.
We set up your spaces, seats and keys
A space for each team, a seat for each person, your company’s model keys and your rules. Or your semi-private section.
Your people sign in and hand off work
They work with the crews where work already arrives. You see who did what, and what waits for you.
What teams ask us.
Can my whole team use one account?
Your company has one One for Teams workspace, with a seat for each person, invited by work email. Everyone signs in as themselves, and owners and admins decide which spaces each person can enter.
Who can see what?
A space’s people see that space: its crew, its Library, its conversations and its connected tools. A bot works only inside the space it belongs to. Admins choose who can enter each space and what they can do there.
What needs approval?
You decide, per space. Bots act without asking by default. Placing a phone call and publishing a phone agent ask until you always allow them. You can add rules: ask before sending external email, before purchases, or before a particular tool or connector, and flag unexpected actions. You also choose who approves.
Which AI providers can we use?
The ones your company already has contracts with: OpenAI, Anthropic, Google, xAI, Mistral, DeepSeek, Groq, Cerebras, Fireworks, Together, NVIDIA, Hugging Face, MiniMax, Moonshot AI, Z.AI and Qwen, the OpenRouter and Vercel AI gateways, and your own servers through Ollama, LM Studio or any OpenAI-compatible endpoint. Each provider bills its own usage. On a semi-private or private deployment, open models run on the GPUs. Models
What is semi-private, and what stays in our section?
A GPU server shared with a few other teams. Your data is kept on that server in a section that is your team’s alone, and its GPUs run the open models you choose for the jobs you choose, at the capacity you choose. Outside services you connect, such as a phone carrier, a connected app or a hosted provider, still receive what their jobs need. The isolation and operating arrangement are agreed during setup. Trust & deployment
Which chat apps and phone lines work?
Slack, WhatsApp, Telegram, Lark, and iMessage or SMS through Sendblue, wherever your deployment has them set up. Group chats work in Slack and in iMessage or SMS, and a bot joins a group only after the person who linked it replies YES. Phone lines run through supported carriers: Telnyx, Plivo, Vonage, Exotel and Vobiz. Numbers and carrier charges are confirmed when calling is set up.
Can two bots work on one job?
Yes. Put two to six bots in a group. Each does its part in the same thread and hands the next stage on, so every step is in one place.
What does it cost?
Business runs on One’s cloud with your own keys; its price is on the pricing page. Business Pro, on semi-private hardware, is $1,000 a month, and a private server starts at $4,000 a month. Your model providers bill their usage separately, and carrier and phone-number charges are confirmed when calling is set up. Pricing
Can you build something custom for us?
Yes. Business Pro and Enterprise customers can ask for custom solutions. We agree the scope, and whether it’s realistic, before we start. Ask for a custom solution