Agrus
PROCESSFour stages

Scope. Sprint. Build. Operate.

Most consulting engagements obscure the math. Here's ours, in four stages, with the decision point at each one.

01
Day 0

Scope

30-minute call with an engineer and our compliance lead. You describe the problem; we describe the shape of the engagement we'd recommend, in writing, within 24h.

Decision
Go / no-go on Discovery Sprint.
02
Week 1–3

Discovery Sprint

Fixed price, fixed scope. We produce: working prototype, architecture document, compliance map your CISO signs, model-selection rationale, cost model. You can stop here and take the artifacts elsewhere.

Decision
Sign-off on production build, or stop with sprint artifacts.
03
Week 4–20

Build

T&M engagement, 4-16 weeks typical. Production-grade deployment, monitoring, eval pipeline. Bi-weekly demos. We don't disappear — your team is in the loop from day one.

Decision
Production release sign-off.
04
Ongoing

Operate

Optional Managed SLA: 24/7 on-call, model upgrade testing, drift monitoring, quarterly eval. Or full handover to your team — we document everything as we go.

Decision
Renew annually, or hand over completely.
What you keep

IP ownership is yours from day one.

The architecture document, the compliance map, the deployment code, the eval pipeline — all yours. We use open-source tooling and your existing infrastructure. Nothing locks you in to us.

The Ethora license is optional; many engagements use it because it fits the shape, and it stays with you if you leave the engagement.

We've had customers complete a Discovery Sprint, take the artifacts, and build the production system themselves. That's a valid outcome. We'd rather earn the build engagement than be owed it.

Start with a scoping call.