Velocity Tech Inc
The engagement

What actually happens,
week by week.

Three acts, roughly twelve weeks. You can stop at the end of any of them and keep everything produced so far.

WEEKS 1–2 Discovery

We start where the work happens.

Not in a workshop. We sit with the people doing the job — the agents answering the same ticket forty times a week, the clerk re-keying invoices into two systems. We count the volume, sample the hard cases, and ask what a wrong answer actually costs you.

More often than not, what arrives labelled as an AI problem turns out to be three process problems and one AI problem. Knowing which is which before you spend anything is the whole point of this phase.

What you get

  • Workflow map and volume baseline
  • Opportunities ranked by payoff and risk
  • Indicative cost and timeline per option
  • A written recommendation — including what to skip

Stop here and you keep the analysis. Some clients do, and go build it themselves. That's a fine outcome.

WEEKS 3–6 Prototype

We prove it on your data, not a sandbox.

Before we tune a single prompt, we build the evaluation set — a few hundred real questions with known-good answers, drawn from cases your team has already argued about. From that point on, "better" has a number attached to it instead of an opinion.

The prototype goes in front of the people who'd actually use it in week four, not week twelve. What comes back reshapes the scope more than any planning meeting ever has.

What you get

  • Working prototype on your real data
  • Evaluation set and baseline scores
  • Retrieval and grounding layer
  • An honest read on what it can't do yet

Stop here and you keep the prototype, the eval set and the source. All of it runs in your cloud.

WEEKS 7–12 Production

We make it safe to put in front of customers.

The distance between a convincing prototype and something you'd let a customer touch is guardrails, access control, PII handling, audit logging, cost and latency budgets, and a considered answer for when the model should decline to answer at all.

This is most of the engineering, and it's the part that gets skipped — which is why so much AI work stalls at the demo. Afterwards it either runs under our operation, or we hand it over with documentation and training and you own it outright. We'd rather you didn't need us.

What you get

  • Hardened, access-controlled deployment
  • Monitoring, budgets and drift alerts
  • Security review and operational runbook
  • Handover documentation and team training

Or keep going. We run it, watch the drift, and iterate as your data changes.

Start with discovery.

Two weeks, a written recommendation, and no obligation to carry on.