Skip to content
Writing
·3 min read·Field note

AI in production is the number that matters

Drafted through my n8n + AI pipeline, edited by me.

Fresh 2026 adoption numbers landed, and they disagree wildly: 82 percent of small businesses say they have invested in AI, 76 percent say they use it, and the US Census Bureau puts actual production use at 17 to 20 percent. That spread is not noise. It is the difference between trying AI and running it.

What the AI in production gap means

'Using AI' usually means someone opened a chatbot to draft an email. AI in production means it runs inside a real workflow, on real data, every day, with an output you can measure. The first is a habit. The second is a system. Almost all of the reported adoption is the first.

Before and after: 'using AI' is someone opening a chatbot occasionally with nothing wired in; 'AI in production' is a real trigger running on real data daily, wired into your tools, logged and measured.

  • Someone opens a chatbot to draft an email.
  • It helps, sometimes.
  • Nothing is wired into your tools.
  • No record, and nothing measured.
'Using AI' is a habit. 'AI in production' is a system.

What it means for a small business

The bar to stand out is low. While competitors count 'we use AI' as done, the real win is getting one workflow into production: triggered, doing real work, logged, and measured. That is where the reclaimed hours and the actual edge come from, not from another open chat tab.

  • Pick one repetitive, rule-clear task.
  • Put AI in the loop with a human check on anything irreversible.
  • Wire it into the tool you already use, and measure the hours it returns.

Bring me one workflow you wish ran itself, and I'll tell you how to get it into production, not just into a chat window.

Building something this should run inside?

Book a systems call