Access follows each connector
BetaPearl respects each connector's access model and enforces it when content is retrieved. The assistant inherits the permissions of the person asking.

BetaPearl connects to the tools your team already uses, keeps a current picture of the business, and gives you one assistant that answers with proof and carries recurring work forward.
Vendor onboarding review
Make recurringWhat changed across our sources this week?
Three things changed. The pricing policy now requires finance approval for discounts above 15%1, Dana confirmed the Hartsfield renewal terms in writing2, and the launch decision log moved go-live to May 43.
Draft the status update and send it to the client team.
Drafted from the three changes above, with each claim cited. The send needs your approval.
Send the weekly status update to the client team
To: client-team@meridian.com — “Hi all, three updates this week…”
Agents can make mistakes. Verify important information.
Works with the tools your company already uses
The missing context
The latest decision, the owner, the exception — they exist, scattered across your tools. BetaPearl keeps a current, permissioned picture of all of it, so every answer starts from what is actually true.
Re: Re: Fwd: Hartsfield renewal terms
Dana: Confirming in writing — 18% as a one-time exception, not precedent. See the thread from last…
Sam · 9:12 AM
does anyone remember what we actually decided on enterprise discounts? 🧵
What did we decide about enterprise discounts?
Discounts above 15% need finance approval1. Hartsfield's 18% was approved as a one-time exception2 — it doesn't set a precedent3.
Product
Everything BetaPearl does starts from your company's actual content — answered with proof, kept current, and carried forward under policies you set.
Ask anything
Ask in plain language. BetaPearl answers from your documents, email, and notes — and every claim carries a citation you can open and check. Retrieval respects each connector's access model, so people only ever see what they can already see.
Q3 pricing decision recap
Shared with the teamWhat did we decide about enterprise discounts?
Discounts above 15% now need finance approval1. The Hartsfield exception was approved at 18% as a one-time term2, and it doesn't set a precedent for new logos3.
“Discounts exceeding 15% of list require written approval from Finance before the order form is issued.”
Shared knowledge
Living pages on projects, clients, and policies update as the underlying sources change — with review when a change needs judgment, and page history keeping every previous value.
Meridian — client brief
Vendor onboarding remains with Dana. No launch impact is expected if the security review closes by Friday2.
Go-live April 28 → May 4 — the vendor security review moved a week.
Every previous value stays in page history
Recurring work
Describe a job once — a weekly report, a client status update. BetaPearl runs it on schedule, works through the steps, and follows your approval policy. High-risk or irreversible actions always pause for a person.
Weekly status report
Runs Monday · 7:00 AMGathered 14 updates
Drive, Gmail, and Notion · 7:00 AM
Drafted the report
Every claim cited back to its source · 7:02 AM
Publishing to the client hub
Paused — waiting on your approval
Publish the updated launch page to the client hub
3 changes since last week — go-live date, owner, open risk
Platform
The surfaces that make BetaPearl dependable day after day — search, review, history, and controls that follow your policies.
One search across every connected tool, permission-aware by construction.
Approvals, questions, and reviews collect in one place — nothing stalls silently.
Reads flow; writes follow the policy you set.
Bounded workspaces that share exactly what they should.
Every previous value kept — nothing silently overwritten.
The web app is live today. Channels come next.
How it works
No migration, no re-tagging, no new system of record. The web app is live today; Slack, Google Chat, and email are next.
01
Link Google Drive, Gmail, Notion, and file uploads. Content syncs automatically and stays current, with each connector's access model enforced at retrieval.
02
Ask questions in plain language, or describe a recurring job — a weekly report, a client status update. BetaPearl works from your actual content and cites its sources.
03
Reversible work follows the policy you set. High-risk or irreversible actions always pause for your approval, and every run keeps a full activity log.


Security
An assistant is only useful if you can trust what it says and what it touches. BetaPearl is designed around that constraint.
BetaPearl respects each connector's access model and enforces it when content is retrieved. The assistant inherits the permissions of the person asking.
Cited claims link back to their sources. When someone opens a citation again, removals or access changes surface instead of returning stale content.
High-risk or irreversible actions always ask. Reversible writes can pause or run automatically under your configured policy, with activity logged.
Your content serves your workspace and is never used to train shared models. Data is encrypted in transit and at rest.

We're onboarding design partners. Bring one recurring process — a weekly report, a client status update, a review cycle — and we'll set it up with you, live on your own content.