Your analytics preferences

With your permission, we use optional analytics to understand website visits and improve our services. You can change your choice in the footer at any time.

Fixed-scope package

From AI pilot to production

Your pilot demos beautifully. Production kills it.

Duration
1–2 weeks assessment; 4–10 weeks hardening
Format
Assessment, then hardening sprints
Pricing
$2,500–$5,000 assessment; $12,000–$45,000 hardening
Best for
Teams with an existing working AI pilot

Fixed-scope package

Move beyond the demo.

Somewhere in your company there's an AI pilot that impressed everyone in the room and never shipped. The model answers questions. The demo works. But it isn't connected to anything real, nobody can tell you what it costs at scale, and the person who built it has moved on. We take pilots like that to production.

This is a fixed-scope package. We look at what you have, we harden it, we launch it, we hand it over.

How the parts of the system connect

01The work

Why pilots stall

01

Nobody measured it.

The pilot answered questions in a demo. Nobody wrote down what "correct" means, so nobody can say whether the production version is working or drifting.

02

It isn't connected to anything.

The demo ran on sample data. Your CRM, your tickets, your documents live somewhere else, and nobody scoped the plumbing.

03

The bill surprised everyone.

A demo makes a few hundred calls. Production makes a few hundred thousand. Nobody set budgets, quotas, or routing, so finance killed it.

04

Nobody owns it.

The pilot was a side project, a hackathon entry, an intern's summer. When the demo ended, so did the maintenance.

05

It can't be audited.

No logs worth reading, no access rules, no record of what the model saw and did. Security said no. Rightly.

02The work

The production checklist

This is what "hardening" means, concretely. Every pilot we take on gets all five.

01

Evals with graded answers.

A set of real questions, graded right or wrong, run before every change. If a tweak makes answers worse, you know before your users do.

02

Connected to your systems.

CRM, ERP, ticketing, documents. Through APIs, with the same permissions your people already have.

03

Cost control.

Model routing, caching, quotas, budgets with alerts. You should know what 10x usage costs before it happens, not after.

04

Monitoring someone checks.

Logs, traces, and a dashboard with a name attached to it. When the system misbehaves at 2am, someone gets woken up instead of being surprised on Monday.

05

Governance.

Access rules, PII handling, an audit trail of what the system saw and did. The things your security team asks for before they'll sign off.

03The work

The package

01

First, the assessment.

We read the pilot's code, run it against your real data, and grade it. You get a written verdict: what's salvageable, what needs rebuilding, and what it will take. If the honest answer is "start over," we say so in the assessment, and you only pay for the assessment.

02

Then, hardening sprints.

We work through the production checklist above. Two-week sprints with demos, the way we run everything. You watch the pilot turn into a system.

03

Then, launch and handover.

It goes live for real users, with monitoring in place. Then we hand it over: code, docs, runbooks, and a walkthrough for your team. You own 100% of it.

$2,500 – $5,000, credited toward the build if you proceed. The assessment is a fixed price on its own, so you know the cost of the verdict before you pay for the cure.

04The work

Is it right for you?

01

Good fit:

you have a working pilot that impressed people and never shipped. The demo runs. The use case is real. What's missing is everything around it.

02

Bad fit:

you don't have a pilot yet. Start with AI Discovery, our 3-week fixed-fee package that finds the use cases worth building. See AI Discovery

03

Also bad fit:

your pilot was a slide deck. There's nothing to harden.

05FAQ

Frequently asked questions

View pricing guide
How do you judge whether our pilot is salvageable?

We read the code, run it against your real data, and grade the answers. Then we tell you in writing what's worth keeping and what isn't. Sometimes the verdict is that the demo was theater and a rebuild is cheaper. You get that answer either way.

How long does it take?

The assessment takes 1–2 weeks. Hardening typically runs 4–10 weeks, depending on how many systems it needs to connect to and how much of the pilot survives the assessment. We give you a scoped timeline after the assessment, never before.

What does it cost?

$12,000 – $45,000, fixed fee, scoped after the assessment. The assessment itself is a fixed $2,500–$5,000, so the verdict costs you a known amount even if you walk away afterward.

We built the pilot in-house. Will you work with our team?

Yes. We pair with your engineers during hardening, and the handover includes walkthroughs so your team can run the system after we leave. The goal is something your team owns, not a dependency on us.

What does "production-ready" actually mean?

Five things: graded evals that run on every change, integrations with your real systems, cost controls with budgets, monitoring someone checks, and governance your security team will sign. If any one of those is missing, it isn't production.

What if the pilot was built on the wrong architecture?

Then we say so in the assessment. Sometimes the demo stack can be hardened. Sometimes rebuilding on the right stack costs less than patching the wrong one. We'd rather tell you that in the assessment than discover it months in.

Who maintains it after launch?

Your team does, with our handover pack: code, docs, runbooks, and the eval suite they can keep running. If you'd rather we stay involved, we offer managed evolution as an ongoing engagement. Either way, you own everything.

AI readiness

Not sure where you stand?

Ten questions, about three minutes. Find out what needs attention before you build.

Plan the work

Book a scope call.

Forty-five minutes. Bring the pilot, or just the story of how it stalled. We'll tell you whether it's salvageable before you spend anything serious. A solutions architect replies within one business day.