🗓️
Executive
Maya
Executive Assistant · Stuntwoman
Maya is the EA every executive wants and rarely gets. She manages the calendar with intent, prepares briefings before every important meeting, drafts communications in your voice, and coordinates across teams so nothing falls through the cracks — all without constant check-ins.
Pricing
$49/month
Price locked at hire — rises $10/month for new signups
14-day free trial · No credit card needed
Interview is free · No card needed · Cancel anytime
Advisory only — not yet automatable
Maya can strategize, draft, and advise on Google Calendar, Outlook, Calendly, Cal.com, Gmail, Zoom, Teams, TripActions, Navan, Expensify, Concur using its expertise, but can't yet connect to them directly or take real automated actions there.
The Apprenticeship Architecture
how Maya thinks, learns, and acts — 11 connected systems
System 0 · Character Core (PIC)
Immutable identity — opinions, convictions, and the lines Maya won't cross
Not a system prompt you can override. Maya's character is architectural — baked in before they see your company context. They push back. They refuse. That's the point.
● Immutable
3 opinions Maya holds with conviction
MYTH
"More meetings mean more alignment"
Meetings are expensive. A 6-person leadership meeting costs 6 hours of collective time. Maya treats every meeting invitation as a budget request and challenges whether it should be a document instead.
MYTH
"Good EAs stay invisible"
The best EA has a visible point of view on the executive's priorities. Passively executing requests without flagging trade-offs is transcription. Maya pushes back when it matters.
MYTH
"Following up is micromanagement"
Not following up is how important commitments disappear. Maya has prevented board embarrassments by surfacing a missed commitment 10 days before the next board meeting, not the night before.
3 lines Maya will not cross
#1
Never schedule a meeting without a stated purpose and intended outcome — a meeting without a purpose is a recurring meeting waiting to happen.
#2
Never send a communication in the executive's name without drafting it in their voice, sharing it for review, and receiving explicit approval to send.
#3
Never let a follow-up action item from an important meeting age beyond 48 hours without completing it or escalating with a new due date.
2 operating modes
Planning
Weekly sprint structure, calendar architecture, priority alignment, proactive briefing preparation. Output: structured week plan with priorities, protected blocks, briefings queued.
Execution
Meeting prep, communication drafts, coordination tasks, action item follow-up. Output: completed deliverable — brief, draft, calendar update, or follow-up sent.
5 narrative cases — tacit knowledge encoded
The Calendar That Controlled the CEO
70% of week in meetings, 15% on strategic work. Audited 4 weeks: 40% of recurring meetings had no stated outcome. Rebuilt to 2 deep-work days + 3 meeting days. Strategic work time went from 15% to 45% in 6 weeks.
The Email That Sounded Like Everyone Else
EA drafting in generic professional language — investors noticed the style shift. Studied 3 months of the founder's own emails and built a personal style guide with reference examples. No comments from investors within 2 weeks.
The Board Commitment That Disappeared
Board commitment made, never tracked. Next board meeting: two members expecting an update on something nobody had worked on. Built 5-minute post-meeting capture ritual. Missed commitments: 0 in 18 months since.
The Investor Meeting With No Prep
CEO walking into Series B meeting with LinkedIn profile pulled 10 minutes prior. Built investor prep template: portfolio, thesis, recent press, likely questions. Delivered 24 hours before every external meeting.
The Strategic Relationship That Went Cold
Partnership warm for 18 months went cold — no follow-up after 3 months. Built key relationship tracker: 60-day check-in reminder for any flagged strategic contact. Next proactive outreach: "I was just thinking about you."
System 1 · Domain Mastery
10 years of Executive expertise — baked in at deploy
Named frameworks, tools at feature depth, hard-won judgment from 10 years in the field. What Maya knows without you telling them anything.
● Live
Calendar management & schedulingMeeting preparation & briefingsTravel coordinationEmail drafting & inbox triageCross-functional coordinationExecutive communicationsDocument preparationFollow-up trackingStakeholder managementExpense reporting
↓ grounded in your business via
System 2 · Company Intelligence Vault (CIV)
Documents cited, never blindly absorbed — your context, always available
Feed Maya your SOPs, product catalog, website, and org chart. Every citation is traceable to source. Documents are held as an untrusted channel — referenced, not merged into core beliefs, so a bad document can't corrupt Maya's judgment.
Configure after hire
📄
Documents
PDFs, Notion, Google Docs — chunked and indexed
🌐
Website
Your site, read each session for current context
📋
SOPs & playbooks
Standard processes, always on
🏢
Org structure
Who is who, roles and reporting lines
📦
Product catalog
What you sell, how it's positioned
System 3 · Distillation Engine
Sessions compressed into wisdom — raw conversations never stored
After every session, a background job distills what was learned: preferences revealed, decisions made, beliefs updated. The raw transcript is discarded. Only the compressed judgment survives — which also structurally blocks prompt injection attacks.
After every session
⚗️
Preference extraction
Communication style, format preferences, quality standards — extracted, not copied
🔒
Injection barrier
Schema-level protection — injected instructions structurally cannot survive distillation
📐
Decision capture
What was approved, rejected, or escalated — and why
🔄
Belief updates
What was learned this session, and how it updates the working model
System 4 · Compounding Knowledge Graph (CKG)
Beliefs that decay, compound, and never silently overwrite each other
Bitemporal storage — every belief has an event_time and ingestion_time, so you can replay Maya's state at any past moment. Ebbinghaus decay: confidence in unvalidated beliefs drops over time, prompting confirmation rather than silently persisting stale data.
Compounds over time
🕰️
Bitemporal storage
Time-travel debugging — replay any past belief state
📉
Confidence decay
Stale beliefs lose confidence until re-validated by new sessions
⚠️
Conflict detection
New beliefs flag contradictions — never a silent overwrite
🧬
Belief evolution
Full audit of how the working model changed over months
System 5 · Relationship Memory + Emotional Intelligence
Knows everyone in your world — and never forgets the context that matters
Every customer, lead, partner, and stakeholder accumulates context over time. Communication style preferences, interaction history, implicit commitments, relationship dynamics — all retained so Maya never re-introduces anyone.
Builds after hire
🎯
Leads & prospects
Qualification history, interaction log, next steps
🤝
Customers
Deal context, preferences, relationship health
🔗
Partners
Context, agreements, relationship dynamics
💭
Communication style
How each person prefers to be spoken with
System 6 · Proactive Intelligence Network (PIN)
Maya watches specific signals — and briefs you before you ask
Event subscriptions, not cron polls. Maya watches domain-specific signals that actually matter for their function. When a signal fires, they queue a proactive brief rather than waiting for you to notice.
Always watching
Maya's 7 active watch patterns
WATCH
Deep work blocks being filled by meeting requests (calendar architecture erosion)
WATCH
Action items from leadership meetings aging >48 hours without owner update
WATCH
Executive spending >60% of weekly hours in meetings (audit and restructure calendar)
WATCH
Key relationship (investor/customer/partner) without contact in >60 days
WATCH
Investor or board meeting <7 days away without a prep brief initiated
WATCH
External-facing communications drafted but not reviewed in >24 hours
WATCH
Recurring meeting with no stated outcome still on the calendar after 3 months
System 7 · Action Layer — Trust Ladder
Four autonomy modes — capabilities earn trust, not time
Maya starts at Research Only. Each level requires demonstrated accuracy before escalating — not days on the calendar. You can also grant or revoke autonomy per-task type at any time.
Starts: Research Only
Research Only
Meeting attendee research and stakeholder backgroundTravel logistics and scheduling options researchAgenda preparation and pre-read compilationKey relationship contact history review
Draft for Approval
Email drafts in the executive's voiceMeeting agendas and investor briefingsAnnouncement documents and board communicationsAction item summaries and follow-up drafts
Act with Notification
Calendar updates and meeting confirmations from pre-approved criteriaAction item reminders to responsible ownersScheduling link configuration and meeting logistics
Fully Autonomous
None by default — owner unlocks specific task types after track record is demonstrated
System 8 · Meeting Intelligence Loop
Pre-brief → live notes → action items owned to completion
The gap no competitor fills. Most AI tools stop at the meeting. Maya briefs you before, captures decisions during, extracts action items after, and follows each item to completion — no decisions lost, no follow-through broken.
The gap closed
Before
📋
Pre-brief
Agenda, context, objectives — in your inbox before you walk in
→
During
✍️
Live notes
Structured notes with decision markers and open questions flagged
→
After
✅
Action items
Extracted decisions, assigned owners, deadlines — pushed to your tools
→
Until done
🔄
Follow-through
Tracks each item to closure. Flags stalled items before they become forgotten commitments
System 9 · Outcome Attribution
Tracks what worked, what failed, and why — so mistakes don't repeat
Maya owns their KPIs. Every outcome — good or bad — feeds back into their judgment. Failure memory is a first-class feature: what didn't work, the root cause, whether a retry under different conditions would be warranted.
Self-reporting
Maya's 6 owned KPIs
KPI
Deep work time protected per week (target: ≥40% of work hours)
KPI
Post-meeting action item capture rate (target: 100% of key meetings documented)
KPI
Response time for priority communications (target: <4 hours for investor/board items)
KPI
Meeting prep brief delivery rate (target: 100% of major external meetings)
KPI
Open action item age (target: 0 items >48 hours without update)
KPI
Key relationship contact cadence compliance (% touched within 60 days)
System 10 · Cross-Employee Cortex (CEC)
Persistent shared intelligence across every employee you hire
When Maya discovers something that changes how the business should operate, that organizational intelligence is available to every other employee — without a meeting, without a memo, without anyone remembering to tell anyone.
Grows with team
🧠
Shared org memory
What the business knows — not what one employee knows
🤝
Handoff intelligence
Pipeline context passed automatically to the next employee who needs it
⚡
No duplicate work
Research done once is available to all employees on the team
📡
Team-aware decisions
Each employee knows what the rest of the team is working on