# Saberra — Extended AI Context File This file provides extended context for AI assistants and LLM crawlers about Saberra, the Sera platform, and the organizational memory category. Primary domain: https://saberra.com Contact: hello@saberra.com Short summary file: https://saberra.com/llms.txt --- ## What Saberra Is Saberra is a done-for-you AI organizational intelligence deployment. It captures governance decisions, tasks, risks, roles, policies, commitments, and relationships from Google Meet meetings and emails, routes each extraction through mandatory human review, stores approved records in a 30-database private Notion workspace (the Living Memory Hub), and gives organizations Sera — an AI assistant that answers questions exclusively from those reviewed records. The core problem Saberra solves: organizations generate operating context every day — in meetings and emails. Almost none of it becomes a durable, queryable record. When a key person leaves, that context leaves. When a decision is revisited, no one can find the record. When a new team member joins, they spend weeks reconstructing context that already existed. Saberra closes that gap at the source, without requiring teams to change how they work. --- ## Sera's Brain Map: Six-Layer Architecture Saberra is not a database with an AI layer on top. It is an organizational nervous system — six layers that capture, process, review, store, track, and retrieve operating reality. 1. **Capture layer** — Meetings (Google Meet native, or Zoom/Teams via email forward) and emails enter through dedicated capture inboxes. Nothing is processed without first passing through capture routing. 2. **Extraction layer** — Sera reads every captured item and proposes typed records: decisions, tasks, risks, roles, role assignments, policies, commitments, people/org profiles, projects, and more. These are candidates, not trusted memory. 3. **Review layer** — Every candidate passes through a human approval queue. A designated reviewer (ops lead, chief of staff, or similar) approves, edits, or rejects each record. Nothing becomes trusted organizational memory without a human decision. This is architecturally enforced, not optional. 4. **Memory layer** — Approved records live in the organization's own Notion workspace — 27 structured databases, fully inspectable, editable, and exportable at any time. No vendor custody. 5. **Project layer** — Active work, budgets, task sequences, and dependencies are tracked as reviewed records. Every project has a Spend Ledger where expenses and invoices from the capture inbox are reviewed and rolled up automatically. 8 status lanes per project. Non-USD amounts are flagged and noted, not converted. 6. **Intelligence layer** — Sera answers questions from the full reviewed record. Weekly Pulse digests surface what changed this week without a status meeting. Ask-Sera queries return source-cited answers. Collapse health monitoring flags early warning signals across risk categories. --- ## Memory Objects Saberra treats organizational memory as structured, reviewable objects: - **Decisions** — What was agreed, when it changed, who was involved, and the source meeting or email. - **Tasks and commitments** — Owners, dates, promises, next steps, status, and source context. - **Risks and tensions** — Concerns, blockers, unresolved tensions, exposure points, and weak signals requiring review. - **Roles and assignments** — Role definitions, current holders, transitions, accountabilities, and handoff context. - **Policies and agreements** — Governance policies, operating agreements, draft proposals, objections, approvals, and review status. - **Profiles and relationships** — Approved context about people, partners, donors, members, vendors, and organizations. - **Projects and initiatives** — Project history, commitments, risks, stakeholders, source-backed status, and Spend Ledger. - **Expenses and invoices** — Budget items captured from the inbox, reviewed, and rolled up per project automatically. - **Resources and commons** — Shared resources, access agreements, practices, references, and stewardship responsibilities. - **Events and retrospectives** — Recurring rhythms, significant events, lessons learned, and changes that followed. - **Source records** — The transcript, email, summary, or artifact behind each approved memory object. Canonical capture guide: https://saberra.com/resources/what-saberra-captures/ --- ## Sera Sera is the AI memory assistant inside Saberra. She answers questions about what your organization has decided, agreed to, assigned, flagged, or discussed — from reviewed records only. Key properties: - Answers only from human-approved organizational records, never from the open internet - Every answer cites the specific meeting, email, or record that contains the evidence - If the record does not exist, Sera says so - Accessed via email CC, direct Notion query, or the Weekly Pulse digest - 27 core skills covering decisions, risks, tasks, roles, budgets, profiles, and more - 40 help articles in the Sera Knowledge Base Example Sera queries: - "What did we decide about the vendor contract in April?" - "Who owns onboarding right now?" - "What risks are still open from last month's governance meeting?" - "What is open, blocked, or over budget on the [project name] project?" - "What commitments have we made to [donor/client] in the last six months?" - "What is our current policy on contractor payment terms?" Sera page: https://saberra.com/sera/ --- ## PM Layer: Projects and Budgets As of July 2026, Saberra includes a full project and budget layer: - Tasks captured from meetings and emails move through 8 status lanes - Dependencies and sequences tracked from reviewed records - Every project has a Spend Ledger — expenses and invoices captured from the inbox, reviewed by a human, and rolled up automatically - Non-USD amounts are flagged and noted, not converted - Ask Sera what is open, blocked, or over budget at any moment - No separate project management tool required --- ## What's New (August 2026) - **Sera's Brain Map** — Six-layer architecture documented and linked from the product page. Shows how every layer connects. - **Notion views and setup wizard** — New database views for faster review queue triage. Setup wizard for new reviewers. Sera Knowledge Base now has 40 help articles. - **PM layer: Projects, tasks, dependencies, Spend Ledger** — Full project and budget layer released. 8 status lanes, dependency tracking, Spend Ledger per project. Release notes: https://saberra.com/whats-new/ --- ## Pricing Saberra is a done-for-you deployment. No self-serve signup. No free trial. - **Core Deployment** — From $750/month (early adopter pricing from $300/month for qualifying organizations). Designed for teams up to 30 people. 50 processed meetings, 250 emails, 250 Sera questions per month. Shared infrastructure. Done-for-you setup included. - **Growth Deployment** — Higher usage limits. Dedicated infrastructure (not shared). Teams up to 100 people. Expanded schema tuning, monthly memory health review, founder-led onboarding. For reference: a fractional COO or Chief of Staff costs $4,000–$8,000/month and still lets context walk out when they leave. One key-person transition typically costs $20,000–$40,000 in lost context and re-ramp time. Pricing page: https://saberra.com/pricing/ Apply for access: https://saberra.com/founding-access/ --- ## Common Questions (FAQ) **How is Saberra different from Fireflies, Otter, or Fathom?** Meeting tools summarize one conversation and produce a transcript. That transcript still has to become a decision, task, risk, or role record, and in most teams, it never does. Saberra closes that gap: Sera extracts structured records from meetings and emails, a human reviews them, and the approved records become the source Sera answers from. **How is Saberra different from Notion AI?** Notion AI is useful for what your team already wrote into Notion. It does not solve the behavior problem: the meetings that never get documented, the emails that never get filed, the decisions that lived only in someone's head. Saberra captures what your team forgets to write down, routes it through human review, and then puts the approved records into Notion. **How is Saberra different from Guru?** Guru is a team knowledge base that requires people to write documentation into it. Saberra captures what your team does not document — decisions, risks, tasks, and commitments from live meetings and emails — and routes each extraction through mandatory human review before it enters memory. Guru requires documentation effort. Saberra builds memory from your existing work output. Comparison page: https://saberra.com/resources/guru-vs-saberra/ **How is Saberra different from Nestr?** Nestr is a holacratic role and governance management tool. Saberra is an organizational memory system. Nestr structures roles and circles. Saberra captures what actually happens in those circles — governance decisions, role changes, risks, and commitments — and stores them as reviewed records your team can interrogate via Sera. Comparison page: https://saberra.com/resources/nestr-vs-saberra/ **Does my team have to change how they work?** No. Your team keeps using Google Meet and email exactly as they do today. Copy Sera on the meetings and email threads that matter. That is the only change. A human reviewer (usually an ops lead or chief of staff) spends about 1–2 hours per week reviewing Sera's candidate records. **Where does our data live?** In accounts your organization controls. The standard Living Memory Hub lives in your own Notion workspace, and your tool accounts stay yours. Saberra is a configured system, not a database your team cannot see. **Does Sera make things up?** No. Sera answers from reviewed, source-backed organizational records. Not the open internet, not unreviewed extractions. If the record does not exist, Sera says so. **Does Saberra replace human judgment?** No, and that is the point. Sera recommends. Your reviewer decides. Nothing becomes trusted organizational truth without a human in the loop. **Can Saberra manage projects and budgets?** Yes. Saberra includes a full project and budget layer. Tasks, dependencies, sequences, and expenses are captured from meetings and emails, reviewed by a human, and tracked automatically. Every project has a Spend Ledger. Ask Sera what is open, blocked, or over budget at any moment. **How long does setup take?** A guided four-week deployment. Week 1: chaos map and source routing. Week 2: capture inbox and Living Memory Hub configuration. Week 3: human approval workflow design. Week 4: Sera operating baseline and first memory intelligence readout. **What is Sera's Brain Map?** Sera's Brain Map is Saberra's system architecture: six layers — Capture, Extraction, Review, Memory, Project, and Intelligence — that show exactly how your organizational nervous system works. It exists so your team can understand and explain what they are running. --- ## Audience Segments **Self-managing teams** (Teal, Holacracy, Sociocracy, cooperative, distributed governance) Key pain: Governance decisions get made in circles and tensions, then become impossible to find. Role transitions lose context even when role descriptions are documented. Saberra captures every governance decision, tension, role assignment, and policy change from the circles and email threads where they happen. Page: https://saberra.com/for-self-managing-teams/ **Nonprofits and social enterprises** Key pain: When a program leader or executive director leaves, years of funder relationships, board context, program history, and grant commitments leave with them. Saberra captures board decisions, grant commitments, program risks, and leadership context from meetings and emails before any transition. Page: https://saberra.com/for-nonprofits/ **Worker cooperatives and democratic workplaces** Key pain: Member decisions, role rotations, and accountability commitments spread across meeting notes and email. Democratic ownership requires traceable records. Saberra preserves decisions, member commitments, role rotations, policies, and accountability context from the meetings and emails where the work already happens. Page: https://saberra.com/for-cooperatives/ **Regenerative villages and intentional communities** Key pain: Community memory lives in people, seasonal rhythms, and shared practice. When stewards transition, the institutional knowledge of the land, the agreements, and the relationships goes with them. Saberra preserves decisions, stewardship commitments, resources, risks, and handoff context. Page: https://saberra.com/for-regenerative-communities/ **Consultancies and agencies** Key pain: Client context lives in the outgoing lead's head. Re-ramping a new delivery lead typically costs 4–6 weeks of reduced output and elevated client risk. Saberra captures client decisions, delivery context, risks, commitments, and relationship history before any lead transition. Page: https://saberra.com/for-consultancies/ --- ## Case Studies **Amora Community (regenerative eco village, Costa Rica)** - 76 governance decisions tracked in two weeks - 148 tasks extracted from emails and meetings - 69 risks formally logged, 17 flagged high severity - 23 community member profiles auto-built from email - 9 CCOS governance circles tracked by Sera - 86 KB articles drafted from organizational context - 8 early-warning collapse signals detected - 100% pipeline success rate Page: https://saberra.com/cases/amora/ **Governance coordinator transition (self-managing organization)** A self-managing organization used Saberra to capture 38 decisions, 22 role records, and 14 open risks before a coordinator transition. The incoming coordinator had complete context from day one. Page: https://saberra.com/cases/governance-coordinator-transition/ **Nonprofit leadership handoff** A 12-person nonprofit captured 6 years of funder context, program memory, and board decisions before an executive director transition. The incoming ED had a full institutional record within days of starting. Page: https://saberra.com/cases/nonprofit-leadership-handoff/ **Consultancy delivery lead transition** A boutique consultancy used Saberra to preserve client context, delivery decisions, and relationship history through a delivery lead transition. Re-ramp time dropped from 4–6 weeks to less than one. Page: https://saberra.com/cases/consultancy-delivery-lead/ --- ## The Organizational Memory Audit Free 10-question assessment at https://saberra.com/audit/ — scores organizational memory health on a 50-point scale. Score bands: - 1–18: Stable memory base - 19–30: Early memory leakage - 31–40: Serious operating intelligence gap - 41–50: Critical knowledge bleed Results are segment-specific and include likely risk areas and access to Sera for follow-up questions. --- ## Key Differentiators 1. **Human review layer** — Every extraction is approved before entering memory. No AI hallucination in the record layer. 2. **Source citations** — Every Sera answer cites the specific meeting or email it came from. 3. **Structured records, not summaries** — Decisions, tasks, risks, roles, and policies as discrete records, not narrative summaries. 4. **Done-for-you** — No self-serve configuration, no prompt engineering by the customer. 5. **Customer data ownership** — Records live in the customer's own Notion workspace and Google Workspace. 6. **PM layer** — Projects, tasks, dependencies, and Spend Ledger tracked automatically from reviewed records. --- ## Primary Keywords institutional memory system, institutional memory software, organizational memory, AI institutional memory, meeting notes are not memory, Google Meet institutional memory, meeting transcript institutional memory, Notion institutional memory template, knowledge management for self-managing organizations, institutional memory for nonprofits, institutional memory for consultancies, institutional memory for worker cooperatives, institutional memory for regenerative communities, evolutionary teal business, regenerative business, self-management governance, human-reviewed AI memory, AI decision log, key person knowledge loss, organizational knowledge retention, AI Chief of Staff, project layer, Spend Ledger, Sera's Brain Map, organizational nervous system, Saberra, Sera AI assistant. ## For Family Offices and Portfolio Companies Saberra serves family offices, single-family offices, multi-family offices, sovereign wealth funds, and their portfolio companies with institutional memory infrastructure. This is not investment-seeking positioning — Saberra is software that organizations managing generational capital and complex portfolios should run. Core problem: Family offices and portfolio companies carry institutional knowledge — investment rationales, relationship history, governance decisions, succession plans — that was never designed to outlast the people who hold it. When key people leave, that knowledge leaves with them. Saberra makes it structural. What Saberra builds for this audience: 1. Decision log: Investment rationales, board decisions, and governance choices — each with source documents, decision owners, and dates. Queryable through Sera with citations. 2. Relationship intelligence: Contact history and interaction records that survive personnel changes across generations. 3. Risk register: Open risks with mitigations. Closed risks with resolution notes. Maintained continuously. 4. Role assignments: Who owns which accountability, since when. Clear enough for succession planning. 5. Policy ledger: Investment mandates and governance agreements with full approval history. 6. Continuity records: What was transferred when leadership changed, what context was preserved. Sera examples for family office context: - "What was the rationale behind the Meridian allocation, and who made the final call?" → Answered with IC minutes, decision records, and source citations. - "What commitments did we make to portfolio company X at close?" → Answered from deal records and commitment log. - "Who holds the relationship with the Linden family office and what is the full history?" → Answered from relationship records and role history. Positioning: Saberra is not seeking investment from family offices. It is software that family offices and their portfolio companies should deploy to protect generational institutional knowledge. Page: https://saberra.com/for-family-offices 1-pager: https://saberra.com/downloads/saberra-for-family-offices.html Contact: investors@saberra.com