Predicting technology five years out is unreliable. Predicting what it means for a business function is a little more stable, because the underlying jobs change slowly.<\/p>\n
So this article goes function by function \u2014 what the work looks like now, what it plausibly looks like later, and what is worth doing this year regardless.<\/p>\n
The final section is the useful one.<\/p>\n
Now.<\/strong> Documents read into drafts, a person checks and posts. Reconciliation matches proposed, a person handles the exceptions. Month-end close is manual.<\/p>\n Likely.<\/strong> More of the routine close prepared automatically \u2014 checks run, missing documents chased, exceptions assembled. The accountant reviews a prepared package rather than building it.<\/p>\n Unlikely to change.<\/strong> Somebody signs the accounts and must be able to explain them. Provisions, accruals and estimates stay judgements. The close stays a review by a person.<\/p>\n The shift:<\/strong> from producing the numbers to interrogating them.<\/p>\n Now.<\/strong> Summaries before calls, drafted follow-ups, prompts for the next activity, prioritised pipelines where there is enough history.<\/p>\n Likely.<\/strong> More preparation \u2014 a pack before each meeting with the history, the open items, the pricing position and what changed since last time. Better prioritisation as data accumulates.<\/p>\n Unlikely to change.<\/strong> The conversation. Negotiation, reading a room, knowing when a deal is not real. Stage changes should stay with the salesperson who knows what happened.<\/p>\n The shift:<\/strong> less admin around selling, roughly the same selling.<\/p>\n Now.<\/strong> Documents read, three-way matching made practical, forecast-based reordering where stock records are accurate.<\/p>\n Likely.<\/strong> Reorder proposals prepared across the whole range with supplier reliability factored in, presented for weekly review rather than decided item by item.<\/p>\n Unlikely to change.<\/strong> Someone counts the receipt. Everything downstream depends on that one human action, and no forecasting improvement substitutes for it.<\/p>\n The shift:<\/strong> from deciding each order to reviewing a prepared list.<\/p>\n FIGURE 1: THE SAME PATTERN ACROSS EVERY FUNCTION<\/p>\n Accounting<\/p>\n Sales<\/p>\n Purchasing<\/p>\n Support<\/p>\n Now.<\/strong> Context summarised for the agent, replies drafted, tickets routed, articles suggested.<\/p>\n Likely.<\/strong> More routine resolution handled end to end, with narrow scope and a fast route to a person. Better prediction of which customers are about to have a problem.<\/p>\n Unlikely to change.<\/strong> The difficult conversation. The customer who is upset and needs a person who can decide something.<\/p>\n The shift:<\/strong> agents handle more, with better preparation, and the hard cases still land with people.<\/p>\n Now.<\/strong> Scheduling assistance, component forecasting, document reading, consumption variance flagging.<\/p>\n Likely.<\/strong> Better scheduling as operation data accumulates. Predictive maintenance where equipment is instrumented \u2014 which is a separate investment, not a software upgrade.<\/p>\n Unlikely to change.<\/strong> Bills of materials still have to be right. A wrong header quantity against the product’s unit of measure will produce wrong numbers quietly, whatever else improves.<\/p>\n The shift:<\/strong> planning gets better, the shop floor changes only where equipment does.<\/p>\n Now.<\/strong> Questions asked in plain language, faster answers, analysis assembled rather than commissioned.<\/p>\n Likely.<\/strong> Analysis arriving before the meeting rather than being built during it. Changes flagged as they happen rather than discovered at month-end.<\/p>\n Unlikely to change.<\/strong> Deciding what matters. A number tells you margin fell. Knowing whether that was a deliberate strategic order or a problem is understanding, and it is not in the data.<\/p>\n The shift:<\/strong> from assembling numbers to discussing them.<\/p>\n Five things, and this is the part worth acting on.<\/p>\n Bad data produces bad answers.<\/strong> More capable systems reach wrong conclusions faster and state them more convincingly. This gets worse, not better.<\/p>\n Unclear processes stay unclear.<\/strong> If nobody agrees who approves a discount, no technology settles it.<\/p>\n Someone is accountable.<\/strong> For the accounts, to the board, to the customer.<\/p>\n Judgement about people stays with people.<\/strong> Credit, relationships, difficult accounts.<\/p>\n Implementation decides the outcome.<\/strong> The gap between businesses will keep coming from how carefully the system was set up, not which features were bought.<\/p>\n FIGURE 2: WHAT MOVES AND WHAT DOES NOT<\/p>\n Changing<\/p>\n Not changing<\/p>\n The prediction worth making, because it is about behaviour rather than technology.<\/p>\n Two companies buy the same system with the same features.<\/p>\n One has clean master data, agreed definitions and a clear process. The other has duplicate customers, product costs three years out of date, and three people who each define revenue differently.<\/p>\n The first gets useful answers. The second gets confident nonsense, faster than before.<\/strong><\/p>\n That gap exists today. Every capability added widens it, because every capability is built on the same data.<\/p>\n Five things. None of them depend on predicting anything correctly.<\/p>\n 1. Fix your master data.<\/strong> Duplicates merged, costs correct, units consistent. A week’s work in a small company, and it improves everything immediately.<\/p>\n 2. Agree your definitions.<\/strong> What revenue means, when a sale counts, what is excluded. Write it down and share it.<\/p>\n 3. Keep customisation in proper modules.<\/strong> Whatever arrives will assume a standard structure. Edited core files make every future change harder.<\/p>\n 4. Adopt what is proven.<\/strong> Document reading pays now. Measure the hours before and after.<\/p>\n 5. Decide where humans stay<\/strong> and write it down. Anything financial, anything customer-facing.<\/p>\n All five are useful today.<\/strong> None of them are bets on a prediction. That is what makes them the right preparation.<\/p>\n FIGURE 3: PREPARATION THAT IS USEFUL EITHER WAY<\/p>\n Clean data<\/p>\n Agreed definitions<\/p>\n Customisation in modules<\/p>\n In five years, a well-run business on Odoo probably looks like this.<\/p>\n Most documents arrive as drafts rather than as typing. Most routine work is prepared and reviewed rather than assembled. Questions get answered in minutes. Attention is better ordered.<\/p>\n People spend more of the week on exceptions, judgement and relationships<\/strong> \u2014 which is what they were hired for.<\/p>\n Not a transformation. A steady removal of the parts of the job nobody valued.<\/p>\n That is worth having, and it is closer than the marketing suggests in some places and further away in others.<\/p>\n Every function follows the same pattern: less assembling, more deciding.<\/strong><\/p>\n What does not change is what actually determines your outcome \u2014 data quality, process clarity, and someone accountable for the numbers.<\/strong><\/p>\n The best preparation for whatever arrives is the work that helps you today: clean your data, agree your definitions, keep your customisation clean, and adopt what is already proven.<\/p>\n Wondering what to do now to be ready?<\/p>\n Get in touch. The answer is almost always clean data and a clear process \u2014 and both pay for themselves whether or not anything new arrives.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":" How to read this Predicting technology five years out is unreliable. Predicting what it means for a business function is a little more stable, because the underlying jobs change slowly. So this article goes function by function \u2014 what the work looks like now, what it plausibly looks like later, and what is worth doing […]<\/p>\n","protected":false},"author":3,"featured_media":9241,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-9240","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai"],"yoast_head":"\nSales<\/h2>\n
Purchasing and inventory<\/h2>\n
\n
\n
\n
\n
Support<\/h2>\n
Manufacturing<\/h2>\n
Management<\/h2>\n
What will not change anywhere<\/h2>\n
\n
\n
The gap that widens<\/h2>\n
What to do this year<\/h2>\n
\n
\n
\n
The realistic picture<\/h2>\n
The short version<\/h2>\n