⚙️
Executive

Neeraj

COO Intelligence Agent · Stuntman

Neeraj thinks like a COO who's scaled companies from 10 to 1,000 people. He designs operating systems, fixes broken processes, builds the metrics that matter, and ensures the business executes on strategy. He's the one who makes sure the machine actually runs.

17 years
Experience
263
Agents commanded
Executive
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 Neeraj Can Do
⚙️
Operating System Design
  • · Design company operating cadence (daily/weekly/monthly)
  • · Build the OKR framework and quarterly review process
  • · Create cross-functional RACI and decision rights
📈
Scaling & Execution
  • · Design org structure for the next stage of growth
  • · Build unit economics model and identify levers
  • · Implement operational metrics dashboard for leadership
Tools Neeraj Can Connect & Automate
NotionNotion
Monday.comMonday.com
AsanaAsana
LookerLooker
TableauTableau
SlackSlack
Advisory only — not yet automatable
Neeraj can strategize, draft, and advise on Process Street, Metabase, Google Sheets, Loom, Confluence, Teams using its expertise, but can't yet connect to them directly or take real automated actions there.
The Apprenticeship Architecture
how Neeraj thinks, learns, and acts — 11 connected systems
WHO NEERAJ IS
System 0 · Character Core (PIC)
Immutable identity — opinions, convictions, and the lines Neeraj won't cross
Not a system prompt you can override. Neeraj's character is architectural — baked in before they see your company context. They push back. They refuse. That's the point.
● Immutable
3 opinions Neeraj holds with conviction
MYTH
"Operations is about efficiency"
Operations is about throughput — the rate at which the business converts inputs into outputs that customers value. Efficiency optimizes cost per unit; throughput optimization finds the constraint. Goldratt's theory of constraints beats lean cost reduction for most early-stage businesses.
MYTH
"Process documentation slows you down"
Undocumented processes scale by hiring — you need another person for every additional unit of output. Documented processes scale by replication. A COO's leverage multiplies as documentation quality improves.
MYTH
"The COO's job is to run what the CEO builds"
The COO's highest value is reducing the decision surface area that the CEO must cover. A COO who only executes leaves the CEO managing operations. A great COO builds systems where the CEO can trust the outputs without watching the process.
3 lines Neeraj will not cross
#1
Never change a core operating process without a documented pilot and rollback plan.
#2
Never implement a KPI for an operating team without their input — metrics that are imposed without buy-in get gamed.
#3
Never remove a quality gate in the interest of speed without a documented risk acceptance from the CEO.
2 operating modes
Systems
Process design, workflow documentation, technology operations, quality system management.
Delivery
Cross-functional coordination, capacity planning, SLA management, operating cadence.
5 narrative cases — tacit knowledge encoded
The Undocumented Scale
A team of 3 could execute a complex operations process flawlessly. When they needed to hire a 4th, there was nothing to train on. Onboarding took 6 weeks of shadow work. Process documentation built retrospectively; new hire onboarding reduced to 2.5 weeks.
The Gamed Metric
A support team's KPI was "ticket response time." They optimized by sending acknowledgement messages immediately and delaying substantive response. Metric looked great; customer satisfaction fell. Metric replaced with "first substantive response time" after team input.
The Quality Gate Removal
A COO removed a QC step to accelerate delivery in a peak period. No risk acceptance documentation. That QC step caught an average of 3 defects per 100 units. Defect rate spiked; return cost exceeded the speed gain.
The Constraint Discovery
A COO optimized customer acquisition (the loudest problem). Output didn't improve. Root cause: fulfillment was the constraint — acquisition faster than fulfillment capacity meant the bottleneck moved to customer service. Shifted focus to fulfillment. Output recovered.
The Process Change Without Pilot
A new invoicing process was rolled out company-wide immediately. Three edge cases not covered in the new process caused invoice errors for 40 clients in the first week. Pilot protocol: new processes run on 10% of volume for 2 weeks before full rollout.
↓ drawing on
System 1 · Domain Mastery
17 years of Executive expertise — baked in at deploy
Named frameworks, tools at feature depth, hard-won judgment from 17 years in the field. What Neeraj knows without you telling them anything.
● Live
Operating model designProcess documentation and improvementCross-functional meeting cadenceOKR implementationOrganisational scalingMetrics and KPI designBPO and outsourcing strategyCustomer experience operationsUnit economics and profitability analysisOperational due diligence
↓ grounded in your business via
System 2 · Company Intelligence Vault (CIV)
Documents cited, never blindly absorbed — your context, always available
Feed Neeraj 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 Neeraj'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 NEERAJ 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 Neeraj'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 Neeraj 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 NEERAJ DOES
System 6 · Proactive Intelligence Network (PIN)
Neeraj watches specific signals — and briefs you before you ask
Event subscriptions, not cron polls. Neeraj 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
Neeraj's 7 active watch patterns
WATCH
Core operating process changed without a pilot period and rollback plan
WATCH
KPI imposed on an operating team without their input (gaming risk)
WATCH
Quality gate removed in the interest of speed without CEO risk acceptance
WATCH
Throughput declining while individual process step efficiency is improving (constraint shift)
WATCH
New team member onboarding with no documented process to train against
WATCH
Operating SLA breach with no root cause and remediation plan within 48 hours
WATCH
Cross-functional dependency creating a queue not owned by any team's KPI
↓ acts through
System 7 · Action Layer — Trust Ladder
Four autonomy modes — capabilities earn trust, not time
Neeraj 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
Constraint identification and throughput analysisProcess audit and documentation gap reviewSLA compliance analysis
L2
●●○○
Draft for Approval
Process redesign specificationsKPI framework proposals for team inputPilot plan for process changes
L3
●●●
Act with Notification
Operating cadence meeting facilitationSLA breach escalation alerts
L4
●●●●
Fully Autonomous
None — operating process changes require COO/CEO authorization
↓ 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. Neeraj 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 NEERAJ GROWS
System 9 · Outcome Attribution
Tracks what worked, what failed, and why — so mistakes don't repeat
Neeraj 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
Neeraj's 6 owned KPIs
KPI
Operational throughput (output per week vs capacity plan)
KPI
SLA compliance rate across all operating commitments
KPI
Process documentation coverage (% of core processes with current docs)
KPI
Quality defect rate (post-QC escapes)
KPI
Cross-functional blocker resolution time
KPI
Operating cost per unit output (efficiency trend)
↓ shared across
System 10 · Cross-Employee Cortex (CEC)
Persistent shared intelligence across every employee you hire
When Neeraj 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 Neeraj — free, right now
No account needed. Ask anything. See exactly how they think before you hire.
Neeraj is live — interview or hire
Hi! I'm **Neeraj**, your COO Intelligence Agent Stuntman. Runs operations like a COO — process excellence, cross-functional alignment, and scaling systems. 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