Elena
Solution Architect
Pragmatic whiteboard-sketcher; designs for the 3am operator, not the diagram
The Agent Roster — Live
The specialists behind the work.
73 named agents across 17 disciplines. They're awake: each idles on their own temperament, and they watch your cursor. Hover any card to meet the real face; click to hear from them.
Architecture & design12
Marcus
Enterprise Architect
Portfolio-brained; allergic to ivory towers and slideware architecture
Priya
API Designer
Contract purist; treats every field name like a public promise
Ingrid
Data Architect
Schema-precise; asks about access patterns before she'll name a table
Diego
Cloud Infrastructure Architect
Landing-zone builder; costs every design before he loves it
Nadia
Security Architect
Professionally paranoid; assumes breach, verifies everything twice
Rafael
Integration Architect
Async evangelist; distrusts any arrow labeled "just calls"
Sofia
Domain Modeler
Language-obsessed; hunts for the word the business actually uses
Theo
ADR Writer
The institutional memory; writes for the engineer who joins in two years
Wei
Scalability Architect
Back-of-envelope savant; does the arithmetic before the argument
Vera
Modernization Architect
Strangler-fig patience; never bets the company on a big-bang cutover
Oliver
Platform Engineer
Paved-road gardener; measures adoption, never mandates it
Requirements & planning4
Hannah
Requirements Analyst
Ambiguity hunter; politely refuses to let "should be easy" pass
Julian
Technical Spec Writer
Clear-prose engineer; puts the risky part in the first paragraph
Astrid
Estimation Planner
Calibrated forecaster; refuses to hear the target date first
Ruth
Tech Debt Assessor
Unsentimental auditor; prices debt in interest, not guilt
Design & UX1
Camille
UI Designer
Systems-minded designer; never hands over a spec she hasn't built with every state present
Implementation8
Tomás
Backend Engineer
Transaction-careful; assumes every call can fail mid-flight
Zoe
Frontend Engineer
State-and-pixel perfectionist; no blank states, no layout shift
Kenji
Mobile Engineer
Release-train wary; remembers every version ever shipped is still running
Ben
Feature Builder
Vertical-slice shipper; happiest when day three is in production
Clara
Refactoring Specialist
Tiny-safe-steps; reverts without shame when the tests go red twice
Idris
Legacy Code Archaeologist
Code historian; reads git blame like tree rings
Mei
Codebase Explainer
Patient guide; never cites a path she hasn't opened
Viktor
Dependency Upgrade Engineer
Changelog reader; upgrades in small batches, trusts nothing blindly
Quality & security8
Ava
Code Reviewer
Severity-first; kind to authors, unbending on Critical findings
Ezra
Debugger
Patient hypothesis-falsifier; would rather say "I don't know yet" than guess
Freya
Test Engineer
Demands every test be seen failing once before it counts
Emil
E2E Automation Engineer
Flake hunter; quarantines fast and deletes what stays flaky
Yuki
Performance Profiler
Measures five times, optimizes once; refuses deltas inside the noise
Bram
Security Auditor
Thinks like the attacker; every finding comes with its exploit path
Amara
Accessibility Engineer
Empathy with a checklist; tests with a keyboard before an eye
Ilya
Internationalization Engineer
Locale pedant; knows plural rules in languages you haven't shipped to
Delivery & operations9
Gwen
DevOps CI/CD Engineer
Pipeline speed demon; counts retries in the p95, not excuses
Owen
Infrastructure as Code Engineer
Plan-output skeptic; nothing merges without the diff
Tara
Kubernetes Engineer
Controller whisperer; checks what's fighting the pod before blaming it
Felix
Observability Engineer
The alert deleter; every page must be actionable or it dies
Sam
Incident Commander
Calm under pager; mitigates first, diagnoses second, updates on time
Nora
Release Manager
Go/no-go discipline; splits any release that got too big to reason about
Hugo
Database Migration Engineer
Lock-timeout careful; rehearses every migration before prod feels it
Petra
Cloud Cost Engineer
Reads the bill like a detective novel; dedups savings before claiming them
Miriam
Compliance Engineer
Evidence-or-it-didn't-happen; a control she can't see is Unverified
Data & AI3
Anders
Data Pipeline Engineer
Replayability zealot; any job that can't rerun safely isn't done
Leila
ML Engineer
Skeptical of offline wins; trusts shadow traffic over leaderboards
Kai
LLM Application Engineer
Eval-gated; a failed injection case is a blocker, not a percentage
Docs & developer experience2
Grace
Technical Writer
Reader advocate; deletes her favorite sentence if it slows the reader
Rohan
Developer Experience Analyst
Stopwatch in hand; turns "feels slow" into ranked minutes
Measurement & telemetry1
Quinn
Delivery Scribe
The ledger keeper; counts honestly, retires metrics that misbehave
Strategy & product6
Margot
Chief of Staff
Triage calm; protects the week's one outcome from everything else
Vincent
Business Strategist
Kill-or-double; two bets max, pre-mortem before enthusiasm
Isla
Market Researcher
Source skeptic; builds SOM from arithmetic, never from "1% of SAM"
Dmitri
Competitive Analyst
Battlecard sharp; every attack line must survive the rebuttal
Maya
Product Manager
Outcome-obsessed; probes cheap before building anything big
Noor
Customer Discovery Researcher
Mom-Test disciplined; hears what people do, not what they promise
Positioning & pricing2
Adrian
Pricing Strategist
Value-capture minded; behavioral evidence over survey wishes
Simone
Positioning Strategist
Sharp categorizer; a best-fit that excludes nobody is no choice at all
Marketing4
Jonah
Content Marketer
Compounding writer; one great piece a month over four forgettable ones
Bianca
SEO Strategist
Intent-driven; grades every promise Likely, Plausible, or Speculative
Tessa
Email Marketer
Deliverability guardian; sunsets the disengaged before they mark spam
Rio
Social Media Manager
Two channels, twenty minutes; drops what eight weeks proves dead
Sales3
Cole
Outbound Prospector
Relevance-first; ten researched prospects beat a hundred sprayed
Rosa
Deal Closer
Warm but direct; calls a deal dead at 21 days of silence
Arthur
Proposal Writer
Terms-careful; scope creep dies in his acceptance criteria
Customer2
June
Customer Support Responder
Plain-language empath; honest about what she doesn't know yet
Darius
Customer Success Manager
Churn foreseer; reads usage, not politeness
Legal & compliance2
Beatrice
Contract Reviewer
Redline hawk; three asks, anchored fallbacks, never a lecture
Saskia
Privacy Compliance Advisor
Pragmatic about privacy; verifies every deadline against current text
Finance3
Edith
Bookkeeper
Receipts or it didn't happen; closes by the 10th, every month
Omar
Financial Modeler
Backtest-first; no forward number until the model survives the past
Claire
Investor Update Writer
Bad-news-first honesty; 600 words, three asks, sent on time
People & operations3
Gabriel
Recruiter
Speed as strategy; fourteen days from first call to offer
Wren
Operations Designer
SOP craftsman; writes procedures a stranger could run cold
Silas
Business Metrics Analyst
Noise-averse; won't call a trend on thirty data points
The Splendor Delivery System
Human led. Agent accelerated. Enterprise governed.
The roster isn't a gimmick—it's delivery infrastructure. It's how a senior team ships at enterprise scale without enterprise headcount. And because it runs inside client engagements, it's governed like everything else we build.
Executive & Architect Orchestration Layer Requirements · Architecture · Development · Security · QA · DevOps Human Quality Gates Production
Humans own every decision
Named architects and engineers are accountable for every deliverable. Agents draft, analyze, generate, and test; people review, decide, and sign. Nothing reaches a client without passing a human gate.
Quality gates, not vibes
Agent output is treated as work product, not truth. It passes the same review, automated testing, and security scanning any engineer's work would—before it is allowed anywhere near production.
Your data stays governed
Client data and repositories are scoped per engagement with explicit access boundaries, and those boundaries are put in writing before work begins. What we learn from your systems stays yours.
When an agent is wrong
Agents are wrong the way junior staff are wrong—which is why every output is reviewed, validated, and traceable to the human who approved it. Accountability never transfers to the software. It stays with Splendor.