Skip to content

For teams

Walk into the meeting
with the call already argued.

SynthBoard is built for the one person who carries the call — the lead, the manager, the operator. Experts argue it first, the dissent stays on the page, and you share the memo as a link anyone on the team can read without an account.

Free to start. No card.

Example. You write: “Thursday the leads decide whether support moves from a night shift to follow-the-sun with our Manila team. I want it argued before I walk in.” She proposes a board of three — The Operator · The Customer · The Empath — on “Night shift, or follow-the-sun with Manila?”, about 6–10 minutes, up to 135 credits. Nothing runs until you tap.

Examples

Before the meeting,
not after it.

The ask as a team lead would type it, how she read it, who sat, and what came back. Examples written for this page, not recorded runs.

Follow-the-sun support?

Work · Board of 3

Our support team is 14 people; three work a permanent night shift and two of them have asked to stop. The option: hand nights to our four-person Manila team. The leads decide Thursday.

Chief of staff

Worth a board — the coverage, your customers, and the people on nights. I’d seat The Operator, The Customer and The Empath.

  • The OperatorCOO
  • The CustomerUser Voice
  • The EmpathPeople Advocate

The board’s call

Move nights to Manila from January after a six-week overlap — and offer the three night agents day roles first.

Four people in Manila cover the night window with one on leave. The overlap is when the playbooks and the escalation rules get written down.

Confidence70 · Moderate

The Customer disagreed

“Your biggest accounts are in US time zones. The first bad handover will land on them.”

First step Ask the three night agents which day roles they’d takeMonday

Example · Board of 3 · up to 135 credits

Why would the launch fail?

Work · One expert

We launch the new onboarding flow on November 3. Assume it’s December and it failed. Why?

Chief of staff

The Skeptic runs this as a pre-mortem: the likeliest ways it fails, and the one to fix first.

  • The SkepticRisk Assessor

The call · The Skeptic

The likeliest failure: support isn’t trained on the new flow, so week-one tickets sit for days.

Three failure paths, ranked by how likely and how costly. The first has a cheap fix — a 30-minute walkthrough for support before launch day.

Example · One expert · up to 65 credits

The post to the team

Work · One expert

Write the Slack post announcing that nights move to Manila in January. Two night agents asked for this; one didn’t. Don’t make it sound like a cost cut.

Chief of staff

The Empath writes it: who hears first, and what the post says to each of them.

  • The EmpathPeople Advocate

The piece · The Empath

“From January, our Manila team covers nights. Before posting this, I spoke with each of the three people on nights…”

The post goes up after the three one-to-ones, names the six-week overlap, says what changes for day shifts, and ends with where to take questions.

Example · One expert · up to 65 credits

What she handles

One person argues it.
The whole team reads it.

The memo with the dissent on the page, the announcement written out, and the tools your team already writes in.

The call, how sure, who disagreed.

Confidence drops with dissent and is never above 90. The objection someone would only raise in a side thread is on the memo instead.

One link, the dissent on the page.

Share the board’s memo as a read-only page before the meeting. Anyone can read it without an account.

The announcement, written.

The post, the email, the notes for the one-to-ones — the whole piece, ready to edit. A Slack post is a preview you confirm before it goes anywhere.

Reads what the team already wrote.

Slack threads, Confluence pages, the Jira board. She says what she read, reads until you allow writing, and every write is a preview you confirm — on Pro and above.

The experts

The voices your meeting
never gets to hear.

The Devil’s Advocate argues the option the room already dropped, The Empath asks who has to carry the decision, The Skeptic runs the pre-mortem. Every board is built with someone whose job is to argue against the obvious answer.

Pick an expert

Hover, tap or tab throughSwipe, then tap one
  • GPT
  • Claude
  • Gemini
  • Grok

Seats are spread across model families: GPT, Claude, Gemini, Grok and more.

Questions

Fair questions.
Straight answers.

What team leads ask before they bring her the first call.

Or see pricing · every use case

Can my whole team use one account?

No. Each person signs up with their own account, their own thread and what they keep on file — there’s no shared team workspace. Share a board’s memo as a link; viewers need no account.

How do I show the team where people disagreed?

Every board’s memo keeps the dissent: who disagreed, why, and what would change the call. Its confidence drops when experts disagree and is never above 90.

Can it post to Slack for me?

Only after you confirm. She reads Slack when you connect it, and a post is a preview you confirm before it goes anywhere. Writes are on Pro and above.

Buying for a whole company?

Each person uses their own account today. For a company-wide conversation, the enterprise page says what’s available and how to reach us.

What does it cost?

Free to start — 150 credits every month + 250 to start. Talking to her is free within a daily allowance. A consult’s card says up to 65 credits and a three-seat board’s says up to 135 credits; nothing runs until you tap, and a board never bills above its card.

Bring Thursday’s call before Thursday.
Start free, with one message.

It waits in her box after you sign up. Nothing is sent until you press send.