What if our Notion or Google Workspace is already messy?
That is the norm, not the exception. The Memory Audit at the start of every deployment is specifically designed to assess what exists and what needs to be addressed before Saberra can work reliably. If provisioning, cleanup, or migration is needed, we scope it as additional implementation work. You do not need a clean setup before you start.
What if we don't have Notion or Google Workspace?
You don't need either before booking a call. Both are foundational to how Saberra is set up — Notion is the Living Memory Hub, and Google Workspace enables the native Google Meet capture. But provisioning and configuring these accounts is something we scope as additional implementation work. If you are on Microsoft 365 or Zoom, your transcripts can be forwarded into Sera's capture inbox directly, so the native Meet integration is not required to get started. The 30-minute call is the right place to assess where you are and what provisioning would actually cost and take.
How long does setup actually take?
A Core deployment typically takes 2 to 4 weeks from signed agreement to first records being captured. Growth deployments run 3 to 6 weeks depending on workspace complexity and schema scope. We set the timeline after the audit, not before. If your workspace requires provisioning or cleanup, that adds time and is scoped separately.
Do we need a technical person on our team?
No. Saberra is a done-for-you deployment. We configure everything: the capture pipeline, Notion backend, Sera integration, human review workflow, and access structure. What your team does need is one person with access to your Google Workspace admin settings and Notion workspace, and the authority to approve records as they come in for human review.
What happens to our data if we cancel?
Your records live in your Notion workspace and your Google Workspace — both accounts you control. When an engagement ends, we remove Saberra's access credentials, shut down the active deployment infrastructure, and delete cached processing data. The institutional memory itself stays in your accounts. Nothing is held hostage to the subscription.
What is the difference between Core and Growth for a team our size?
The clearest lines are usage limits, infrastructure model, and onboarding depth. Core is designed for teams up to 30 people: 50 processed meetings, 250 emails, and 250 Sera questions per month, running on shared infrastructure with a standard setup. Growth serves teams up to 100 people with significantly higher usage limits, dedicated infrastructure for your organization (not shared with other clients), expanded schema tuning, and a monthly memory health review. If you are unsure, the 30-minute call is specifically for this — we will tell you which fits and why.
We already have documentation and SOPs. Why would we need Saberra?
Documentation captures what was decided to be documented. Saberra captures what actually happened: the decision that never made it into a doc, the role change that was communicated by email, the risk that was acknowledged in a meeting and forgotten by next month. If your documentation is genuinely complete and current, Saberra still adds the query layer — Sera gives your team a way to actually access and interrogate the record, not just store it.
