Menu

AI

Inference

A practical guide to understanding what inference means in AI and why it matters for product performance and cost.

What inference is, how it differs from training, and what product and design teams need to understand about its implications for speed, cost, and reliability.

5 min read

What it is

is the of using a trained to generate outputs: producing a response, completing a task, or making a prediction based on a given input.

Every time a user sends a message to an AI chatbot, asks an AI tool to summarise a document, or a generated image, that is in action.

is distinct from training. Training is the of building and improving the using data. Inference is the process of using the finished model.

From a product perspective, is almost always what matters day-to-day. Training happens once, or periodically when the is updated. Inference happens every time a user interacts with the .

has cost, , and implications that directly affect the user experience.

When to use it

Understand when considerations are practically relevant. They matter most when:

They matter less when:

You are estimating or managing the running costs of an AI feature
Response speed is a meaningful part of the user experience
You are designing for high-volume usage where cost and performance at scale matter
You are troubleshooting slow or inconsistent AI responses
You are in early exploration or prototyping and performance is not yet a concern

Key takeaway

Inference is the operational reality of AI products. Understanding it helps you design features that are fast, cost-effective, and reliable under real-world usage.

How it works

The basic mechanism

When a user sends an input to a language , the model it token by token, generating a probability distribution over possible next tokens and from it to produce a response.

This happens on powerful servers maintained by the provider. The cost and speed of depend on the size of the model, the length of the input and output, and the being used.

Longer inputs and outputs cost more and take longer. Smaller, more efficient are cheaper and faster but may produce lower-quality outputs.

What this means for designers and product teams

(the time between sending a and receiving a response) is a direct UX consideration. Long response times frustrate users and reduce the perceived value of AI features.

Streaming (where the 's output is displayed progressively as it is generated, rather than all at once after completion) can significantly improve the perceived of AI features even when total generation time is unchanged.

What to look for

Focus on:

Latency: whether response times are acceptable for the intended use case
Cost per interaction: whether inference costs are sustainable at projected usage volumes
Streaming: whether displaying responses progressively would improve perceived performance
Model selection: whether a smaller, faster model could deliver acceptable quality at lower cost
Error rates: how often inference fails or returns errors, and how those failures are handled

Where it goes wrong

Most issues come from: Ignoring costs until production scale reveals them as a problem is a common and expensive mistake.

No cost modelling before launch, leading to unexpected bills at scale
Latency only tested on fast connections and not representative of real user conditions
No streaming implementation, making response times feel longer than they are
Over-engineering with large, expensive models for tasks that a smaller model handles adequately

What you get from it

Understanding gives you:

A clearer picture of where AI running costs come from
Better criteria for balancing model quality against performance and cost
A basis for designing AI features that feel responsive and reliable
More informed conversations with engineers about performance optimisation

Key takeaway

Every AI response is an inference call. Designing around its cost, latency, and reliability is as important as designing the experience itself.

Get in touch

Every AI response carries a cost and a wait. We can help you understand what drives both, before they start shaping the product for you.

No guesswork. No assumptions. Just a clear view of what each response costs you.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is inference in AI?

Inference is the process of using a trained AI model to generate outputs: producing a response, completing a task, or making a prediction. It is what happens every time a user interacts with an AI feature.

How is inference different from training?

Training is the process of building the model using data. Inference is the process of using the finished model. Training is expensive, slow, and happens infrequently. Inference is what your product does constantly in production.

Why do AI responses sometimes take a long time?

Because generating a long response token by token takes time, and that time increases with the length of both the input and the output. Model size, infrastructure load, and network conditions also affect response speed. Streaming responses can make the experience feel faster by displaying output as it is generated.

How much does inference cost?

It varies significantly by model size, provider, and input and output length. Most providers charge per thousand tokens. Small, efficient models can cost a fraction of a penny per interaction. Large, complex models with long inputs and outputs can cost several cents per interaction, which adds up quickly at scale.

Can inference speed be improved?

Yes, through several approaches: using smaller models where quality requirements allow, caching common responses, optimising prompt length, and choosing providers with lower-latency infrastructure. Streaming responses also improves perceived speed without changing actual generation time.

Quick take

Inference is what happens every time an AI generates a response, and understanding it helps you design better AI features and have more informed conversations about performance and cost.

Related Services

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer