How it works
From sign-up to synced, in six steps.
Verybear sits between the tools your people already use and the AI providers behind them. Here's what setting it up actually looks like.
Sign up & connect
Create your org, add the first admin, and connect the tools your people already use. No migration, no new app to install.
Connect your tools
Each person connects once. No API keys to copy around.
- Claude Connected
- Pi Connected
- Codex Connected
- Cursor
- Paseo
$ verybear login
Open verybear.com/device and enter code BLUE-7FOX
Define flows
A flow is a task, named in plain language, with the model, effort, playbook and any helper agents that should run it. Write it once.
New flow
Task description
Model
Effort
Playbook
Subagents
Set guardrails
Approve the models you're comfortable with, give every team a budget, and block the request types that should never reach a model.
Approved models
Budgets per team
Blocked request types
- Customer PII export
- Payroll data
- Source code to unapproved vendor
- Legal advice to customers
Invite people
Add people by email, team and role, or turn on SSO and let your identity provider do it. No one is ever handed an API key.
Invite people
Add an email, pick a team and a role. That's it.
SSO (SAML / OIDC) provisions people automatically on Business and above. No API keys are ever handed out. People sign in with their existing accounts.
The user experience
One prompt. Two very different views.
People just ask for what they need. Admins see exactly how it was handled, including the requests nobody had a flow for yet.
What everyone sees
Their normal tool. A plain prompt. Nothing new to learn.
What the admin sees
Every request, with the flow, model and spend behind it.
Marcus Lee
Reconcile ledger to bank · Sonnet
$1Sofia Alvarez
Draft customer reply · GPT mini
$0Tom Okafor
Review pull request · Sonnet
$1Dev Patel
General assistance · GPT mini
Flagged$0Hannah Weiss
Campaign brief · Gemini
$2
Discovery & review loop
Every unhandled request and every pattern in the data becomes a proposal: a new flow to create, or an existing one to make cheaper or better. Approve it, and the change syncs to every connected desk.
Discovery inbox
7 to review- New flow
Summarize ticket for engineering
37 similar requests in the last 7 days hit the General assistance flow.
- New flow
Explain a Slack thread decision
19 requests asked to summarize a thread and extract the decision.
- New flow
Draft a job description
12 requests from Operations and Engineering.
- Optimization$390 / mo
Explain this codebase → move to Arch (local)
Quality signal unchanged in a 2-week shadow run; 98% of prompts answered from local context.
Synced to 148 desks
Who it's for
Everyone gets something different. Nobody gets left out.
CFO
- A spend number that matches the invoice
- Per-team budgets that actually hold
- Blocked request types, enforced everywhere
AI lead
- One place to define every flow
- New flows and savings proposed automatically
- Nothing to retrain, nothing to re-explain
Everyone
- The tools they already use, unchanged
- No model picker, no API key, no training
- The best way to do the task, by default