If your quotes live in email, your stock in a spreadsheet and your invoices in a third place, you do not have a software problem. You have a connection problem. Devvista is a software development and growth agency that implements Odoo and builds custom business management systems for Australian businesses, from the first workshop to go-live.
This page covers the signs you have outgrown separate tools, the four routes you can take, the Australian tax and payment points to settle first, what a project costs in hours and dollars, and how delivery works from a distance.
What business management software does, and the signs you need it
Business management software puts the core records of a company in one place: customers, quotes, sales orders, stock, purchases, invoices, projects and reports. When a sale is confirmed, the stock moves, the invoice is raised and the figure lands in the report without anyone retyping it.
Most small firms start with separate tools, and that is sensible. The trouble starts when the gaps between the tools become a job. Use the table to see where you sit.
| What you see in the business | What it usually means | What fixes it |
|---|---|---|
| The same customer or product is typed into two or more systems | No single record of truth | One system that owns the data, or an integration |
| Month-end reports are built by hand from exports | Nobody trusts the numbers until someone checks them | Reports that read live from the same records |
| Stock counts and sales never quite agree | Inventory is updated by hand | Orders that move stock automatically |
| A quote is lost between email and the accounting package | The sales process has no home | Quote to order to invoice in one flow |
| One person holds the process in their head | The business depends on a single spreadsheet and a single person | A documented workflow in a system |
If one row describes you, you may only need an integration. If three or four do, a business management system pays for itself in hours saved.
Four routes: spreadsheets, packages, Odoo or a custom build
There is no best route, only one that fits your size and how unusual your process is. Here is the honest comparison.
| Route | Best when | Watch out for |
|---|---|---|
| Spreadsheets plus an accounting package | Under a handful of staff, simple sales, few products | Errors and key-person risk grow with every new row |
| A packaged all-in-one tool | Your process looks like the average business | You adapt your business to the tool, and extra modules cost more |
| Odoo, configured and extended | You want sales, stock, accounting and projects in one system and can accept its standard flows | It needs a proper setup, data migration and staff training |
| A custom-built system | Your core workflow is unusual and no package fits without heavy bending | Higher build cost, so be sure the process is worth it |
Our Odoo implementation service covers the third route, and our custom software development page covers the fourth. We will tell you if a package or a simple integration is enough, because a build you do not need costs both of us time.
Australian points to settle before you choose a system
A system that does not handle local tax and payments just moves the spreadsheet to a new place. The Odoo's Australia fiscal localization documentation lists what its Australian setup covers. We have summarised it here as a checklist of questions for any system you consider, including ours.
| Topic | What the Odoo documentation says | What to ask any vendor |
|---|---|---|
| GST | The Australian localization uses GST at a standard rate of 10%, with sales and purchase variants. | Does it apply the right GST to each line, and to imports? |
| BAS reporting | A BAS report covers GST, PAYG tax withheld and deferred GST, using pre-configured tax grids. | Can it produce the figures your accountant needs each period? |
| Subcontractor payments | A TPAR report combines taxes and fiscal positions to report payments to subcontractors. | If you pay contractors, can it report them? |
| Supplier payments | ABA credit transfer support is installed with the localization, and ABA files for batch payments are listed. | Can you pay a batch of suppliers from one file? |
| E-invoicing | Peppol e-invoicing is listed among the localization features. | Can it send and receive e-invoices if your customers require them? |
| Account security | Two-factor authentication cannot be deactivated for this localization, because the Australian government requires it. | How are logins protected, and who can see financial data? |
Two limits. The Odoo page also says it does not fetch the deferred GST balance from the ATO automatically, so that figure is entered by hand. And the same page points payroll to separate documentation that we have not reviewed, so confirm payroll and Single Touch Payroll with your payroll provider and accountant. Nothing here is tax advice.
Who runs on this kind of system: the size of the Australian market
Most Australian businesses are small. The Australian Bureau of Statistics business counts report 2,814,778 actively trading businesses at 30 June 2026. Of those, 1,818,575 have no employees, 689,600 have one to four, and 232,912 have five to 19. By our arithmetic that makes about 97.4% of businesses smaller than 20 staff.
That matters for the choice of system. A firm with five to 19 people has real processes but no IT department, so it needs a system that is simple to run and that a small team can understand. That is why we steer most firms of this size towards a configured package or Odoo first, and towards a custom build only when the process demands it.
What moves the cost of a business management project
A short call comes first, then a scoped proposal. Tell us the range you can spend and we shape the scope around it.
| Example (assumption) | What drives the cost |
|---|---|
| Odoo for a 10-person trade business: sales, stock, invoicing and a stock import from a spreadsheet | How many records are migrated and cleaned, and the invoicing rules |
| Odoo for a 25-person distributor: adds purchasing, a custom report and two integrations | The custom report and each integration |
| A custom job and invoicing system for a 15-person services firm | Staff roles, screens and reports |
What moves the number: how many records must be migrated and cleaned, how many integrations you need, how many staff roles need their own screens, and how many reports you want. A written scope is the best way to keep the price steady. Our guide on what custom software costs sets out the factors in more detail.
How a remote delivery runs, step by step
The process is built to be written down and inspected, not to depend on being in a room together.
- Discovery call. You describe the process that costs the most hours. We tell you whether a package, Odoo, an integration or a custom build fits, and what it would cost
- Written scope. Screens, data, integrations, reports and what is out of scope, in a document you approve before the price is fixed
- Data preparation. We agree which records move across, clean obvious duplicates and test an import before the real one
- Build in stages. You see a working version at each stage on a shared board, so problems surface early
- Training and handover. Recorded walkthroughs and written guides for each role, then a period of support after go-live
- Review. We check the three numbers below against the baseline
The code and configuration sit in your repository and your accounts.
What to prepare before the first call
You do not need a specification. A short list gets the first call to a useful answer faster.
- The three tasks that cost your team the most hours each week.
- The tools you use now and what you pay for them.
- A rough count of customers, products and staff roles.
- Any integration that must stay, such as your accounting package or an online store.
- The reports you wish you had, written as the question they answer.
Is Devvista the right partner for your business?
We are a good fit for owners who want a clear scope and price, and who can work with a team over video and a shared board.
| A good fit | Not a good fit |
|---|---|
| Small and mid-sized firms with real processes and no IT team | A project that needs engineers on site in Australia |
| Owners who want the scope written down before work starts | A tender that requires an Australian entity, ABN or local references |
| Firms who will confirm tax points with their own accountant | Companies that want a product on the shelf with no setup |
See also business automation and NDIS CRM.
How to tell the system is paying back
Write three numbers down before the project starts and read them monthly. Without a baseline, nobody can say whether it worked.
- Hours per week on the process, from a two-week timesheet sample before and after.
- Days to close the month, from the last sale to the report your accountant needs.
- Stock or invoice corrections per month, counted from the credit notes and adjustments you raise.