What an AI feature actually costs to run
How to work out the monthly bill for an AI feature before you build it, which factor dominates the cost, and the four changes that reliably cut it.
AI development
Vuewer builds AI features into existing web applications: retrieval-augmented search, document extraction, generation inside real workflows, and multi-step agents. We work in Laravel and PHP with OpenAI and Anthropic models, ship a first production feature in three to six weeks, and set cost, latency and accuracy budgets before writing code.
What we build
Every one of these is in production somewhere. None of them is a chatbot in the corner of a homepage.
01 AI features
Not a chatbot bolted onto the corner of your site. Features that use your own data and do real work, added to software that already works.
Retrieval over your documents, products and history, so answers cite something real.
Generation and summarisation where your users already are, not in a separate tab.
Documents, email and forms turned into data your systems can act on.
A test set from day one, so you know when the model is wrong before your customers do.
Cost per request and response time agreed before we build, not discovered after.
02 Agents & automation
The repetitive work your team does by hand, handed to something that does not get bored.
Real tasks completed end to end, with a human approval step where the stakes justify it.
The systems you already pay for, wired together properly instead of by copy and paste.
Work that starts because something happened, not because someone remembered.
Every action logged, so you can answer what happened and why.
Your team's own AI tools given safe, scoped access to your systems.
What you get
Not optional extras. An AI feature without an eval set is a feature nobody can prove works.
When not to
We turn work down for these reasons, and saying so up front saves everyone a wasted month.
FAQ
Field notes
How to work out the monthly bill for an AI feature before you build it, which factor dominates the cost, and the four changes that reliably cut it.
Retrieval teaches a model what you know; fine-tuning teaches it how to behave. Most features need the first, a few need both, almost none only the second.
A sequence for putting an AI feature into an application that already has users: pick a job, ground it in your data, set budgets, and ship behind a flag.
Get in touch
Do you have a question or need help with a website or web application? Whether you are starting from scratch, refining what you already have, or stuck on something complex.
Fill in the form and we'll get back to you as soon as possible.