Who this is for

You have agents in front of customers, or about to be

Something works well enough to demo. Now you need it to survive real traffic, real edge cases, a real security review, and a cost line your CFO will actually approve.

Typically:

Series A through mid-market, an engineering team of 10 to 150, and a CTO or VP of Engineering who knows what is missing but doesn't have anyone who has run this at scale before.

The problem

Building an agent is a weekend. Running one is a different job.

The failures are almost never in the prompt. They're in the parts nobody builds until the incident happens:

Every one of these is solvable. Most teams discover them in the order listed above, one incident at a time.

Offer

AI Production Readiness Assessment

Fixed Fee $25,000 |  Four weeks

I go through your agent systems the way an SRE goes through a service before it gets an SLA.

Weeks 1 & 2

Architecture review, code and infrastructure walkthrough, interviews with the engineers who own it. I map every tool call, every side effect, every place state is held, and every path a failure can take.

Weeks 3 & 4

Failure mode analysis against production conditions: concurrency, retries, partial failures, hostile inputs, cost under load, and multi-tenant boundaries.

What you get

  • A findings document, ranked by severity, written for engineers rather than for a slide review
  • A remediation plan with effort estimates your team can execute against
  • A reference architecture for missing pieces: eval harness, observability/tracing, cost controls, approval gates, tenant isolation, durable orchestration
  • A working session with your engineering team to hand it over

If the assessment finds that you're in better shape than you thought, that's a real outcome — and you get it in writing.

What usually happens next

Most teams can execute the plan themselves. Some want the person who wrote it to own the remediation and stay on through it. That runs as a fractional engagement, one or two days a week, on a monthly retainer. We'd scope that after the assessment, not before.

Who you'd be working with

Direct access, not a bench

Arulraja Livingston. I built and ran Platform Engineering at OutSystems from zero to a 140-person organization inside a 500-person engineering group, carrying a 99.95% contractual SLA across EMEA, AMER, and APAC. I built an AI-native development framework there that 80% of the engineering organization adopted, well beyond my own reporting line. Before that, CTO at Cloud49 and Cocolevio, and senior architecture roles at IBM and Dell.

I'm currently building a production-grade agent orchestration platform, which means the failure modes on this page are ones I'm designing against every day, not ones I read about.

You work with me directly. No bench, no handoff to a junior team.

Platform Engineering: 0 → 140 people at OutSystems
99.95% contractual SLA — EMEA, AMER, APAC
AI-native dev framework adopted by 80% of engineering
Direct engagement — no bench, no handoff

Start here

A 30-minute call. Bring the system you're worried about. You'll get a straight answer on whether the assessment is worth it for you — including when it's not.

Book a call Contact via email