Most writing about AI in business assumes resources you do not have.<\/p>\n
It assumes years of clean historical data. A person who can own the project. Budget for consultants. Volume high enough that a small percentage improvement is real money.<\/p>\n
A twenty-person company has none of that in the same measure. So the useful question is narrower: what actually pays for itself at your size?<\/strong><\/p>\n The answer is a short list, and it is not the exciting part of the technology.<\/p>\n Three things. All of them are about volume of dull work, not sophistication.<\/p>\n Why it works small.<\/strong> Even at fifty bills a month, that is real hours of typing. And you can verify it instantly \u2014 the document is right there.<\/p>\n What you need.<\/strong> Clean vendor records. That is it.<\/p>\n Realistic saving.<\/strong> A few hours a month at fifty bills; considerably more at two hundred.<\/p>\n Product descriptions, routine emails, knowledge base articles.<\/p>\n Why it works small.<\/strong> It removes the blank page, which is the expensive part when one person does everything.<\/p>\n What you need.<\/strong> Nothing. It works from your product data.<\/p>\n The catch.<\/strong> Read every word. At small scale you probably will, because it is one person and they care.<\/p>\n A customer’s history condensed before a call.<\/p>\n Why it works small.<\/strong> In a small company, whoever picks up the phone is often not the person who dealt with them last. This closes that gap.<\/p>\n FIGURE 1: THE THREE THAT PAY AT SMALL SCALE<\/p>\n Reading documents<\/p>\n Drafting text<\/p>\n Summarising<\/p>\n Being direct here saves you money.<\/p>\n Sales prediction.<\/strong> Needs thousands of closed deals. If you close forty a year, a score is a guess with a confident interface.<\/p>\n Lead scoring.<\/strong> Same problem. If you get thirty enquiries a month, sort them yourself in five minutes.<\/p>\n Demand forecasting.<\/strong> Needs years of history and stable patterns. A business winning four large contracts a year has no pattern to learn.<\/p>\n Recommendations from a model.<\/strong> Under a few thousand orders, a hand-set list of “these go together” is more accurate. Not a lesser option \u2014 genuinely more accurate.<\/p>\n Anomaly detection.<\/strong> Needs enough transactions to know what normal looks like. At low volume it flags everything, and you stop reading the flags.<\/p>\n FIGURE 2: WHAT SIZE ACTUALLY DECIDES<\/p>\n Works at any size<\/p>\n Needs volume you may not have<\/p>\n Your data.<\/strong><\/p>\n This is more true at small scale, not less, because you have less of it. Every duplicate customer is a larger proportion of your history.<\/p>\n Four things, and they cost nothing but attention:<\/p>\n Merge duplicate customers.<\/strong> “ABC Trading” and “ABC Trading Ltd” are one company.<\/p>\n Fix product costs.<\/strong> Every margin figure depends on these. In small businesses they are frequently years out of date.<\/p>\n Make units of measure consistent.<\/strong> Decide the rule and apply it.<\/p>\n Agree what revenue means.<\/strong> Invoiced, ordered or delivered. Write it down.<\/p>\n A week spent on this is worth more than any AI feature you could switch on.<\/strong> It is also useful immediately, whether or not you adopt anything.<\/p>\n Six steps, in order, over a few months.<\/p>\n 1. Fix your data.<\/strong> A week. Duplicates, costs, units, definitions.<\/p>\n 2. Measure a baseline.<\/strong> How long does bill entry take? How many bills a month? Write the numbers down.<\/p>\n 3. Turn on document reading.<\/strong> Set up an email alias for supplier bills.<\/p>\n 4. Run it for a month with review.<\/strong> Note where it gets things wrong \u2014 usually tax codes and account allocation.<\/p>\n 5. Compare against your baseline.<\/strong> Did the hours actually drop? If not, find out why before adding anything else.<\/p>\n 6. Add drafting and summaries<\/strong> if step 5 was positive.<\/p>\n Then stop and use it for six months<\/strong> before considering anything else.<\/p>\n FIGURE 3: A PLAN THAT FITS A SMALL COMPANY<\/p>\n Fix the data<\/p>\n Measure<\/p>\n Document reading<\/p>\n Compare<\/p>\n Buying a tool because a competitor mentioned it.<\/strong> The question is what it does for your specific costs.<\/p>\n Adopting several things at once.<\/strong> You will not know what helped.<\/p>\n Removing review to save more time.<\/strong> At small scale one duplicate payment can exceed a year of saved hours.<\/p>\n Paying for capability you cannot feed.<\/strong> Forecasting on eight months of data produces a confident number with no basis.<\/p>\n Worth being straight about, because budgets are real.<\/p>\n Odoo Enterprise<\/strong> is a per-user monthly cost, and AI features are increasingly part of it rather than a separate product. For a small team the licence is a modest line.<\/p>\n Implementation help<\/strong> is usually the larger cost, and it is the one worth spending on \u2014 mostly on getting the data and configuration right rather than on features.<\/p>\n Your own time<\/strong> is the hidden cost. Someone has to make decisions and check output. In a small company that is likely you.<\/p>\n The realistic saving<\/strong> is hours per week, not a headcount. At small scale that time usually goes into work that was not getting done rather than into savings on a payroll line.<\/p>\n One thing small businesses do better than large ones, and it is worth knowing.<\/p>\n You can fix your data.<\/strong> A twenty-person company with three thousand customers can clean its records in a week. A large enterprise with two million cannot.<\/p>\n Since data quality is the main determinant of whether any of this works, that is a genuine advantage \u2014 and it is available to you now, for the cost of some attention.<\/p>\n At small scale, AI pays for reading documents, drafting text and summarising history<\/strong>. Those three are worth having and they work at any volume.<\/p>\n It does not pay for prediction, scoring or forecasting<\/strong>, because those need data volumes you do not have \u2014 and they will produce confident numbers anyway.<\/p>\n Fix your data first.<\/strong> It costs a week, it helps immediately, and it decides whether anything else you try is worth reading.<\/p>\n Small team wondering whether any of this is worth it?<\/p>\n Get in touch. We will tell you honestly which two or three things would pay at your volume \u2014 and which ones to leave until you are bigger.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":" The small business problem Most writing about AI in business assumes resources you do not have. It assumes years of clean historical data. A person who can own the project. Budget for consultants. Volume high enough that a small percentage improvement is real money. A twenty-person company has none of that in the same measure. […]<\/p>\n","protected":false},"author":3,"featured_media":9223,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-9222","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai"],"yoast_head":"\nWhat works at small scale<\/h2>\n
1. Reading supplier documents<\/h3>\n
2. Drafting text<\/h3>\n
3. Summarising before a conversation<\/h3>\n
\n
\n
\n
What does not work at small scale<\/h2>\n
\n
\n
The thing that matters more than any of it<\/h2>\n
A realistic plan<\/h2>\n
\n
\n
\n
\n
What to be careful with<\/h2>\n
What it costs<\/h2>\n
The advantage you actually have<\/h2>\n
The short version<\/h2>\n