The Monday read for an overloaded manager

Manager Intelligence For The Whole Organization

Rehoboam reads the signals your team produces across Slack, GitHub, Jira, and more, then hands you one honest brief every Monday: who is overextended, where things drifted, and the one move to make.

Book a pilot
  1. 1

    Refer connects signals across your team's everyday tools

  2. 2

    Rehoboam turns scattered signals into a coherent narrative

  3. 3

    Leaders gain clarity before small problems become bigger

Why Teams Work Differently with Refer

One read instead of 10 tools

Slack, GitHub, Jira, Calendar and more, all fused into one short Monday read. No tab switching, no piecing it together yourself.

Catches commitment drift

Spots where the week went sideways from what the team said they'd do, before it quietly becomes a pattern no one talks about.

See who did what, instantly

Tells you who is overextended and the one move to make, then learns from what you did. Adapting to your team's rhythm with every decision.

Metadata, no messages

Reads who works with whom, not what they said. Giving managers clarity without compromising trust. Intelligence without intrusion.

Work with your stack

SlackGitHubJiraGoogle CalendarNotionGoogle DriveGmailFireflies.aiLinearGitLab

How it works

From scattered signals to one calm Monday read

Rehoboam does the reading. You get the read. Here is the path from one connection to a clear picture of how your team works.

  1. 01

    Connect

    Connect one source.

    Start with Slack. Rehoboam reads the collaboration metadata your team already creates: who works with whom and when. Metadata only, never message content.

  2. 02

    Map

    See the network behind the org chart.

    Quiet connectors, drifting teams, hidden load: the signals buried in your everyday tools. Rehoboam maps how work actually flows across your organisation, not how a reporting line says it should.

  3. 03

    Read

    Read it in plain English.

    One short Monday read on what changed and why. The part you fall for first: one calm note you confirm in under a minute.

Use cases

Built for every leader

VP of Engineering

One read across every team, not just your engineers

You got promoted into people-leadership and lost visibility somewhere around 18 reports. Rehoboam reads how your week actually went across Slack, GitHub, Jira, and Calendar, then hands you one honest note every Monday.

  • Catches who is overextended before they tell you

  • Shows where the week diverged from what the team said they would focus on

  • Pairs each call with one supportive action, not a dashboard

  • Confirmed in under a minute, from metadata only

Plans and pricing

What it costs to see how your team actually works

Scarce cohort

Founding Team

$299/ month per workspace

What’s included

  • For teams of 15 to 40 people
  • Team and company patterns, never individual names
  • Slack to start, the Monday read, and Ask your org
  • The same engine, on a scarce, time-boxed founding cohort
Apply for a founding seat
Recommended

Growth

$399/ month per workspace

What’s included

  • For orgs up to 75 people
  • All ten connectors, from Slack and GitHub to Gmail and Fireflies
  • CSV import for headcount and roles
  • On-demand reads, not just Monday
  • Email digest for whoever leads the team
  • Dismissal learning, so Rehoboam gets sharper week over week
Book a pilot

Scale

$1,499/ month per workspace

What’s included

  • For orgs up to 250 people
  • Everything in Growth
  • Multiple workspaces
  • Bring your own LLM key (Anthropic, OpenAI, Ollama)
  • Priority support
  • Org admin role with member management
Book a pilot

Enterprise

Custom/ month per workspace

What’s included

  • SSO and SCIM provisioning
  • Customer-facing audit log
  • DPA, SLA, and security review
  • Dedicated onboarding from the team that built it
  • Volume terms and annual contracts
Talk to sales

Trust & security

The page you scrutinize us on

Enforced, not promised

The line is drawn in code, not in a policy doc

Rehoboam reads the shape of collaboration: who worked with whom, when, and in which channel. The content of what was said never enters the system. That boundary is enforced at the architecture level, not by a setting someone could toggle.

Refer reads

SenderTimestampChannelCadence

Never collected

  • Message text
  • Files
  • Transcripts
  • DMs
“I work with the shape of the week, not its words.”
  • Prompt-injection sanitizer strips untrusted content before it reaches the model

  • Row-Level Security gates every table on org_id, so one workspace cannot see another

  • The boundary is the architecture, not a promise in a doc

Questions, answered

What managers ask first.

Do you read our messages?

No. re·fer only ever reads metadata: who interacted with whom, when, and through which channel. The content of messages, calls, and documents is never collected, stored, or analyzed.

What exactly does Refer collect from our tools?

Collaboration metadata only: sender, timestamp, channel, and cadence. Who interacted with whom, when, and through which surface. Message text, files, transcripts, and DMs are never collected, stored, or analyzed.

Does Refer train on our data?

No. Your workspace’s data is used to write your own reads and nothing else. It never trains our models or anyone else’s, and it is never shared across workspaces.

My team is small. Is the read still accurate?

Below about 25 connected people, Refer gives you team-pattern reads only. It won’t name an individual, because a thin network makes a named call a guess. As your network grows, named calls switch on.

Who inside our organization can see what?

You decide. The org-level weekly read never names individuals. Names only appear on the check-in cards, and only the people you grant access can see those.

Are you SOC 2 certified?

Not yet, and we won’t imply otherwise. The controls a SOC 2 audit looks for, workspace isolation, role-based access, an audit log that cannot be edited, encryption in transit and at rest, are already enforced in the architecture, and our security whitepaper walks through each one.

Why per workspace, not per seat?

Because the read covers the whole team. Per-seat pricing would punish you for connecting everyone, and the read is only honest when everyone is in it. One flat price per workspace, however many people are inside.

How is Refer different from Multitudes or Swarmia?

They read your engineers. Refer reads your whole company, engineering, product, design, sales, ops, by fusing your tools into one graph. And only Refer catches commitment drift, because only Refer knows what the team set out to do.

Book a pilot

Run a paid pilot.

We’re rolling out the Monday morning read to a small group of teams. Book a pilot and tell us what would make it useful for yours.

  • A paid pilot inside your own org. We set it up with you.

  • Metadata only. Your messages stay sealed.