You do not need to rebuild your product to add AI. Most useful AI features are a new part bolted onto software that already works: a search box that understands questions, a form that accepts a sentence instead of ten fields, or a background job that reads documents. This guide walks through how we add AI to existing products, including our own.
Step 1: pick one feature that removes a real task
Start from a task your users or staff repeat, not from the technology. Good first features share three traits: high volume, a clear right answer, and a cheap way to recover when the AI is wrong.
- Natural-language input: let people type what they want instead of filling a form.
- Search that answers questions from your help pages, policies, or product data.
- Document reading: pull fields out of PDFs, invoices, or emails.
- Summaries of long records, tickets, calls, or transcripts.
- A chat assistant that can look things up and take simple actions for the user.
Step 2: connect a model behind your own API
Your app should call your own server, and your server should call the AI provider. That keeps API keys secret, lets you add limits and logging in one place, and means you can switch between providers such as Anthropic, OpenAI, or Google without touching the front end.
Step 3: ground it in your own data
A model on its own only knows what it learned in training. To answer about your products, customers, or policies, you pass in the relevant information with each request. For larger collections of documents, that means indexing them so the right passages can be found and included, a technique usually called retrieval-augmented generation, or RAG.
Step 4: design for the answer being wrong
- Show AI output as a draft the user confirms, not a final action.
- Validate structured output before saving it, and fall back to a person when it fails.
- Never let the model do arithmetic or make decisions that need an audit trail on its own.
- Keep a set of real test examples and run them whenever you change the prompt or model.
Step 5: control cost and speed
- Use the smallest model that does the job well, and save larger models for hard cases.
- Cache answers to repeated questions.
- Stream long responses so users see text immediately.
- Set spending limits and per-user rate limits before launch.
Step 6: handle privacy properly
Use business API tiers that do not train on your data, send only the fields a feature needs, and update your privacy notice to name the providers involved. For UK businesses, record the processing in your UK GDPR records like any other supplier.
Step 7: release it gradually
Turn the feature on for a small group first, watch the logs and feedback, fix what goes wrong, and then widen it. AI features improve fastest from real use, so an early, limited launch beats a long private build.
Making your product usable by AI agents
The other side of adding AI is letting AI assistants use your product. Publishing an MCP endpoint, the open standard for giving AI agents tools, lets assistants call your app on a user's behalf. We added one to PivotBank so AI assistants can convert bank statements directly.