Your client does not want a separate AI tool. They want the app you built last year to draft the reply, summarize the thread, pull the fields off the invoice and file it in the right place. That is usually a sprint, not a rebuild.
Scope this with us“Could the system just write the first draft so my team is only editing?”
Two to four discrete features fit comfortably in one 14-day sprint, assuming we are working inside an existing, running codebase.
Built in your repo, in your framework, matching the patterns your team already uses — not bolted on as a separate service.
Token streaming, optimistic states and graceful loading, because a 6-second blank spinner reads as broken.
Extraction and classification return typed, schema-checked data your app can rely on rather than free text you have to parse.
Per-tenant limits and cost visibility, so your client's bill cannot surprise either of you in month two.
Yes — that is the common case. We work in your repo, follow your conventions and open PRs your team reviews. If your stack is unusual we will tell you on the call whether we are a fit.
We pick per feature based on cost, latency and quality, and keep the provider behind an interface so switching later is a config change rather than a rewrite.
We give you real per-run cost numbers from the build, so you can price with a margin instead of guessing and absorbing the difference.
Bring the scope you’re unsure about — an RFP, a client request, a half-quoted project. We’ll tell you what’s buildable, what it takes, and whether it fits in one sprint. No charge for the call.