The case studies you read about artificial intelligence (AI) — the ones with the dashboards, the percentage gains, the executive quote — are almost always written about companies with full data teams and seven-figure budgets. The version that lands on the desk of a 40-person Denver firm looks nothing like that. The model is the easy part. The expensive part is everything around it.
AI here means the practical kind a small or mid-sized business (SMB) actually buys: software that reads documents, drafts text, forecasts numbers, or moves data between systems without a person retyping it. This post is about the everything-around-it — where these projects break, what the budget really looks like, and the few patterns that hold up after the launch applause dies down.
Why this matters before you sign anything
The reason AI projects stall is rarely the technology. The industry’s own benchmark, the State of AI in Business report from MIT’s Project NANDA, found that the large majority of enterprise generative-AI pilots never reach production or produce measurable return. At SMB scale the math is harsher: you do not have a data team to absorb the cleanup, and a six-month dead-end costs a bigger share of your year. Knowing the three failure modes up front is the cheapest insurance you can buy.
Where SMB AI projects actually fail
Three failure modes account for most of what we see, and none of them are about the algorithm.
Data the team doesn’t trust. Most SMBs have data in three or four systems that disagree with each other — QuickBooks says one revenue number, the customer relationship management (CRM) system says another, the spreadsheet on the controller’s desktop says a third. Vendor and analyst estimates routinely put data preparation at well over half of an AI project’s effort; in smaller shops it runs higher, because the cleanup has never been done before. A model trained on dirty data produces confident wrong answers, which is worse than no model at all.
No one owns the change. A pilot that produces a useful weekly report is not a project until someone’s job changes to use it. We routinely see pilots prove value, get a round of applause, and then quietly die because the controller’s month-end close still runs the old way. The technical deployment is the cheap half; the workflow change is the expensive half.
Recurring cost gets discovered after launch. The license fee is the line item people plan for. Inference cost (what you pay each time the model runs), retraining, monitoring, the contractor who reviews outputs once a quarter, the storage growth — these are not optional and they do not show up on a vendor pricing page. Budget for them on day one.
Get the data ready first
Because data is the failure mode that sinks the most projects, it is also the one to fix first — and it is fixable without buying any AI at all. Before a pilot starts, you want:
- One agreed source of truth per number. If revenue, headcount, or inventory can be answered three ways, decide which system wins before a model reads any of them.
- A clean export path. The data has to leave QuickBooks, the CRM, or the warehouse in a structured form on a schedule — not as a screenshot someone emails.
- Definitions written down. “Active customer” and “completed job” mean different things to different people. Pin them before the model encodes the wrong one.
This is unglamorous plumbing, and it is exactly the work that determines whether the AI on top of it is trustworthy. It is also work that pays off even if you never run the pilot, because cleaner data makes every report better.
A staged approach that works at SMB scale
The pattern we see succeed for businesses in the 10–200 employee range is small, sequential, and deliberately boring:
- Pick one process, one number. Not “AI for the business” — “cut accounts-payable (AP) coding time on month-end close from 12 hours to 4.” If you cannot write the goal as a single number with a baseline, you are not ready.
- Run a four-to-eight-week pilot against that one number. Use an off-the-shelf model wherever you can; custom training is rarely worth it at this scale.
- Decide explicitly what changes in someone’s job. Who runs the new workflow, who reviews the output, what happens when the model is wrong. Write it down.
- Roll out, then instrument. Log inputs, outputs, and overrides from day one so you can prove value six months later when the budget conversation comes back.
The mistake is skipping step 3. It is the difference between a project and a demo.
Where AI is paying off in SMB work right now
The wins we see most often are not glamorous, and that is the point — they survive the quarter:
- Professional services (law, accounting, design): document classification, contract-review triage, time-entry suggestions drawn from calendar and email activity. Three- to six-month payback when the work was previously billable-but-undelivered.
- Light manufacturing and distribution: parsing supplier emails into purchase-order updates, demand forecasting against historical sales plus a few external signals, automated freight-quote reconciliation. It relieves clerical headcount pressure rather than replacing people.
The pattern in both: the AI sits between two systems that previously required a human to retype data between them. That is a far easier business case than “AI for strategic decision-making.”
Watch-outs before you sign
- Audit and explainability. If the output drives a financial entry, a compliance filing, or a customer-facing price, you need a logged reason for every answer. Many cheaper AI products do not provide this.
- Vendor lock-in. Tuning a prompt or workflow tightly to one model is fine for a pilot, risky for a system you will run for three years. Keep the integration thin enough to switch.
- Data residency and confidentiality. Decide what the model is allowed to see before the contract, not after. For regulated work (the Health Insurance Portability and Accountability Act (HIPAA), Payment Card Industry (PCI) standards, or customers who require SOC 2) this is non-negotiable.
- The honest twelve-month picture. A useful first project typically runs 4–8 weeks of implementation, then six to nine months of iteration before it does what the original pitch promised. Plan for the iteration, not just the launch.
Next step
Most AI conversations should start with the data underneath, not the model on top. If you are weighing an AI project and want to know whether the case study you saw last week applies to your actual business, our [[AI solutions and intelligent automation]] is where to begin — including the data-readiness work that decides whether the project is worth starting. We scope realistically for Denver-area SMBs and tell you when the honest answer is “not yet.”