How we engage

4

Phases against a Statement of Work. The same shape, every engagement. No retainers, no scope drift, no agile cover for missing milestones.

Pricing is transparent, we share ranges on the qualifying call and lock specifics in the SOW.

  1. 01

    Discovery

    2 weeks
  2. 02

    Architecture

    4 weeks
  3. 03

    Build

    12–24 weeks
  4. 04

    Operate

    Ongoing, 6 to 12-month contracts
01

Discovery

2 weeks

Fixed-fee, paid up front, non-refundable

Operations audit, stack mapping, opportunity sizing. Two weeks inside your operation with the people doing the work.

What we do

  • Sit with the operating team for 4–6 hours total across the engagement
  • Map every workflow, system, and decision point in scope
  • Quantify where AI + HITL meaningfully changes throughput or accuracy
  • Draft a thin architecture and identify integration risks

What you commit

  • Read access to relevant systems
  • 4–6 hours of operating-team time, not just executive sponsors
  • Honest answers about what is broken, political, and previously tried

Deliverables

  • Opportunity map ranked by impact, with sized lift bands
  • Stack inventory + integration feasibility ratings
  • Recommended Architecture phase scope, or honest "we are not the right fit"

Sample artifacts

  • 6–10 page opportunity map document
  • One-page stack diagram
  • 90-minute readout with the operating team (recordable)
02

Architecture

4 weeks

Fixed-fee, paid 50% up front / 50% on delivery

Solution design, HITL touchpoints, integration plan, and a Statement of Work for the Build phase.

What we do

  • Design the system end-to-end with explicit human-in-the-loop touchpoints
  • Draft data flow, model selection, and approval surfaces
  • Build a thin prototype on representative data to de-risk assumptions
  • Produce a Build-phase SOW with named milestones and acceptance criteria

What you commit

  • Decision-makers in design reviews (not just delegates)
  • Sign-off on HITL touchpoints and risk model
  • Procurement aligned for Build phase kick-off

Deliverables

  • Architecture document with HITL surfaces named
  • Working prototype on a representative dataset
  • Statement of Work for the Build phase, fixed-scope, milestone-billed

Sample artifacts

  • Architecture document (typically 15–25 pages, technical)
  • Prototype walkthrough recording
  • Build-phase SOW with milestone schedule
03

Build

12–24 weeks

Milestone-billed against the SOW

Implementation, integration, and deployment to production against the Architecture phase SOW.

What we do

  • Ship the system against the Architecture SOW, milestone by milestone
  • Integrate with systems of record on read and write paths
  • Stand up monitoring, audit logs, and the operator review console
  • Run UAT with the operating cohort that will use the system daily

What you commit

  • A named operations counterpart, ~30% allocation through Build
  • UAT cohort drawn from people who will use the system daily
  • Production access on the agreed schedule

Deliverables

  • Production system in your VPC or ours, your call
  • Operator console with full HITL review surfaces
  • Runbook + incident playbook
  • Audit log queryable from day one

Sample artifacts

  • Bi-weekly milestone demos with the operating team
  • Production deployment runbook
  • Monitoring + alerting set up against your channels
04

Operate

Ongoing, 6 to 12-month contracts

Monthly, with annual roadmap review

Tuning, monitoring, and expansion. The phase where AI either keeps earning its keep or it does not.

What we do

  • Monitor accuracy, latency, and human override rates weekly
  • Tune models, prompts, and approval thresholds as the operation evolves
  • Run a working forum with the operating team on a fixed cadence
  • Expand scope when foundations are earning their keep

What you commit

  • A working forum (weekly or biweekly) with the operating team
  • Visibility on metric targets and override rates
  • Annual roadmap review

Deliverables

  • Monthly operating report (metrics, drift, override audit)
  • Quarterly roadmap update
  • On-call coverage to your SLA

Sample artifacts

  • Monthly report (5–10 pages, metric-driven)
  • Quarterly roadmap document
  • Operate-cadence Slack or Teams channel for the working forum

What it costs

Rough order of magnitude.

PhaseDurationShapeOrder of magnitude
Discovery2 weeksFixed-fee, up frontlow five figures
Architecture4 weeksFixed-fee, 50/50mid five figures
Build12–24 weeksMilestone-billedsix figures and up
OperateOngoingMonthly retainerlow five figures / mo

Hiding pricing wastes everyone's time. Specific quotes come from the qualifying call once we know the operation. We will not under-promise to win the engagement.

Frequently asked

Questions procurement asks first.

Why fixed-fee on Discovery and Architecture, but milestone on Build?

Discovery and Architecture are scope we control, we know how much work it is. Build is scope you control via the SOW we agree on at the end of Architecture. Milestone billing keeps incentives aligned: we get paid for shipping, not for time on a clock.

What does it actually cost?

Discovery and Architecture are fixed-fee, we share ranges on the qualifying call. Build pricing comes from the Architecture SOW and depends on scope. Operate is monthly. We do not hide pricing; we share it once we have enough context to quote honestly. As a rough order: Discovery is in the low five figures, Architecture is in the mid five figures, Build runs six figures and up, Operate is a monthly retainer in the low five figures.

Do you take equity?

No. Cash only. Equity contracts complicate operating relationships and we want the right to walk away if a fit fails.

What happens if Build runs late?

We eat it. Build is fixed-scope, milestone-billed against the SOW. If we miss a milestone, we keep working without billing the next milestone until it ships. We have not had to invoke this in practice, but it is the contract.

Can we hire you for just Operate, on a system someone else built?

Sometimes. We need a shortened Discovery first to assess the system and the operating context, and a clear handoff from whoever built it. We say no often enough that the asking is worth it.

Will you sign our MSA, our SOC 2 questionnaire, our DPA?

Yes, within reason. We work to standard procurement processes, sign a DPA when GDPR or CCPA applies, and complete vendor security questionnaires as part of the engagement. We will push back on terms that fundamentally conflict with how we deliver.

Where is the data?

Your call. We can deploy in your VPC (preferred when data residency or compliance posture matters) or in ours (faster to stand up). Either way, your data stays your data, no training on client data, no cross-engagement reuse.

Will you talk to our existing vendor / SI partner?

Yes. We integrate against the systems they manage every engagement. We do not compete with implementation partners on the platform layer, we sit on top.

Talk to us

Start with a 30-minute qualifying call.

We'll walk through the operation you're thinking about, share rough numbers, and either schedule Discovery or be honest about why we shouldn't.