Extending X10
The Extensions We're Pitching
The specific AI capabilities we want to add to the X10 platform that already exists.
This is the actual plan for the team: a small, bounded set of extensions that bolt onto the X10 platform that already exists. Each one maps to a revenue capability — which is how the platform hours are justified by what they earn.
The extensions, and what each unlocks
| Extension | What it adds | Revenue it unlocks | Owner |
|---|---|---|---|
| Surface Claude | Expose the already-wired Claude integration in the portal flow | Turns the platform from "routes to humans" into "AI-assisted" | Andrew + Paul |
| REST-wrap specific tasks | Expose high-value configuration templates behind the X10 API broker | The AI-assisted delivery engagement | Paul |
| Health Assessment surface | Upload → sanitize → analyze → review → report, in the portal | The entry-point offer | Paul (surface) + Jacob (UX) |
| Deterministic sanitization | Redact PII/secrets/hostnames before any model | Clears customer security review | Paul (Vince reviews) |
| Consent flow | Explicit, logged consent | Unblocks Deloitte-class customers | Andrew + Paul |
| Background scheduling | Recurring analyses, not just on-demand | The subscription tier | Andrew + Paul |
Every row is an addition to the existing broker — not a change to the platform's foundation. That's why this is a weeks-to-months extension effort, not a rebuild.
Where they attach
Why this is the right, defensible technical work
The honest constraint
Two of these — explicit consent and the sanitization boundary — are not just features, they're the compliance answer. They gate enterprise revenue. See the compliance gate.