Where to start with business digitization - and what to automate first.
By Subash Magar | SNM | 7-minute read
It is 9:15 on Monday. A customer asks, "Can you confirm when my order will arrive?" Sales checks a spreadsheet. The warehouse searches a message thread. Finance asks whether the latest quotation included delivery.
Everyone is working. The customer is still waiting.
If that sounds familiar, start by looking at how information moves through your business. Every time an employee has to copy, chase, or reconstruct an update, there is a process worth improving.
This guide shows how to choose one manageable workflow, connect the people involved, and measure whether the change actually helps.
The hidden work between your tools
Spreadsheets are useful for analysis and flexible planning. Messaging is convenient for quick conversations. Trouble begins when a customer commitment, stock update, or approval exists only in a personal file or a busy chat thread.
Watch for three patterns: the same information is entered several times; a task waits because nobody knows who owns it; or two departments give different answers about the same order. These are practical starting points for improvement.
Digitization and automation solve different problems
Digitization makes information easier to capture, find, and use. Instead of a handwritten delivery note, you keep a structured delivery record. Automation applies a rule to that information - for example, assigning a follow-up when a quotation needs attention.
The sequence matters. Agree on the information, the owner, and the next step before asking software to perform that step automatically. Otherwise, an unclear process simply moves faster.
Follow one order before choosing software
Consider a fictional small distributor, Harbor Supply. A customer requests 40 units. Sales sends a quotation, the warehouse can ship only 25, and finance needs to know what should be billed. This is an illustrative scenario, not a client case study.
In a disconnected process, "40 ordered" may become "40 delivered" as someone copies the quantity into another file. The improvement is to give each fact a clear home: the quotation holds the offer; the confirmed order holds the commitment; the delivery record holds what actually shipped.
Ask the team to trace this journey: inquiry, quotation, confirmed order, delivery, invoice, and payment. At each handoff, identify the record, the person responsible, and what must be true before work proceeds.
Try this with your team
Choose one recent order. Can a colleague find its agreed price, delivery status, and next action without contacting the original salesperson? Wherever the search breaks down, record the missing information or unclear responsibility. That is your first requirements list.
What a connected process could look like
For Harbor Supply, sales owns the customer requirement and agreed terms. The warehouse records the actual shipment and outstanding quantity. Finance checks the billing basis before issuing the invoice. A shared system makes these related records accessible to the right people.
Odoo is one option for implementing this structure. Its CRM supports opportunity tracking, and activities can attach follow-up tasks to business records. A useful first step is to give each active opportunity an owner and a dated next action. [1, 2]
Billing rules need an explicit decision. Odoo supports invoicing based on ordered or delivered quantities. In our example, a delivered-quantity policy would make the 25 shipped units the basis for the relevant invoice; an ordered-quantity policy follows a different timing rule. Choose the policy that fits the agreement, then test partial deliveries. [3]
These are capabilities to configure and validate. Installing apps does not decide your approval rules, clean your data, or train your employees. Also, do not assume existing WhatsApp messages will automatically become ERP records; message capture or integration requires a separate design decision.
Start with one useful automation
Choose a frequent, predictable task where the consequence of a mistake is manageable. A reminder for a salesperson to review an unanswered quotation is a good pilot: the system prompts action, while a person checks the context.
Define the trigger, the action, the owner, and the exception. For example: when an open quotation reaches its review date, create one follow-up task for its owner. Stop the rule when the quotation is accepted or cancelled, and prevent duplicate reminders. Test this behavior before enabling it broadly.
Keep judgment where it belongs
An overdue invoice may be disputed. A shipment may be blocked. A customer may already have replied through another channel. Give employees a way to pause automation, explain the exception, and assign the next action. Decide who monitors failed or incomplete runs.
A practical first month
Week one: observe and choose
Pick one workflow and interview the people who perform it. Record the delays, repeated entries, and common exceptions. Set a narrow pilot scope and measure the current process before changing it.
Week two: simplify and prepare
Agree on ownership, required fields, approvals, and status definitions. Clean the customer and product records used in the pilot. Decide who can view or edit them and how corrections will be handled.
Week three: configure and rehearse
Set up the workflow with a small group. Test an ordinary order, a partial delivery, a cancellation, and incorrect data. Train each person using tasks from their own role. Include a recovery plan if the pilot encounters problems.
Week four: review and adjust
Run a controlled pilot, collect feedback, and compare results with the starting point. Fix confusing steps before adding more automation. This is a suggested pilot schedule; a full ERP rollout may require substantially more time.
Measure the improvement - not the number of apps
Track measures that describe the work: time to prepare a quotation, orders requiring correction, time from eligible delivery to invoice, and follow-up tasks completed by their due dates. Compare similar workloads so a quiet week does not look like an automation success.
Here is an illustrative calculation. If 100 monthly orders each require 12 minutes of repeated entry, that is 20 hours. If the pilot reduces that work to 5 minutes per order, it releases about 11.7 hours per month. These are hypothetical figures, not a promised result.
Released time is capacity, not automatically a cash saving. Weigh the benefit against software, implementation, training, and ongoing maintenance costs. Ask what the team can do with the time recovered: answer customers sooner, check orders more carefully, or handle more work.
Before you expand, answer these questions
Can someone cover the process when its usual owner is absent? Can staff see what is waiting and why? Are duplicates and incomplete records being caught? Can the team handle an exception without starting a separate spreadsheet? Have the people doing the work agreed that the change helps?
If an answer is unclear, improve that part of the pilot before extending it to the rest of the business.
Your next step: find the handoff that needs fixing
You do not need to redesign the entire company this week. Choose the point where people repeatedly ask, "What happens next?" Make the information visible, assign responsibility, and test one improvement.
Want help mapping that workflow? Connect with Subash Magar at SNM to discuss your current process, the biggest handoff problem, and whether Odoo could support the next step.
About the author
Subash Magar is an Odoo functional and technical consultant and founder of SNM. His work connects business requirements with workflow design, ERP implementation, customization, and employee training.
Odoo references
- [1] Odoo 19 documentation: CRM
- [2] Odoo 19 documentation: Activities
- [3] Odoo 19 documentation: Invoicing policies