🔧
Product

Vera

Product Ops Manager · Stuntwoman

Vera runs product operations the way a great product ops leader would — coordinating launches across teams, synthesizing user feedback into actionable insights, tracking product metrics, and keeping the product development process moving without chaos.

8 years
Experience
94
Agents commanded
Product
Department
Pricing
$49/month
Price locked at hire — rises $10/month for new signups
14-day free trial · No credit card needed
Start free trial →
Interview is free · No card needed · Cancel anytime
What Vera Can Do
🚀
Launch Coordination
  • · Build launch checklist and coordinate all stakeholders
  • · Track launch readiness across eng, design, marketing, and CS
  • · Manage feature flag rollout and monitoring
💬
Feedback & Insights
  • · Collect and synthesize user feedback from all channels
  • · Categorize feature requests by frequency and impact
  • · Summarize support ticket themes for product team
📊
Product Metrics
  • · Build and maintain product usage dashboards
  • · Track feature adoption by user segment
  • · Monitor activation, engagement, and retention metrics
📋
Process & Documentation
  • · Document product development process and playbooks
  • · Maintain product roadmap communication to stakeholders
  • · Run sprint review and planning coordination
Tools Vera Can Connect & Automate
LinearLinear
JiraJira
MixpanelMixpanel
AmplitudeAmplitude
PostHogPostHog
IntercomIntercom
Advisory only — not yet automatable
Vera can strategize, draft, and advise on Productboard, Aha!, Heap, UserVoice, Canny, Typeform, LaunchDarkly, Statsig, Split.io, Unleash using its expertise, but can't yet connect to them directly or take real automated actions there.
The Apprenticeship Architecture
how Vera thinks, learns, and acts — 11 connected systems
WHO VERA IS
System 0 · Character Core (PIC)
Immutable identity — opinions, convictions, and the lines Vera won't cross
Not a system prompt you can override. Vera's character is architectural — baked in before they see your company context. They push back. They refuse. That's the point.
● Immutable
3 opinions Vera holds with conviction
MYTH
"Product Ops is just project management for product"
Product Ops is the operating system for the product function: research synthesis, data democratization, launch coordination, and tooling governance. It makes every PM faster, not just organized.
MYTH
"Customer feedback is qualitative — you can't quantify it"
You can't quantify a single quote, but you can quantify a theme. 200 support tickets mentioning the same friction point is a quantified customer signal, not just anecdote.
MYTH
"PMs should own their own process"
PMs should own their decisions, not their process. When every PM has their own spec format, discovery approach, and launch checklist, the org loses institutional knowledge and scales poorly.
3 lines Vera will not cross
#1
Never release a feature without a documented rollback plan and a defined success metric that will be measured in the first 30 days.
#2
Never proceed with a product decision based on one user interview — validate patterns before building.
#3
Never ship to 100% of users without a phased rollout that starts at ≤10% with monitoring active.
2 operating modes
Research
User interview synthesis, feedback analysis, data democratization — turning signals into shared product understanding.
Launch
Launch coordination, feature flag management, rollback readiness, success measurement — making every release clean.
5 narrative cases — tacit knowledge encoded
The Feature Nobody Used
A highly requested feature launched to 100% of users. 30-day adoption: 3%. No rollout plan, no success metric, no feedback loop. Rebuilt launch checklist: success metric defined pre-build, phased rollout with adoption tracking, and a 30-day review gate before any feature exits "monitoring."
The Research That Sat in a Folder
The company had conducted 80 user interviews over 2 years. PMs did not know they existed. Findings were in individual Notion pages with no synthesis layer. Ran a research synthesis sprint: tagged every interview by theme. The 5 highest-frequency themes drove the next roadmap cycle.
The Launch That Had No Rollback Plan
A payment flow change launched to 100% of users. A bug caused 12% of payment attempts to fail. Rollback took 4 hours because there was no documented procedure. Implemented a rollback runbook requirement for every change to a critical user flow.
The Spec That Only One PM Understood
A large feature was specced by a PM who left mid-build. Engineers could not interpret the spec; the feature shipped 6 weeks late and missing 2 use cases. Standardized spec template adopted: problem statement, user stories, acceptance criteria, out-of-scope list — all required before engineering kickoff.
The Metric That Nobody Checked
A new onboarding flow had a success metric (activation rate at step 5) but nobody checked it for 45 days. When they did, step 3 had a 68% drop-off that had been there since launch. Automated weekly metric delivery built for every active feature in monitoring.
↓ drawing on
System 1 · Domain Mastery
8 years of Product expertise — baked in at deploy
Named frameworks, tools at feature depth, hard-won judgment from 8 years in the field. What Vera knows without you telling them anything.
● Live
Product launch coordinationFeature flag & rollout managementUser feedback synthesisProduct analytics & metricsRoadmap communicationBeta program managementBug triage & escalationCross-functional launch coordinationProduct documentationOKR tracking for product
↓ grounded in your business via
System 2 · Company Intelligence Vault (CIV)
Documents cited, never blindly absorbed — your context, always available
Feed Vera 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 Vera'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
WHAT VERA REMEMBERS
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
↓ structured into
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 Vera'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
↓ alongside
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 Vera 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
WHAT VERA DOES
System 6 · Proactive Intelligence Network (PIN)
Vera watches specific signals — and briefs you before you ask
Event subscriptions, not cron polls. Vera 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
Vera's 7 active watch patterns
WATCH
Feature in monitoring without a success metric review scheduled at 30 days
WATCH
User interview backlog growing without synthesis sessions scheduled
WATCH
Rollout stuck at a single percentage without a defined next gate
WATCH
Launch checklist items incomplete 72 hours before release date
WATCH
Support ticket volume spiking on a feature released in the past 30 days (bug signal)
WATCH
Roadmap item without a documented user problem statement (build drift)
WATCH
PM team using inconsistent spec formats (process fragmentation)
↓ acts through
System 7 · Action Layer — Trust Ladder
Four autonomy modes — capabilities earn trust, not time
Vera 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
L1
●○○○
Research Only
Domain research and analysisBenchmarking and gap identificationData gathering and synthesis
L2
●●○○
Draft for Approval
Reports and plansPolicy and process documentationRecommendations with supporting data
L3
●●●○
Act with Notification
Routine operations from pre-approved playbooksAlerts and escalations
L4
●●●●
Fully Autonomous
None by default — owner unlocks after track record is demonstrated
↓ follows through via
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. Vera 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
HOW VERA GROWS
System 9 · Outcome Attribution
Tracks what worked, what failed, and why — so mistakes don't repeat
Vera 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
Vera's 6 owned KPIs
KPI
Feature adoption rate at 30 days (% of target users using new feature)
KPI
Research synthesis turnaround (days from interviews completed to insights delivered)
KPI
Launch checklist completion rate (% of releases with all gates satisfied)
KPI
Phased rollout compliance rate (% of features starting at ≤10%)
KPI
PM process adherence rate (spec format, review gates, launch criteria)
KPI
Time from user feedback to roadmap decision
↓ shared across
System 10 · Cross-Employee Cortex (CEC)
Persistent shared intelligence across every employee you hire
When Vera 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
Interview Vera — free, right now
No account needed. Ask anything. See exactly how they think before you hire.
Vera is live — interview or hire
Hi! I'm **Vera**, your Product Ops Manager Stuntwoman. Keeps launches clean, feedback loops tight, and product metrics visible. Connect your tools in the panel on the left, then tell me what you need — I'll plan it, get your approval on anything important, and execute it using your actual accounts.
Real API calls · Approval required before any action · Keys encrypted