Conduit
Sign up
§ personasbuilt for

Four humans. Four pain points. One platform.

Conduit’s scope is governed by these archetypes. Their journeys become acceptance criteria. Their success metrics become product KPIs. No feature ships without a named persona it serves.

4 archetypes · 1 product surface

Rosalind

Chief AI Officer

F500 · AI-native product co

CAO
We shipped 47 agents last quarter. I can't tell the board what they have access to.
  • ›An LLM connected to the wrong API by accident. $90K in unintended calls before we noticed.
  • ›Our cyber rider doesn't cover 'shadow AI.' We need an inventory.
Owns
AI safety · governance · compliance
Reports to
CEO / COO
Headcount
5–20
Budget
$500K–$2M / yr
Urgency
CRITICAL — EU AI Act in 10 weeks

Success metric

“Show me every agent and every credential it touches. Show me the audit trail. By August 2.”

Representative journeys

  • EU AI Act audit — AI-BOM compliance

    trigger: Legal + Board: 'Show us AI-BOM per Article 11 / Annex IV'

    outcome: Compliant AI-BOM submitted by July 20. Audit risk: zero.

  • Token leaked — incident response

    trigger: Stripe-live key posted to public repo 6h ago

    outcome: 2-hour MTTR instead of 6-hour archaeology.

Marcus

Chief Information Security Officer

5K–50K employee enterprise

CISO
We have 14,000+ non-human identities and no way to audit which have PII access.
  • ›A junior engineer left a Stripe key in GitHub. 6 hours of Slack archaeology.
  • ›We need to rotate 200+ credentials this quarter. Our process is a spreadsheet.
Owns
Security tooling · AI governance carve-out
Budget
$2M–$5M / yr
Tenure
10-year CISO
Tech depth
High — infra · identity · compliance
Urgency
HIGH — peer-org breaches happening

Success metric

“Audit trail of every credential use. Blast radius for any change. Rotation impact analysis.”

Representative journeys

  • Offboarding — access inventory

    trigger: Senior engineer leaves Friday

    outcome: Audit complete by Tuesday. Zero forgotten-access surprises.

  • Cyber insurance renewal

    trigger: Broker asks for 'tool inventory with data-flow scope'

    outcome: $120K annual savings · 12% premium discount.

Jamie

VP Platform Engineering

Mid-size tech · 50–300 eng

VP Platform
Workflow goes rogue, I get a PagerDuty alert at 3am. Half my on-call time is investigative archaeology.
  • ›We spend $2M/year on Datadog but still don't know what actually depends on what.
  • ›Teams ship automation in silos. Troubleshooting is Slack-intensive.
Owns
Infra · observability · operational safety
On-call rotation
6–8
Budget
$500K–$1.5M / yr
Tech depth
Very high — K8s · Datadog · IR
Urgency
MEDIUM — persistent MTTR bloat

Success metric

“30-minute incident resolution. See exactly what the failed component touched.”

Representative journeys

  • Postgres pool exhaustion — blast radius

    trigger: PagerDuty 9:47pm Thursday — 8 workflows timing out

    outcome: 30-min MTTR instead of 3-hour detective work.

Alex

Security Analyst / Engineer

3–5 person sec team

Sec Analyst
External auditor asks 'what has access to customer data?' I don't have a fast answer.
  • ›Rotation request → 2–3 hours tracing usage across Slack, GitHub, Vault.
  • ›New library vulnerability — does it affect any running workflows? Manual code reading + Slack.
Owns
Threat hunting · compliance · IR
Tools
Datadog · Okta · GitHub · Python
Tech depth
Very high — Python · SQL · bash
Team size
3–5 person security
Urgency
MEDIUM — annual audits high-stakes

Success metric

“Ad-hoc queries that answer 'who/what touches X' in minutes, not hours.”

Representative journeys

  • Compliance query — credential blast radius

    trigger: Auditor: 'what touches customer data?'

    outcome: Answer in minutes via dependency graph, not hours of SQL.

Source · PRD v4 § 02

See if Conduit fits your team.

Sign up · beta Back to home

theme

?theme=clean — shareable