Route to Terraform
One Function — 'Generate customer invoice' — across all six rungs of the adoption ladder. 21 months, 5 decision records, 2 emergent roles, 6 → 0 specialists, 18 → 0 days cycle time. Click each rung to walk through what changed and why.
Generate customer invoice
Roll up a customer's shipments for the month into a single invoice. Apply the right rate cards, surcharges, and contracted discounts. Reconcile with payments.
Six specialists, eighteen-day cycle, four percent errors
This is where Helios started. Billing specialists pulled shipment data out of the TMS, applied rate cards by hand in spreadsheets, drafted invoices in DocuFlow, and emailed them. End-of-month was a sprint; mid-month was preparation for the sprint.
6 Billing Specialists (4 senior, 2 junior). Stable team; high turnover risk in juniors due to the repetitive nature of the work.
Shipment-manifest quality was already flagged as a constraint on any future automation.
“We knew billing was eating the team. The question was whether we'd get more value from making the team better at it, or from making the work itself smaller.”
Drafting copilot lands; specialists spend less time typing
An AI copilot drafts each invoice from the shipment manifest. The specialist still reviews every line, applies any non-standard adjustments, and presses Send. Human is firmly in the driver's seat. The copilot writes maybe 70% of the words.
- End-to-end automation (autonomous) — Too aggressive for a first move. Workforce impact unclear; data quality unproven.
- Templating-only (no AI) — Wouldn't move the needle on cycle time. Past attempts had stalled.
No role changes. All 6 specialists trained on the copilot UI in two half-day sessions. New skill added to their profiles: 'AI-assisted drafting'.
Passed first-time. Specialists actively asked for the copilot to be expanded.
“The first version was honestly nothing fancy. But once the team saw the AI didn't make them dumber, they got curious. That curiosity was worth more than the four-day cycle-time win.”
Multi-doc reasoning takes the bulk; humans handle exceptions
The agent now reads shipment manifests, rate cards, contract addenda, and prior disputes — produces the invoice, including all line items, surcharges, and adjustments. The specialist no longer 'reviews every line' — they review summaries and exceptions only. Routine invoices flow through untouched.
- Stay at assisted, do data-quality work first — Would have been the safer call. CFO chose the more ambitious path because the team was confident.
1 junior specialist position not back-filled after natural attrition. Team is now 5 — two seniors developed deeper exception-triage muscle.
- Exception Triager (Billing) — predicted, not yet promoted
Marginal on correctness because rate-card refresh lag caused 4% of invoices to use stale prices in the first two weeks. Mitigated with a freshness-check + auto-pause.
Resolution:Added a freshness-check at invoice generation; if rate-card timestamp older than 72h, auto-pause and notify Tom. AdoptionState briefly auto-demoted to assisted; restored after fix.
“The marginal assessment was the most useful thing that happened that quarter. It was a real signal, the platform forced us to address it, and the rate-card freshness fix paid off everywhere — not just in billing.”
Self-disputing flow — agent handles reconciliation, humans approve outliers
The agent doesn't just generate the invoice — it watches the customer's payment flow, reconciles automatically, and opens dispute drafts itself when something looks wrong. The specialist now approves outliers only: cases where the agent flagged uncertainty or where customer-facing language matters.
- Build a separate dispute-only agent — Would have created a seam that loses context. Better to extend the existing agent's remit.
- Outsource disputes to a BPO — Considered briefly; would have killed the workforce-evolution story.
2 specialists transitioned to a new emergent role: Customer Outcome Steward. They own the customer-facing language, edge cases, and the agent's training feedback loop.
- Noah Kowalski · Billing Specialist → Customer Outcome Steward · completed
- Ines Marchetti · Billing Specialist → Customer Outcome Steward · completed
- Customer Outcome Steward — approved, filled
First-time pass. Drift thresholds set tighter than usual due to customer-facing exposure.
Resolution:Customer Outcome Steward feedback loop caught it; brand-voice policy added to evals; no AdoptionState demotion required.
“When Noah and Ines became Customer Outcome Stewards, the disputes weren't a back-office cost any more — they were an outcome lever. That changed who they were in the org, in a good way.”
End-to-end agent with attestation cadence; humans on the loop
The agent owns the entire billing-to-collection cycle. Tom Whitfield stopped reviewing invoices and disputes individually — he now signs a quarterly attestation that the agent's pattern of behaviour is within policy, supported by the platform's continuous evidence pack. Auto-fallback to supervised mode kicks in if drift trips a threshold.
- Stay at supervised-autonomous, tune further — Diminishing returns. The supervision overhead was costing more than the residual risk.
Tom Whitfield transitioned from Head of Billing to Agent Steward (Billing). His direct reports dropped from 4 to 2 (the two Outcome Stewards). The Billing OrgUnit was flagged as a candidate for terraforming in the next planning cycle.
- Tom Whitfield · Head of Billing → Agent Steward (Billing) · completed
- Agent Steward (Billing) — approved, filled
Continuous evidence pack; quarterly re-attestation. First attestation due 2026-Q3.
“I went from running a team that processes invoices to running an agent that processes invoices. Same outcome ownership, much less middle-management. I'd rather be a Steward.”
Continuous reconciliation — invoicing dissolves into real-time settlement
The Function 'Generate customer invoice' stops being a thing. Instead of monthly invoices, Helios moves customers to a real-time settlement model: every shipment settles against contract terms as it completes. 'Billing' as an OrgUnit dissolves; the work merges into Treasury (cash flow) and Customer Success (commercial relationship). The agent doesn't 'invoice' — it maintains a continuously reconciled position.
- Stay at autonomous, refine further — Hits the ceiling. The Function as conceived can't get faster than 'real time' which is what we'd be approaching anyway.
- Roll out continuous reconciliation only to top 5 customers, keep monthly for everyone else — Considered. May be the staged delivery path within the chosen scenario. Decision deferred to plan kickoff.
Billing OrgUnit (current headcount 3) dissolves over 9 months. Tom remains Agent Steward but for the new continuous-reconciliation function. Outcome Stewards merge into Customer Success. 1 specialist will need a substantive transition pathway — current candidate destinations: Treasury Analyst (emergent) or CS Operations.
- Tom Whitfield · Agent Steward (Billing) → Agent Steward (Settlement) · draft
- Customer Outcome Stewards · Billing-attached → Customer Success · draft
- 1 remaining Specialist · Billing Specialist → Treasury Analyst (emergent) · draft
- Treasury Analyst (settlement-aware) — predicted, not yet proposed
- Settlement Steward — predicted
Marginal because: contract renegotiation is the binding constraint, not the technology. Workforce-intent marginal because the dissolution of Billing OrgUnit is large change for 3 people. Regulatory marginal because real-time settlement crosses revenue-recognition lines that need finance/audit sign-off.
“Terraform isn't 'more autonomy.' It's the moment you realise the question you were optimising was the wrong question. We don't need a faster invoice — we need to stop having invoices.”
From 6 specialists & 18-day cycles to a continuously-reconciled customer position
Six rungs. Twenty-one months. Five signed decision records. Two emergent roles created and filled. Two drift events caught and resolved. The Function being optimised stopped existing — replaced with a new one that's native to autonomous agents.