Scope and roadmap
What Olga deliberately does not do in Phase 1, and what is deferred to later phases.
Phase 1
This page draws the line. It states what Olga does not do in Phase 1, how she handles a request that falls outside that line, and what is deferred to later phases.
Why Phase 1 is scoped narrowly
Phase 1 deliberately scopes Olga narrowly. The architecture supports much more; Phase 1 stops at what can be built, tested, and shipped responsibly.
The boundary is a feature, not a limitation. Everything inside it is grounded, confirmed, and verifiable. A narrow scope that always holds is worth more to a leadership team than a broad scope that sometimes guesses. Each later phase widens the line only as far as the next set of behaviors can be built to the same standard.
What Olga does not do in Phase 1
These are out of scope. Olga does not do them, and she does not pretend to.
- No pattern recognition across history. "Do we have recurring issues?" Olga can list issues but not identify patterns.
- No pre-meeting briefings with analytical synthesis. She can pull current data but does not generate analytical summaries.
- No capacity assessment. "Is this priority realistic?" requires historical velocity data; this is Phase 3.
- No cross-seat coordination beyond direct retrieval.
- No external calendar writing. Tasks appear in RunOlga's Task view; there is no Google Calendar or Outlook integration.
- No external system reads. No access to Anaya, QuickBooks, HubSpot, or any other system. This is Phase 2.
- No autonomous action. Every action requires user confirmation.
- No decisions on behalf of the user. She never commits the organization to anything.
- No clinical, legal, financial, or other licensed professional recommendations.
In Phase 1, Olga prepares, proposes, surfaces, and captures. She does not decide and she does not recommend. For the four things she does do, see Capabilities; for the guarantees behind them, see Trust and safety.
How Olga handles an out-of-scope ask
When asked for something out of scope, Olga acknowledges it honestly and offers the in-scope version of what the user is trying to accomplish. She does not refuse flatly, and she does not improvise a capability she does not have. She names the boundary and redirects to the nearest thing she can actually do.
You: Olga, do we have recurring issues with caregiver retention?
Olga: I can't look across history for patterns yet — that's on the roadmap. What I can do right now is pull every open issue tagged to retention so you can see them in one place. Want me to list them?
The honest "not yet," paired with a real next step, is the behavior. It keeps trust intact and still moves the user forward.
Roadmap
The items below are deferred to later phases. They are listed here so the boundary is unambiguous, not as commitments to dates. Each future phase will be specified in its own PRD as it approaches.
Phase 2 (deferred)
| Capability | What it unlocks |
|---|---|
| Pulse meeting briefings with analytical synthesis | Olga prepares the team for the pulse meeting with a synthesized read of current state, not just raw data. |
| Pattern recognition across accumulated history | Olga surfaces recurring themes across issues and other records over time. |
| Issue pre-work with context and proposed approaches | Olga assembles context for an issue and proposes approaches ahead of IDS. |
| Calendar integration (Google Calendar, Outlook) | Tasks flow to external calendars, not only the in-app Task view. |
| Cadence calculation for priority-driven tasks | Olga schedules the tasks behind a priority across its 90 days. |
| First external integrations (Anaya, QuickBooks, core HR) | Olga reads from the systems where operational data already lives. |
Phase 3 (further deferred)
| Capability | What it unlocks |
|---|---|
| Simple-to-Complex realism assessment | Olga assesses whether a priority is realistic, using accumulated velocity. |
| Priority sequencing across the quarter | Olga helps order priorities across the quarter. |
| Cross-seat coordination | Olga coordinates work across seats beyond direct retrieval. |
| Full pedagogical principles embodied | Graduated complexity and realistic scaffolding in how Olga teaches the operating model. |
| Chief-of-staff-level meeting support | Olga supports the pulse meeting at the depth a chief of staff would. |
Phase 4+ (commercial)
| Capability | What it unlocks |
|---|---|
| Multi-subscriber onboarding | Onboarding organizations beyond the first customer. |
| Public marketing site | A public-facing site for RunOlga. |
| Pricing and subscription | Commercial plans and billing. |
| Vertical Starter Configurations beyond Senior Care | Pre-built configurations for industries beyond the founding Senior Care vertical. |