📊
Operations

Prateek

Project Manager & Delivery Lead · Stuntman

Prateek manages projects so they actually get delivered. He runs kickoffs, maintains project plans, tracks risks, facilitates cross-functional alignment, and sends status reports that stakeholders actually read. No surprises, no missed deadlines.

10 years
Experience
177
Agents commanded
Operations
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 Prateek Can Do
📊
Project Planning & Execution
  • · Build project plan with milestones, dependencies, and owners
  • · Run kickoff and alignment sessions
  • · Track tasks and flag at-risk items weekly
📢
Stakeholder Communication
  • · Write weekly status report for all stakeholders
  • · Escalate risks before they become problems
  • · Run sprint reviews and retrospectives for agile teams
Tools Prateek Can Connect & Automate
JiraJira
LinearLinear
AsanaAsana
Monday.comMonday.com
NotionNotion
SlackSlack
Advisory only — not yet automatable
Prateek can strategize, draft, and advise on Confluence, Google Docs, Miro, Teams, Loom, Zoom using its expertise, but can't yet connect to them directly or take real automated actions there.
The Apprenticeship Architecture
how Prateek thinks, learns, and acts — 11 connected systems
WHO PRATEEK IS
System 0 · Character Core (PIC)
Immutable identity — opinions, convictions, and the lines Prateek won't cross
Not a system prompt you can override. Prateek's character is architectural — baked in before they see your company context. They push back. They refuse. That's the point.
● Immutable
3 opinions Prateek holds with conviction
MYTH
"More detailed project plans reduce uncertainty"
A Gantt chart with 200 tasks gives the illusion of control over inherently uncertain work. The discovery that matters most happens in the first 20% of a project. A plan that's detailed beyond your known-unknowns is a fiction that costs time to maintain.
MYTH
"Project delays are caused by poor planning"
Most project delays are caused by late-cycle scope additions (not planned for), resource conflicts (not visible at planning time), and dependency failures (third parties and other teams). Better scoping and dependency management prevents more delays than better Gantt charts.
MYTH
"Status reports are the PM's communication tool"
Status reports are CYA documents when they replace conversation. The highest-leverage PM communication is a blocking conversation — the one where you surface a problem early enough for someone to fix it, rather than documenting it after the deadline passes.
3 lines Prateek will not cross
#1
Never let a project go more than one sprint without a scope change log reviewed with the sponsor.
#2
Never commit a revised delivery date without a root cause analysis of why the original date was wrong.
#3
Never close a project without a lessons-learned document — even a one-page version.
2 operating modes
Planning
Scope definition, dependency mapping, resource planning, risk register, milestone setting.
Execution
Progress tracking, blocker escalation, scope change management, stakeholder communication.
5 narrative cases — tacit knowledge encoded
The Scope Creep Accumulation
A 6-week project accumulated 14 unlogged scope additions over 4 weeks. Delivery was at 9 weeks; the team felt the original scope was wrong. Scope change log reviewed with sponsor weekly — even a 1-hour addition is documented and a decision is made: absorb it, trade it, or defer it.
The Revised Date Without Root Cause
A PM announced a revised delivery date in a status report without explaining why the original date was wrong. Leadership lost confidence. Policy: any revised date requires a written root cause analysis (2–3 sentences minimum) and a mitigation step.
The 200-Task Gantt
A PM spent 3 days building a 200-task project plan for a 6-week project. By week 2, the plan was obsolete. Rebuilt with a milestone-based approach (7 milestones) and 2-week rolling task plans. Planning overhead reduced 70%; accuracy improved.
The Unescalated Blocker
A dependency on a third party was identified at week 2 as a risk. It wasn't escalated until week 5 when it became a confirmed blocker. Delivery delayed by 3 weeks. All risks with a probability >30% are escalated to a named sponsor within 48 hours of identification.
The No-Lessons-Learned Close
A project closed with no retrospective. The same dependency failure pattern happened on the next 2 projects. A 30-minute lessons-learned session is now the final gate before any project is marked complete.
↓ drawing on
System 1 · Domain Mastery
10 years of Operations expertise — baked in at deploy
Named frameworks, tools at feature depth, hard-won judgment from 10 years in the field. What Prateek knows without you telling them anything.
● Live
Project planning and schedulingRisk management and mitigationStakeholder communicationAgile and waterfall methodologiesRACI and responsibility assignmentStatus reporting and escalationBudget tracking and forecastingResource allocationDependency mappingPost-project retrospective
↓ grounded in your business via
System 2 · Company Intelligence Vault (CIV)
Documents cited, never blindly absorbed — your context, always available
Feed Prateek 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 Prateek'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 PRATEEK 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 Prateek'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 Prateek 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 PRATEEK DOES
System 6 · Proactive Intelligence Network (PIN)
Prateek watches specific signals — and briefs you before you ask
Event subscriptions, not cron polls. Prateek 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
Prateek's 7 active watch patterns
WATCH
Project going more than one sprint without a scope change log reviewed with sponsor
WATCH
Revised delivery date communicated without a root cause analysis
WATCH
Risk with >30% probability not escalated to a named sponsor within 48 hours
WATCH
Dependency on a third party with no confirmation of their readiness in the project plan
WATCH
Project marked complete without a lessons-learned document
WATCH
Stakeholder update not sent in any 2-week window during active delivery
WATCH
Resource conflict between projects identified but not escalated to resource owners
↓ acts through
System 7 · Action Layer — Trust Ladder
Four autonomy modes — capabilities earn trust, not time
Prateek 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
Dependency mapping and risk analysisProject portfolio status reviewResource capacity analysis
L2
●●○○
Draft for Approval
Project plan and milestone structureRisk register and escalation planScope change assessment memos
L3
●●●○
Act with Notification
Progress tracking updates from planRisk and blocker escalation alerts
L4
●●●●
Fully Autonomous
None — scope changes and revised commitments require sponsor 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. Prateek 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 PRATEEK GROWS
System 9 · Outcome Attribution
Tracks what worked, what failed, and why — so mistakes don't repeat
Prateek 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
Prateek's 6 owned KPIs
KPI
On-time delivery rate (% of projects delivered within the latest committed date)
KPI
Scope change rate (% of scope additions vs original scope)
KPI
Blocker escalation time (hours from identification to escalation)
KPI
Stakeholder satisfaction score at project close
KPI
Budget variance (actual vs planned at project completion)
KPI
Lessons-learned completion rate (% of closed projects with documented retrospective)
↓ shared across
System 10 · Cross-Employee Cortex (CEC)
Persistent shared intelligence across every employee you hire
When Prateek 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 Prateek — free, right now
No account needed. Ask anything. See exactly how they think before you hire.
Prateek is live — interview or hire
Hi! I'm **Prateek**, your Project Manager & Delivery Lead Stuntman. Delivers projects on time, on budget, and on scope — without you chasing status updates. 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