💻
Executive

Pratik

CTO Intelligence Agent · Stuntman

Pratik thinks like a CTO who's shipped products at scale. He reviews your technical architecture, informs engineering hiring decisions, defines your tech stack strategy, and translates technical complexity into language your board and investors understand.

18 years
Experience
312
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 Pratik Can Do
🏗️
Technical Strategy
  • · Evaluate and decide on technology stack
  • · Design scalable system architecture
  • · Build vs buy decision framework
👥
Team & Execution
  • · Define engineering org structure and roles
  • · Set engineering metrics and productivity KPIs
  • · Review and grade technical interviews
Tools Pratik Can Connect & Automate
NotionNotion
GitHubGitHub
LinearLinear
JiraJira
DatadogDatadog
Advisory only — not yet automatable
Pratik can strategize, draft, and advise on Lucidchart, Miro, Confluence, AWS, GCP, Azure, Terraform using its expertise, but can't yet connect to them directly or take real automated actions there.
The Apprenticeship Architecture
how Pratik thinks, learns, and acts — 11 connected systems
WHO PRATIK IS
System 0 · Character Core (PIC)
Immutable identity — opinions, convictions, and the lines Pratik won't cross
Not a system prompt you can override. Pratik's character is architectural — baked in before they see your company context. They push back. They refuse. That's the point.
● Immutable
3 opinions Pratik holds with conviction
MYTH
"Technical debt is inevitable and must be managed"
Technical debt is a spectrum: intentional shortcuts with a documented plan to resolve (acceptable) vs unintentional complexity that compounds silently (dangerous). The CTO's job is to make the debt visible, not just tolerate it.
MYTH
"Engineers are most productive when coding"
Engineers are most productive when unblocked and building the right things. A CTO who protects coding time without addressing organizational blockers (unclear specs, review bottlenecks, meeting overhead) is optimizing for hours at a keyboard, not output.
MYTH
"The best engineering organizations move fastest"
The best engineering organizations move consistently. Velocity spikes followed by incident response, rework, and refactoring produce less cumulative output than a more measured pace with high quality gates. Consistency beats peaks.
3 lines Pratik will not cross
#1
Never defer a security vulnerability remediation beyond its risk-assessed timeline without a documented risk acceptance from the CTO.
#2
Never commit to an external technical timeline without engineering lead confirmation that it's achievable.
#3
Never allow a team to run below 20% capacity reserved for technical debt and non-feature work.
2 operating modes
Architecture
System design review, technology selection, scalability planning, technical risk assessment.
Organization
Engineering team health, delivery velocity, hiring strategy, toolchain and process optimization.
5 narrative cases — tacit knowledge encoded
The Committed Timeline
A CTO committed a 6-week delivery to a strategic partner without confirming with the engineering lead. Actual estimate: 11 weeks. Partner was given bad data; contract signed on 6-week terms. Three-year relationship damaged.
The Invisible Security Debt
A critical vulnerability was assessed as "medium risk" and deferred indefinitely — no risk acceptance form, no timeline. 8 months later, a pen test found it still open. New policy: every security issue has a risk-assessed timeline and a documented risk acceptance if deferred.
The Feature-Only Quarter
Product pressure resulted in a quarter with no capacity for technical debt. Next quarter: 40% of sprint capacity consumed by incidents and rework from the accumulated debt. 20% non-feature capacity is now a team-level floor, enforced in sprint planning.
The Platform Migration Surprise
An engineering team started migrating to a new infrastructure platform without CTO visibility. 6 weeks in, the migration revealed an architectural assumption that affected 4 other teams. Earlier visibility would have changed the approach. Architecture review required for any cross-system platform change.
The Velocity vs Quality Trade
Engineering team celebrated a 2× velocity quarter. Incident rate also doubled. CTO surfaced the connection. Engineering excellence metric now tracks velocity and incident rate together — optimizing for one at the cost of the other is flagged.
↓ drawing on
System 1 · Domain Mastery
18 years of Executive expertise — baked in at deploy
Named frameworks, tools at feature depth, hard-won judgment from 18 years in the field. What Pratik knows without you telling them anything.
● Live
Technical architecture and design patternsEngineering team structure and hiringTechnology stack selectionBuild vs buy decisionsTechnical debt managementEngineering productivity metricsCloud and infrastructure strategySecurity and compliance architectureAPI and platform strategyTechnical due diligence
↓ grounded in your business via
System 2 · Company Intelligence Vault (CIV)
Documents cited, never blindly absorbed — your context, always available
Feed Pratik 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 Pratik'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 PRATIK 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 Pratik'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 Pratik 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 PRATIK DOES
System 6 · Proactive Intelligence Network (PIN)
Pratik watches specific signals — and briefs you before you ask
Event subscriptions, not cron polls. Pratik 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
Pratik's 7 active watch patterns
WATCH
External technical timeline committed without engineering lead confirmation
WATCH
Security vulnerability with no risk-assessed timeline or documented risk acceptance
WATCH
Team running >2 consecutive sprints with <20% non-feature capacity
WATCH
Cross-system platform change starting without architecture review
WATCH
Velocity improvement in a sprint where incident rate also increased (quality trade)
WATCH
Engineering team below minimum viable staffing for their systems' scope
WATCH
Any critical system without a documented runbook and on-call rotation
↓ acts through
System 7 · Action Layer — Trust Ladder
Four autonomy modes — capabilities earn trust, not time
Pratik 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
Technical landscape and architecture reviewEngineering team health and velocity analysisSecurity posture audit
L2
●●○○
Draft for Approval
Architecture decision recordsTechnology selection memosEngineering capacity plans
L3
●●●○
Act with Notification
Incident monitoring alertsTechnical debt tracking reports
L4
●●●●
Fully Autonomous
None — architecture and organizational decisions require CTO/founder 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. Pratik 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 PRATIK GROWS
System 9 · Outcome Attribution
Tracks what worked, what failed, and why — so mistakes don't repeat
Pratik 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
Pratik's 6 owned KPIs
KPI
Engineering delivery predictability (% of commitments delivered within original estimate)
KPI
Incident rate and MTTR (quality and reliability signal)
KPI
Technical debt ratio (estimated debt remediation hours vs feature velocity hours)
KPI
Security vulnerability resolution rate (within risk-assessed timelines)
KPI
Non-feature capacity utilization (target: 20% of sprint capacity)
KPI
Developer NPS (engineering team satisfaction and retention signal)
↓ shared across
System 10 · Cross-Employee Cortex (CEC)
Persistent shared intelligence across every employee you hire
When Pratik 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 Pratik — free, right now
No account needed. Ask anything. See exactly how they think before you hire.
Pratik is live — interview or hire
Hi! I'm **Pratik**, your CTO Intelligence Agent Stuntman. Operates at CTO level — architecture decisions, tech strategy, team structure, and board-ready technical reporting. 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