Project scope
AI Development Cost: How to Scope a Useful First Release
Understand AI project cost drivers, discovery inputs, evaluation work and ongoing expenses before requesting a development quote.
Summary
- Key takeaways
- Start with one workflow
- The main cost drivers
- Budget for evaluation, not just a demonstration
- Separate build costs from operating costs
- Compare proposals on the same assumptions
- The exact first-release workflow and what is outside scope
- Required data preparation and who provides source access
- Integrations, permissions and consequential-action approvals
- Evaluation examples and agreed acceptance criteria
- Deployment, account ownership and handover deliverables
- Recurring costs, support coverage and change-request handling
- A discovery brief you can prepare today
- Questions buyers ask
- How SmartWeb AI Labs can help
- A note on what this guide is
Key takeaways
- An AI project estimate is useful only when it describes the workflow, data, integrations and acceptance criteria.
- Separate development costs from the cost of running the system, and compare proposals on the same scope.
Start with one workflow
Describe what a person does today, which information they use and what a successful outcome looks like. “Add AI to our business” leaves too many choices open. “Find the relevant policy and prepare a cited draft response for a support specialist” is a workflow that can be evaluated.
Choose a first release that is complete enough to use but limited enough to test. A focused knowledge assistant and an agent that changes records across several systems have different development and operational requirements.
When that first release is a tool-using agent, how much an AI agent costs to build covers the actions, permissions and running costs that change the estimate. This page remains the general guide for comparing any AI project.
The main cost drivers
| Driver | What changes the work | What to bring to discovery |
|---|---|---|
| Data preparation | Inconsistent files, missing metadata and document permissions | Representative files and an explanation of who may access them |
| Integrations | API access, authentication, rate limits and write operations | System names, API documentation and available test accounts |
| User experience | Internal tool versus customer-facing product; roles and approvals | User types and the intended journey |
| Evaluation | Task variety, consequences of errors and required human review | Real examples of successful and unacceptable outputs |
| Operations | Usage, monitoring, deployment and support expectations | Expected users, hosting constraints and support requirements |
Budget for evaluation, not just a demonstration
A demonstration can show a model answering a few selected questions. A production workflow also needs to handle missing information, conflicting sources, denied access and external system failures. Include test examples that reflect those conditions.
Agree how the result will be assessed: source accuracy, task completion, unacceptable actions, response time or another measure relevant to the workflow. The assessment method should be defined before the team declares the prototype ready.
Separate build costs from operating costs
Ask which accounts belong to your business, who can view usage and how budgets or limits will be set. Clarify whether maintenance and incident response are included or quoted separately. A low initial build estimate can omit work that becomes necessary immediately after launch.
Compare proposals on the same assumptions
1The exact first-release workflow and what is outside scope
2Required data preparation and who provides source access
3Integrations, permissions and consequential-action approvals
4Evaluation examples and agreed acceptance criteria
5Deployment, account ownership and handover deliverables
6Recurring costs, support coverage and change-request handling
A discovery brief you can prepare today
Write a short description of the business problem, the current process and the intended users. Add representative documents or inputs without sending confidential material through a public enquiry form. List the systems to connect and identify any deadline or hosting constraint.
Questions buyers ask
These answers explain how to read an estimate. They are not a price list, a statistic or a client result.
Does this guide give a price for an AI project?
No. It lists the inputs that change an estimate: workflow, data, integrations, evaluation and operating costs. A figure comes from a project-specific proposal after those inputs are discussed.
How is this different from the AI agent cost guide?
This page is for any AI project, including a feature inside an application. The AI agent cost guide applies only when the first release is a tool-using agent. Use that page for actions, permissions and running costs of an agent.
What should we bring to a discovery discussion?
Bring the workflow, the intended users, the systems to connect and what is outside the first release. Representative inputs are useful. Do not send confidential records through the public form.
Are running costs part of the build estimate?
They should be discussed separately from the build: model usage, hosting, storage, monitoring and support. A build figure that ignores them does not describe the cost of keeping the system available.
Can a prototype price stand in for the full project?
A prototype can be scoped on its own. It does not include production evaluation, permissions, deployment and handover unless the proposal says so. Ask which of those are in the figure you are comparing.
How SmartWeb AI Labs can help
AI Software Development
A generative AI software agency for teams in the US, UK and Europe. Choose one AI feature, chatbot or agent, then scope a first release.
Explore this serviceAI Agents & Workflow Automation
AI agents for business workflows, with approved tools, human review and clear limits. Built remotely for teams in the US, UK and Europe.
Explore this serviceA note on what this guide is
This guide explains a decision. It is not a quotation, a client result, or a delivery date. A written proposal comes after the workflow is discussed.