“How much does AI cost” has no single answer because most of the cost is not the AI. Here is how the numbers actually break down.
The three cost buckets
Tool subscriptions. Language model access, automation platforms, connectors. For a small business this is often tens to low hundreds per month. Not the expensive part.
Building and connecting the system. Designing the process, connecting the tools that hold the data, setting boundaries, testing. This is the main cost, and it scales with how much the process needs to change, not with the AI.
Running and supervision. Usage charges at volume, plus the time a person spends reviewing output and handling exceptions. Lower than a salary for the same work, but not zero.
What makes a project expensive
- Messy or scattered source data that needs cleanup first.
- Many systems to integrate, some without good ways to connect.
- A process nobody has mapped, so design takes longer.
- Loose boundaries, where a wrong answer has a real cost.
How to size it
Put a number on the constraint. If a process costs the team 15 to 20 hours a week, or if slow follow-up is losing a measurable share of leads, the value is clear and the budget follows from it. If you cannot quantify the constraint, that is the first thing to fix, and it is cheap to do.
How XP Labs approaches it
XP Labs sizes the opportunity in time or revenue before proposing anything, and the first build is deliberately small and focused on the highest-value part. The planning conversation produces that first estimate. Read an AI adoption roadmap for SMBs and the AI growth overview.