Replacing the 1,000 Seats

Sets and owns company strategy, capital allocation, culture and the external face; final decision authority per §6.2.

Force multiplier for the CEO: owns the agenda, the escalation clock and cross-C-suite coordination that no line report owns.

Owns technical strategy, architecture at scale, platform bets and engineering culture across 374 + 26 R&D seats.

Deliverability leader: converts product roadmap into shipped software through 4 directors and ~30 teams.

Owns the production estate: infrastructure, reliability, developer platform and the runbooks the whole company pages from.

Program-level owner: staffs and aligns managers, owns a product area’s technical outcomes end to end.

Owns a team’s people, delivery and quality; the hinge between IC craft and company commitments.

Sets technical direction for a team or domain, writes the hardest code, raises the craft bar without a people budget.

Builds services, APIs, billing and integration logic — the server-side surface everything else consumes.

Turns designs into fast, accessible interfaces across web, native mobile and desktop clients.

Keeps production up with automation, not heroics: owns SLOs, paging quality and capacity.

Builds the automation that makes releases boring: frameworks, device farms, load gates and release checkpoints.

Builds the internal developer platform: golden paths, pipelines and service templates other engineers consume daily.

Runs cross-team engineering programs where the org chart ends: dependencies, risk, schedules and the status truth.

Owns what gets built and why: portfolio strategy, roadmap arbitration, product org and the customer-truth feedback loop.

Leads a product pillar (billing, core app, platform): coaches PMs, aligns strategy to the CPO roadmap, owns pillar outcomes.

Single accountable owner of a surface: discovers the problem, writes the PRD, shepherds delivery, watches the metric after launch.

Turns problems into interfaces: flows, prototypes, design-system stewardship and the usability bar features must clear.

The evidence layer: research studies, in-product copy systems, and the intake→triage→launch cadence machinery that keeps the roadmap honest.

Owns data as a product: strategy, platform economics, governance, and the metrics layer every division reports against.

Builds the pipelines and warehouse layers product telemetry flows through — freshness, quality and cost are their SLAs.

Owns the metrics layer: semantic models, dashboards and the single definition of “active user” the whole company reports against.

Ships models into product surfaces: serving infrastructure, evaluation harnesses and retraining loops that survive production traffic.

Answers “why” and “what if”: churn and pricing models, the experimentation platform, causal reads on business decisions.

Keeps the data estate findable, lawful and trustworthy: catalog, quality rules, retention, access policy enforcement with Legal.

Runs the three-year-horizon portfolio: feasibility probes, publishable research, prototypes that graduate to incubators.

Turns papers and hunches into demo-able artifacts: fast, honest prototypes with measured claims.

Owns the company’s risk posture: threat model at company scale, compliance proof, and the security voice enterprise customers hear.

Finds and prevents vulnerabilities in code and cloud before customers do: reviews, scanning at scale, threat models per feature.

Watches, detects, contains: detection engineering, alert triage across shifts, identity lifecycle enforcement.

Turns controls into evidence and abuse policy into product rules: audits, questionnaires, certification maintenance and abuse-risk review.

Carries the company number: quota allocation, forecast truth, deal-desk arbitration and the field machine.

Owns the full sales cycle on named accounts: discovery to signed contract, with the technical win via SEs.

Opens conversations: outbound sequences, inbound qualification, and booked meetings that fit the AE’s ideal profile.

Owns the technical win: demos that match the use case, PoCs with success criteria, security & integration reviews.

Builds the reseller, agency and marketplace machine: recruitment, enablement, co-sell motions and channel hygiene.

The operating system of the revenue engine: CRM truth, comp admin, forecasting models and tooling across Sales/CS/Marketing.

Owns demand, brand and narrative: budget allocation across channels, the company story, and pipeline shared with the CRO.

Translates features into outcomes buyers understand: positioning per pillar, launch plans, battlecards for the field.

Fills the funnel with profit-in-qualified-terms: paid media, lifecycle email, ABM plays and webinar programs against pipeline targets.

The reach layer: editorial systems, visual identity, live moments and PLG experiments that compound the brand and pipeline.

Owns the public narrative and the crisis voice: media relations, exec comms, and the comms track of the escalation flow (§6.1).

Owns retention, resolution and the usage relationship: NRR health, support economics, and the customer-truth input to Product.

Portfolio owner for adoption and renewal health: success plans, QBRs, risk flags and expansion signals handed to Sales.

The technical deep partners: architecture-adjacent guidance for top accounts, and the 30–90 day activation journey for new logos.

Resolves, reproduces and escalates with evidence: triage from runbooks up to code-level investigation for the hardest cases.

Owns the numbers, the controls and the capital: plan vs actual across the 1,000-seat ledger, audit relationships, and the approval spine (§6.2).

Business-partners every division head: budget lines, headcount models, the variance story behind the monthly review.

The transaction engine: close, pay, invoice, collect, payroll, tax — each on checklists and segregation-of-duties rules.

Tests the controls and runs the buying desk: control walkthroughs, vendor risk intake, SaaS/cloud spend discipline.

Owns the people system: band architecture, the hiring plan against §7’s ledger, org health, and the manager-ship standard of 165 leaders.

Runs the req pipeline against the hiring plan: sourcing, loop design, offer negotiation and candidate experience at 71:29 IC-to-manager hiring volume.

The people operating layer: contracts & moves, HRIS integrity, onboarding camp, manager academy, band maintenance and the internal comms machinery.

Holds the external-commitment gate: enterprise contracts, IP, privacy program, employment matters and board advisory — final counter-signature in §6.2.

Internal product: helpdesk, device fleet, corporate network and the SaaS admin layer — the employee-facing analogue of customer Support.

Runs company-level programs the org chart cannot express: market entry, certification, cost programs — with named C-suite sponsors and honest status.

The delivery mechanics embedded in divisions: sprint health, status discipline, process maps and requirements for internal systems work.

Fleet orchestrator — routes every task to the right agent, balances load across instances, and keeps the queue honest about what is stuck and why.

Front door for human requests — turns a vague ask into a complete, checkable task brief before any work begins.

Owns the human-approval queue — packages each decision so a person can approve or reject in under two minutes, and chases nothing into a void.

Adversarial tester — tries to make agents fail, drift, overreach or leak, before customers or auditors do.

Eval-harness owner — builds and runs the golden sets that decide whether any agent keeps its autonomy level.

Behaviour drift monitor — watches outputs over time for slow decay in quality, tone or judgement before it becomes an incident.

Guardrail watchdog — verifies G1–G10 are actually enforced at the tool boundary and audits every exception.

Agent security — defends the fleet against prompt injection, tool abuse, corpus poisoning and identity misuse.

Knowledge curator — keeps the corpus each agent learns from accurate, current, deduplicated and lawfully held.

Skill and tool librarian — maintains the registry of what each agent may do and with which tools, so permissions never sprawl.

Cost auditor for the fleet — meters compute and tool spend per agent and per task, and flags waste before it compounds.

Agent lifecycle operations — provisions new agents, manages configuration and permissions, retires the ones no longer needed.

Fleet observability — the single pane that shows what every agent is doing, what it costs, and where it is stuck.

Training-data factory — builds the labelled datasets (tickets, deals, incidents, contracts) each agent learns its role from.

Continuity and failover — keeps a warm path so that if an agent, model route or tool fails, the workflow continues safely.