Use-case scope
We pick the one or two features with the clearest value, define what good looks like, and write the scope.
AI features inside a product you already have, in six to fourteen weeks, with evaluation and cost controls so the feature is trusted and affordable.
The buyer question this answers: We have a product. Can you add AI without breaking it?
Reference timings for a typical engagement. The written scope gives you the dates for yours.
We pick the one or two features with the clearest value, define what good looks like, and write the scope.
A labelled test set of real inputs and expected outputs, built with your team.
Retrieval, prompting, and integration into the product, with the score run on every change.
Injection defences, sensitive-data handling, refusal behaviour, caching, and per-feature cost budgets.
Gradual rollout with monitoring of accuracy, latency, and spend.
Fixes and tuning as real usage arrives.
Every build has risks. These are the ones we plan for on this kind of project, and what we do about each.
How we handle itThe evaluation set comes before the build, and the score is reported weekly. Nothing launches below the threshold you set.
How we handle itCost per request is estimated in scope, measured in build, and budgeted per feature with alerts.
How we handle itAnswers cite sources, the feature refuses when unsure, and the interface makes confidence visible.
One or two features with success criteria written down can be priced. Broader AI programmes suit a dedicated team.
No prices on this page. The scope phase ends with a written quote for your project.
It is built behind a feature flag with its own tests and rolled out gradually. Your existing paths do not change.
The one that scores best on your test set at an acceptable cost. The integration lets you swap models later.
You will know by week three, from the score, and we will know why. Sometimes the answer is better retrieval, sometimes a narrower feature, occasionally not doing it. We say so.
API terms that exclude training on your data, or models running in your own cloud. Sensitive fields are filtered before anything reaches a model.
We reply within one business day with how we would build it, what it would cost, and which engagement model fits.
A short form or an email. No deck required, and "not sure yet" is a fine answer.
Within one business day. Technical questions get technical answers, from the person who would build it.
Fixed price where the scope is defined. The document is yours whether or not you go ahead.