How Tandem is useful, from features we actually have.
These are not logo case studies. Each one names the surfaces that already ship: projects, wiki, approvals, browser, costs, mesh, local models.
Eight clients. One project picker.
Projects · Wiki · Activity
FounderGoals and runway in the same view.
Goals · Costs · Approvals
EngineeringMany agents, one review loop.
Worktrees · Review · Approvals
SupportTickets next to the product file.
Inbox · Wiki · Approvals
SalesFollow-up that does not drop.
CRM · Enrich · Approvals
ResearchSources stay with the claim.
Safe-scrape · Wiki · Tasks
LegalPrivileged files stay on the box.
Local models · Approvals · Audit
FinanceNumbers next to the decision.
Costs · Dashboards · Approvals
CreatorOne week of content, one board.
Files · Tasks · Socials
OpsStandup is a board, not a meeting.
Tasks · Kanban · Digest
ITAccess and machines in one place.
Permissions · Hosts · Security
PeopleHiring notes stay with the role.
Projects · Wiki · Approvals
DevOpsPipelines next to the agents that break them.
Pipelines · Tasks · Review
DesignBrand files next to the page being built.
Files · Worktrees · Preview
SEOPages drafted where the site already lives.
Tasks · Files · Approvals
AdsPause waste without leaving the board.
Browser · Scheduled jobs · Approvals
CommunityDiscord and Slack land in one inbox.
Socials · Inbox · Wiki
DataA pipeline you can read.
Scheduled jobs · Files · Costs
SecurityReview before it leaves the vault.
Approvals · Audit · Security
SoloOne person, five channels.
Dashboard · Socials · Approvals
MeshWork splits across your machines.
Mesh · Hosts · Dashboard
Local AICloud when you want it. Local when you must.
BYO keys · Local models · Routing
On-callThe incident is a task, not a thread.
Tasks · Terminal · Wiki
EnterpriseWe build the first jobs with you.
Assessment · Projects · Audit
StudentA lab that does not evaporate.
Files · Tasks · Wiki
NonprofitVolunteers see the same board.
Projects · Tasks · Approvals
ProductSpec next to the agents building it.
Wiki · Tasks · Review
QAReplay what the agent did.
Activity · Sessions · Audit
SwitchBring the old stack in, then hide it.
Integrations · Modules · Switch
Autopilot BetaWork continues. You stay informed.
Scheduled jobs · Digest · Approvals
AutomationYour real Chrome, not a stealth browser.
Browser CDP · Safe-scrape · Skills
BuilderTurn a repeated job into a page.
Custom pages · Plugins · Skills
Finance / EngA token budget before the run.
Costs · Budgets · Tasks
Any modelOpenAI, Claude, Gemini, Grok, local — one project.
Model routing · Projects · Approvals
TeamThe next person does not start from zero.
Wiki · Tasks · Sessions
ServicesA client sees progress, not a chat dump.
Activity · Kanban · Approvals
ManagerWeekly review writes itself.
Activity · Wiki · Digest
On the goA walk becomes a task list.
Voice · Tasks · Approvals
DocsA page is a file agents can use.
OpenPages · Files · Review
DeliveryThe card is the conversation.
Kanban · Activity · Tasks
ExtendA skill is a file, not a store checkout.
Skills · Plugins · Vault
Power userMany terminals, one operator.
Terminal · tmux · Agents
HabitsThe goal does not reset each session.
Goals · Sessions · Tasks
PartnerA link, not another SaaS.
Affiliates · Terms · Billing
SwitchKeep the editor. Move the fleet.
Switch · Compare · Projects
We build itFirst jobs shipped with you in the room.
Assessment · Projects · Wiki
PrivacyLocalhost unless you choose otherwise.
Security · Local-first · Cloud optional
GlobalThe site speaks more than one language.
i18n · FAQ · App
BuyerA score before a call.
Scorecard · Compare · Assessment
Eight clients. One project picker.
Each client used to live across chat, docs, and a terminal. Switching ate the hour.
How they run it
- One Project per client.
- Wiki keeps last decisions.
- Activity is the billable log.
Surfaces used
Projects · Wiki · Activity
Goals and runway in the same view.
The board, the bank, and the agents were three tabs.
How they run it
- Goals sit next to spend.
- Exceptions come to you.
- The rest keeps moving.
Surfaces used
Goals · Costs · Approvals
Many agents, one review loop.
Agents shipped in separate chats with no shared evidence.
How they run it
- Worktrees isolate writes.
- Reviewer agents leave a trail.
- You approve the merge.
Surfaces used
Worktrees · Review · Approvals
Tickets next to the product file.
Replies were drafted without the last incident or the wiki.
How they run it
- Inbox lands in the same workspace.
- Docs are already attached.
- A human sends the reply.
Surfaces used
Inbox · Wiki · Approvals
Follow-up that does not drop.
The CRM and the outreach draft lived in different products.
How they run it
- Lead file sits next to the sequence.
- Enrichment is a job, not a paste.
- You approve anything outbound.
Surfaces used
CRM · Enrich · Approvals
Sources stay with the claim.
Notes, PDFs, and the model chat were three places.
How they run it
- Safe-scrape lands in raw/.
- Wiki compiles the brief.
- Citations stay on the page.
Surfaces used
Safe-scrape · Wiki · Tasks
Privileged files stay on the box.
Cloud AI was off the table. Local models had no operating layer.
How they run it
- Local models in the same project.
- Approvals on anything leaving the vault.
- Audit log for every action.
Surfaces used
Local models · Approvals · Audit
Numbers next to the decision.
Forecasts lived in a sheet. The work lived somewhere else.
How they run it
- Costs and budgets are a surface.
- The decision stays attached.
- You see spend before it surprises you.
Surfaces used
Costs · Dashboards · Approvals
One week of content, one board.
Transcripts, titles, and the calendar were four apps.
How they run it
- Transcript lands as a file.
- Tasks cover edit, title, schedule.
- Socials send after you approve.
Surfaces used
Files · Tasks · Socials
Standup is a board, not a meeting.
Status lived in people's heads.
How they run it
- Each job is a task with a state.
- Blocked work is visible.
- Morning digest names what needs you.
Surfaces used
Tasks · Kanban · Digest
Access and machines in one place.
Who can run what was a spreadsheet.
How they run it
- Agents get allowed tools and dirs.
- Hosts show where work runs.
- Nothing binds the public internet by default.
Surfaces used
Permissions · Hosts · Security
Hiring notes stay with the role.
Scorecards vanished into email.
How they run it
- Each role is a project.
- Notes land in the wiki.
- Outreach waits for approval.
Surfaces used
Projects · Wiki · Approvals
Pipelines next to the agents that break them.
CI lived in another tab from the chat that caused the fail.
How they run it
- Pipeline surface in the workspace.
- The failing job is a task.
- The fix is reviewed in the same place.
Surfaces used
Pipelines · Tasks · Review
Brand files next to the page being built.
Tokens, copy, and the preview were three tools.
How they run it
- Files stay in the project.
- The builder agent works in a worktree.
- You review the preview, not a zip.
Surfaces used
Files · Worktrees · Preview
Pages drafted where the site already lives.
Keyword notes never became a page with a review trail.
How they run it
- Research is a task.
- The page is a file.
- Publish waits for you.
Surfaces used
Tasks · Files · Approvals
Pause waste without leaving the board.
The ads manager and the budget chat were separate.
How they run it
- Browser works in your real login.
- A scheduled job watches ROAS.
- Pause still needs you if you want it to.
Surfaces used
Browser · Scheduled jobs · Approvals
Discord and Slack land in one inbox.
The same question arrived in three channels.
How they run it
- Socials connectors are in the box.
- Triage is a task.
- The answer can be reused from the wiki.
Surfaces used
Socials · Inbox · Wiki
A pipeline you can read.
The job ran in a black box.
How they run it
- The job is a scheduled task.
- Output lands as a file.
- Cost of the model run is visible.
Surfaces used
Scheduled jobs · Files · Costs
Review before it leaves the vault.
Agents could touch disk and the network with no gate.
How they run it
- Approval inbox on money, network, and deletes.
- Audit tables do not delete.
- Localhost by default.
Surfaces used
Approvals · Audit · Security
One person, five channels.
Newsletter, YouTube, socials, and clients were five logins.
How they run it
- One dashboard.
- Agents draft.
- You send.
Surfaces used
Dashboard · Socials · Approvals
Work splits across your machines.
One laptop could not run the fleet.
How they run it
- Peers share the load.
- Your boxes, your network.
- The board still looks like one place.
Surfaces used
Mesh · Hosts · Dashboard
Cloud when you want it. Local when you must.
Every request went out by default.
How they run it
- BYO keys.
- Local providers in the same project.
- You pick per job.
Surfaces used
BYO keys · Local models · Routing
The incident is a task, not a thread.
The page, the chat, and the fix lived apart.
How they run it
- Incident becomes a task.
- Browser and terminal stay in the project.
- The write-up lands in the wiki.
Surfaces used
Tasks · Terminal · Wiki
We build the first jobs with you.
Buying a workspace is not the same as getting work moving.
How they run it
- Assessment is the we-build-it door.
- The work still lands in your Tandem.
- You keep the files and the trail.
Surfaces used
Assessment · Projects · Audit
A lab that does not evaporate.
Chat history was the only memory.
How they run it
- Notes are files.
- The experiment is a task.
- The next session reads the last one.
Surfaces used
Files · Tasks · Wiki
Volunteers see the same board.
Handoffs died in email.
How they run it
- One project.
- Clear owners.
- Approvals on public posts.
Surfaces used
Projects · Tasks · Approvals
Spec next to the agents building it.
The spec was a doc. The build was a chat.
How they run it
- Spec is a wiki page.
- Tasks hang off it.
- Review happens in the same project.
Surfaces used
Wiki · Tasks · Review
Replay what the agent did.
A fail could not be reconstructed.
How they run it
- Activity log per task.
- Session linked.
- You can see the trail.
Surfaces used
Activity · Sessions · Audit
Bring the old stack in, then hide it.
A big-bang replace never starts.
How they run it
- Connect first.
- Replace one workflow.
- Hide unused modules.
Surfaces used
Integrations · Modules · Switch
Work continues. You stay informed.
Nothing moved unless you pushed every task.
How they run it
- Scheduled jobs run.
- Digest names what changed.
- Autopilot is Beta — money and public posts still stop.
Surfaces used
Scheduled jobs · Digest · Approvals
Your real Chrome, not a stealth browser.
Fake browsers failed the sites that matter.
How they run it
- CDP against your logged-in Chrome.
- Safe-scrape on the way in.
- Skills per site.
Surfaces used
Browser CDP · Safe-scrape · Skills
Turn a repeated job into a page.
The same prompt was pasted every Monday.
How they run it
- Describe the page.
- It becomes a surface.
- The agent uses it next week.
Surfaces used
Custom pages · Plugins · Skills
A token budget before the run.
The bill arrived after the fleet had already spent.
How they run it
- Per-task budgets.
- Cost preview.
- The job pauses when it hits the cap.
Surfaces used
Costs · Budgets · Tasks
OpenAI, Claude, Gemini, Grok, local — one project.
Each model was a different tab and a different memory.
How they run it
- Same files.
- Same tasks.
- Same review loop.
Surfaces used
Model routing · Projects · Approvals
The next person does not start from zero.
Context died when the first person closed the laptop.
How they run it
- Wiki between sessions.
- Task state is the truth.
- The next agent reads both.
Surfaces used
Wiki · Tasks · Sessions
A client sees progress, not a chat dump.
Status updates were screenshots.
How they run it
- Activity is exportable.
- The board is the status.
- You still approve what they see.
Surfaces used
Activity · Kanban · Approvals
Weekly review writes itself.
Friday status was a scramble.
How they run it
- Activity is the week.
- Wiki keeps the write-up.
- You edit, not invent.
Surfaces used
Activity · Wiki · Digest
A walk becomes a task list.
Voice notes died in the phone.
How they run it
- Voice lands as text.
- Tasks get owners.
- You approve anything that sends.
Surfaces used
Voice · Tasks · Approvals
A page is a file agents can use.
The site and the workspace were two worlds.
How they run it
- OpenPages is in the workspace.
- The agent edits a real file.
- You review the diff.
Surfaces used
OpenPages · Files · Review
The card is the conversation.
The board and the chat disagreed.
How they run it
- Kanban is a surface.
- The card has a trail.
- The next owner sees both.
Surfaces used
Kanban · Activity · Tasks
A skill is a file, not a store checkout.
Needed connectors lived behind a marketplace tax.
How they run it
- Skills live in the vault.
- Agents load them by site.
- You can write one.
Surfaces used
Skills · Plugins · Vault
Many terminals, one operator.
tmux and the chat were two brains.
How they run it
- Terminal grid is in the workspace.
- Agents share the same jobs.
- Closing the browser does not kill the shell.
Surfaces used
Terminal · tmux · Agents
The goal does not reset each session.
Every morning started from zero.
How they run it
- Goals persist.
- Streaks show up.
- Agents pick up the same thread.
Surfaces used
Goals · Sessions · Tasks
Keep the editor. Move the fleet.
The IDE was fine. The rest of the work was not.
How they run it
- Switch page names the move.
- Compare stays honest.
- The workspace takes the jobs the editor cannot.
Surfaces used
Switch · Compare · Projects
First jobs shipped with you in the room.
Buying seats did not start the work.
How they run it
- Assessment is the door.
- We sit with you.
- It still lands in your Tandem.
Surfaces used
Assessment · Projects · Wiki
Localhost unless you choose otherwise.
Every other tool started in someone else's cloud.
How they run it
- Services refuse 0.0.0.0.
- You pick cloud or local.
- Zero telemetry when you run local.
Surfaces used
Security · Local-first · Cloud optional
The site speaks more than one language.
The product was English-only in the nav.
How they run it
- EN, ES, FR, DE, JA stay.
- FAQ is the capability home.
- App login is still app.tandembase.xyz.
Surfaces used
i18n · FAQ · App
A score before a call.
Demos started before anyone knew if it fit.
How they run it
- Scorecard stays.
- Compare stays.
- Assessment is the human next step.
Surfaces used
Scorecard · Compare · Assessment