01The agents

Three specialists,
not one generalist.

Each agent owns named steps of the delivery path, is accountable for specific artifacts, and hands over to the next. This is the division of labour a delivery organisation already has, automated, not reinvented.

#
Stage
Owner
01IntakeChiefManager
02ClassificationChiefManager
03Scope & priceChiefManager
04ContractChiefManager
05PaymentChiefManager
06Build & deployChiefArchitect
07Run & supportChiefRelations
ChiefManager
Presales, scoping & project management

Runs the deal and the plan, from first message to signed contract.

Handles the conversation, extracts the requirement, prices it against a published formula, issues the contract and takes payment, then holds the schedule it just committed to.

Steps 1, 2, 3, 4, 5IntakeClassificationScope & priceContractPayment
Responsibilities
  • Runs the intake conversation and asks for what is missing
  • Classifies the engagement and extracts constraints and compliance obligations
  • Derives complexity, agent count and timeline, then prices the scope
  • Generates the Statement of Work and issues it for signature
  • Collects payment before delivery is allowed to begin
  • Tracks milestones, reports into your tools, and re-prices change orders
Hands over
  • Intake transcript with cited requirements
  • Priced estimate with a complexity rationale
  • Countersigned Statement of Work
  • Milestone plan, synced into your workflow
What it produced in a real run
POST/projects/:id/estimate201
HIGH · ×1.5
{
"complexity": {
"tier": "HIGH"
"multiplier": 1.5
"score": 6
"drivers": [
"HIPAA compliance constraints detected"
"onprem deployment target"
"Real-time latency requirement"
"40 concurrent video streams"
]
}
"agents": 7
"deliveryDays": 11
"baselineWeeks": 31
"timeReductionPct": 95
"dueNowCents": 2292000
}
ChiefArchitect
Architecture, build & deployment

Takes the approved scope and ships the whole thing.

Designs the architecture, writes the code, integrates the systems it has to talk to, deploys to your infrastructure and proves it against the acceptance criteria, without a build team behind it.

Step 6Build & deploy
Responsibilities
  • Selects the reference architecture and writes the implementation
  • Generates repositories, infrastructure-as-code and CI/CD
  • Integrates the systems it has to read from and write to
  • Provisions the target: your cloud, your VPC, on-premise, or edge
  • Runs the acceptance suite and security scan before handover
Hands over
  • Architecture decision record
  • Source repositories and IaC
  • Deployed environment with rollback
  • Acceptance and security scan results
What it produced in a real run
POST/projects/:id/kickoff201
8 tasks queued
01architectProvision target environment
02architectGenerate repositories and IaC
03architectWire ingestion pipeline
04architectConfigure inference layer
05managerPublish milestone plan
06architectRun acceptance suite
07architectRun security scan
08relationsDeliver handover briefing
ChiefRelations
Post-deployment support & customer success

Knows the whole history, and answers for it after go-live.

Takes over at handover with the full record (the requirement, the contract, the architecture, every deployment) and stays the line your users talk to for the life of the system.

Step 7Run & support
Responsibilities
  • Owns the relationship from handover onward
  • Answers questions against the delivered system and its history
  • Triages incidents and escalates against the SLA
  • Reports health, usage and spend to the stakeholders who signed
  • Flags where the system has outgrown its scope, and raises a change order
Hands over
  • Support and incident history
  • Health, usage and spend reporting
  • Escalation and root-cause records
  • Change orders raised from real usage
What it produced in a real run
POST/webhooks/esign201
SOW-2SLB7KXY
{
"contract": "SOW-2SLB7KXY"
"envelopeId": "ENV-FHZA8W79"
"gate": {
"contractSigned": true
"paymentCleared": true
"canKickoff": true
}
"payment": {
"status": "SUCCEEDED"
"amountCents": 2292000
}
}

One project record. No gaps between them.

The scope ChiefManager priced is the scope ChiefArchitect builds and the contract ChiefRelations issues.