If your team retypes orders from e-mail into a stock spreadsheet, chases leads from memory and keeps a sheet next to software you already pay for, the problem is rarely a lack of software; it is the wrong few systems, badly joined. Business software solutions are the applications a company runs on (accounting, a CRM, an operations or ERP system, HR and payroll, plus the automation between them), and most SMEs need those core systems bought off the shelf, with custom business software only where their process is genuinely unusual.
“Business software” covers everything from a £15-a-month invoicing app to a six-figure ERP. This guide is the framework we use with small and mid-sized businesses in the UK and US to decide what to buy, what to build and what to leave alone.
If you only read one line: buy standard tools for standard jobs, build only where your process is genuinely yours, and fix the most expensive problem first. The rest of this guide shows you how to apply that to your own business.
What are business software solutions?
In short: software that records and moves the work of the business, in three forms: bought, built, or a mix of both.
Business software solutions are the applications a company uses to run itself. They record what is sold, to whom and at what margin. They track stock, jobs and people. They move information from one team to the next so nobody has to retype it.
Three terms get used interchangeably, and the difference matters when you are comparing quotes:
The umbrella term. Any application a business uses to do its work, from an invoicing app to a booking system. Usually one tool per job.
One system that runs several core functions together: sales, jobs or stock, invoicing and reporting, so managers see the whole business in one place. ERP is the larger form of it.
Software built for one company’s process. It can be a single internal tool, a CRM or a full management system. You own it and it does not charge per seat.
Usually means the whole arrangement: the products, how they are configured, and the integrations and automation that make them work as one.
Whatever you call it, it comes in three forms:
- Off-the-shelf (packaged) software. A product many companies use, usually sold as a monthly subscription per user. Fast to start, and you adapt your process to it.
- Custom business software. Built for one company’s process. Slower to start, but it fits the way you work, you own it, and it does not charge per seat.
- Hybrid. Standard tools where the job is standard, with a custom layer or integrations that join them up. This is where most growing SMEs end up.
Which tools to start with, by category
In short: for standard jobs, start with an established product; build custom only where the product forces a workaround.
These are well-known starting points, not endorsements or a ranking. Prices and plans change often, so check each vendor’s current pricing before you decide.
| Category | Start with | Best when | Consider custom when |
|---|---|---|---|
| Accounting | Xero, QuickBooks, Sage, FreeAgent | You need invoicing, bank feeds and tax returns. FreeAgent suits sole traders and micro-businesses; Sage suits established UK SMEs. | Almost never. Keep the accounting package and connect other systems to it. |
| CRM | HubSpot, Pipedrive, Salesforce, Zoho CRM | HubSpot to start free with sales and marketing together; Pipedrive for a small, pipeline-led sales team; Salesforce for large or complex teams; Zoho for a budget suite. | Your quoting, pricing or follow-up rules are how you win work, or per-seat fees outgrow the team. See custom CRM development. |
| ERP & operations | Odoo, NetSuite, Dynamics 365, SAP Business One | Odoo for a modular start; NetSuite for growing multi-entity businesses; Dynamics 365 if you run on Microsoft; SAP Business One for small manufacturers and distributors. | Your stock, costing or job logic does not fit any module without spreadsheets alongside it. |
| HR & payroll | BrightHR, Breathe, Sage Payroll, Xero Payroll | Holidays, records and payroll for a standard UK workforce. | Rarely. Shift patterns or pay rules unusual enough to need it are the exception. |
| Sales channels | Shopify, WooCommerce, Square, Lightspeed | Shopify for a hosted online store; WooCommerce if you run WordPress; Square or Lightspeed for shop and hospitality tills. | Pricing, bundling or trade-customer rules the platform cannot express. |
| Collaboration | Microsoft 365, Google Workspace, Slack, Asana | Always a buy: e-mail, documents, chat and task tracking. | Never. |
| Automation | Zapier, Make, Power Automate | Zapier for the simplest no-code links; Make for multi-step visual flows; Power Automate inside Microsoft 365. | The flow carries money or customer data, runs at volume, or must recover from errors reliably. See custom software integrations. |
The pattern across every row: buy the standard tool, then connect it. If you are unsure which side of the line you are on, the full comparison is in custom software vs off-the-shelf software.
The main types of business software
In short: seven categories cover almost every system an SME runs; accounting and collaboration are always a buy.
Almost every business system falls into one of these categories. The examples are well-known off-the-shelf products, not recommendations; they show what each category looks like.
| Type | What it does | Common off-the-shelf examples | You need it when… |
|---|---|---|---|
| Accounting & invoicing | Invoices, bills, bank reconciliation, VAT or sales tax, financial reports | Xero, QuickBooks, Sage, FreeAgent | From day one. This is almost always a buy, not a build. |
| CRM (customers and sales) | Every lead, quote, follow-up and deal, with an owner and a next action | HubSpot, Salesforce, Pipedrive, Zoho CRM | Leads live in inboxes and WhatsApp, and follow-up depends on memory |
| ERP & operations | Inventory, purchasing, production, jobs, costing and reporting in one place | Microsoft Dynamics 365, NetSuite, Odoo, SAP Business One | Nobody can tell you today’s stock or this month’s true margin without a spreadsheet exercise |
| HR & payroll | Staff records, holiday, attendance, payroll, payslips | BrightHR, Breathe, Sage Payroll, Xero Payroll | Payroll takes days each month or produces disputes |
| Sales channels | Online store, point of sale, bookings, customer portal | Shopify, WooCommerce, Square, Lightspeed | Customers buy or book directly from you |
| Collaboration | E-mail, documents, chat, projects | Microsoft 365, Google Workspace, Slack, Asana | From day one. Always a buy. |
| Automation & AI | Moves data between systems, reads documents, sends follow-ups, answers calls | Zapier, Make, Power Automate, or custom-built | Your staff are the integration, copying data between tools that do not talk |
Two points people miss. First, the automation layer is often the cheapest place to start and pays back fastest, because it replaces nothing; it just stops people doing robot work. Second, for businesses that live on the phone, an AI calling agent now belongs in this list. It answers, qualifies and books callers when nobody is free.
Business software examples by type of business
In short: the core stack is similar everywhere; what differs is the one process that makes each business money.
These are illustrative examples of the patterns we see, not specific client projects. Each one names the standard tools that usually fit and the place where custom business software tends to earn its cost.
Accounting plus a CRM is standard. The custom piece is usually costing and stock: landed cost per shipment, supplier price lists, reserved stock against open quotes, and a live margin per order instead of a month-end surprise.
Accountants, consultants, agencies and law firms buy practice or project tools for time and billing. The custom work is often intake and client onboarding: one enquiry form that creates the client, the matter or project, the engagement letter and the follow-up tasks.
Installers, maintenance and cleaning firms need job scheduling, a mobile app for engineers, photos and sign-off on site, and invoicing the same day. Packaged job tools fit simple trades; custom fits when quoting, variations or compliance paperwork are unusual.
Booking, reminders and payments are standard. The custom layer is usually the rules: which practitioner can see which case, room and equipment scheduling, intake forms that feed the record, and reminder calls that cut no-shows.
Shopify or WooCommerce runs the shop. Custom business software shows up behind it: order routing to warehouses, bundle and subscription logic, wholesale pricing per customer, and returns that update stock and accounting without a person in the middle.
Nobody here rebuilds accounting or e-mail. The money goes into the process specific to how the business wins and delivers work.
What a small business or SME actually needs, by stage
In short: the breaking point tells you which system to add next, more reliably than headcount does.
You do not need every category at once. This is the pattern we see in UK and US SMEs as they grow.
| Stage | Typical stack | The usual breaking point |
|---|---|---|
| 1–10 people | Cloud accounting, Microsoft 365 or Google Workspace, a simple CRM or a well-kept spreadsheet, a payroll service | Enquiries get missed because they arrive on five channels |
| 10–50 people | A proper CRM, stock or job management, HR software, the first automations between them | The same data is typed into three systems, and reports need a day of spreadsheet work |
| 50–250 people | An ERP or connected operations platform, CRM integrated with it, dashboards, role-based access | Per-user licences balloon, and the tools no longer match how the business actually works |
The breaking point is more useful than the headcount. If you recognise the problem in the right-hand column, that is the system to look at next, whatever your size.
Signs you have outgrown your current tools
In short: when staff work around the software instead of in it, the tool has stopped fitting.
The clearest signs, and the point where custom business software development starts to pay for itself:
- Your team keeps a spreadsheet next to a tool you pay for. That spreadsheet is the specification for the software you should have.
- The process is the business. A trading company’s costing logic, a clinic’s scheduling rules or a contractor’s job and variation tracking are competitive advantages, not settings on a form.
- Licences punish growth. You pay for 40 modules to use three, and the bill rises every time you hire.
- Two systems must behave as one. Winning a deal should create the job, reserve the stock and raise the invoice, and the vendors will not connect.
- Reports need a person. Every month someone spends a day exporting, pasting and reconciling before anyone can see the numbers.
- Data rules are strict. You need UK hosting, detailed access control or an audit trail a shared platform will not give you.
If none of these apply, buy. Spending £8,000 to build what a £30-a-month subscription already does is bad engineering and worse business. We say so when we see it. For the full list of signals and how to weigh them, see when a business should build custom software.
Off-the-shelf, custom or hybrid
In short: buy what is standard, build what is yours, and expect to end up with a mix.
This is not an ideological choice. It is arithmetic plus one judgement call: is this process standard, or is it how we win?
| Off-the-shelf | Custom | Hybrid | |
|---|---|---|---|
| Time to start | Days | First release in weeks | Days for the standard parts, weeks for the custom layer |
| Cost model | Per-user subscription, rising with headcount | One-off build plus hosting and maintenance | Some subscriptions plus a smaller build |
| Fit to your process | You adapt to the tool | Built around your process | Standard where standard, custom where it matters |
| Ownership | Vendor’s platform and roadmap | Your code and your data | Your custom layer; vendor for the rest |
| Best for | Accounting, e-mail, payroll, basic e-commerce | Unusual workflows, growing teams, systems that must work as one | Most SMEs past about 15 people |
The hybrid answer wins more often than either extreme: keep the accounting package, keep the payment provider, and build the piece that ties them to how you actually work. For the full comparison read custom software vs off-the-shelf software; for sales systems specifically, see custom CRM vs off-the-shelf CRM.
Not sure whether to buy or build?
Send us two lines about the process that keeps breaking and the tools you already use. We will tell you honestly whether you need custom software at all.
How your business systems should connect
In short: decide which system owns each piece of data, then make every other system read from it.
Most of the pain in a small business software stack is in the gaps between tools, where a person copies a customer from the CRM into accounting, or an order from the shop into the stock sheet.
Three rules keep integrations manageable:
- One owner per type of data. Customers live in the CRM, invoices in accounting, stock in the ERP or inventory tool. Other systems read from the owner rather than keeping their own copy.
- Use the official API where it exists. Xero, QuickBooks, Sage, HubSpot, Shopify and most modern tools have one. Screen-scraping and nightly CSV imports break quietly.
- Log every sync. When a record fails to copy, someone should be told the same day, not at month-end.
Simple connections between two mainstream tools can often be done with Zapier, Make or Power Automate. When the logic gets conditional, the volume grows, or the data is sensitive, a small custom integration is usually cheaper to run and easier to trust. We cover the options and costs in custom software integrations.
Where business process automation fits
In short: automation is often the first and cheapest win, because it removes retyping without replacing any system.
Business process automation means letting software do the repetitive steps between people and systems: creating the CRM record from a web form, sending the quote follow-up three days later, raising the invoice when a job is signed off, or chasing a missing document.
Good first candidates are tasks that happen often, follow the same rules each time and currently involve someone copying data. A typical automation between two systems costs £650–£2,500 ($800–$3,000) and is live in 3–10 days, which is why it is often the right place to start before any bigger build.
AI now extends this to work that used to need a person to read or listen: sorting incoming e-mails, extracting details from documents, or answering and qualifying phone calls. Our guide to business process automation explains how to pick candidates, and our AI automation service covers what we build.
Will your business software scale with you?
In short: check how cost, speed and permissions behave when users, data and locations double.
Scalability for an SME is less about millions of users and more about four practical questions:
- Cost. What does the system cost at twice your current headcount? Per-seat licences scale linearly; a custom system on cloud hosting usually does not.
- Data. Will reports and searches still be quick with five years of orders in them? Ask the vendor or developer how they test this.
- Structure. Can it handle a second site, a new product line, another currency or a new team without a rebuild?
- Permissions. As you hire, can you control who sees margins, salaries and client data by role rather than by trust?
For custom builds, the answer comes from sensible choices early: a modular design so new parts can be added one at a time, an API so other systems can connect, and mainstream cloud hosting such as AWS that grows with use. You should not pay for scale you do not need yet, but you should not be boxed in either.
Security questions to ask about any business software
In short: access, backups, an audit trail and clear ownership matter more for an SME than exotic features.
Whether you buy or build, ask:
- Does every user log in individually, with multi-factor authentication, and can access be limited by role?
- Where is the data hosted, is it encrypted, and how often is it backed up? Has anyone tested a restore?
- Is there an audit trail showing who changed what, and when?
- Who at the supplier can see your data, and how is that access controlled and removed?
- Are the cloud accounts, domain and code in your company’s name, so you are never locked out?
The UK’s National Cyber Security Centre publishes a practical small business guide covering backups, devices, accounts and scams. For what to require from a custom build specifically, see custom business software security.
What business software costs in the UK and US
In short: subscriptions look cheap and grow with headcount; custom builds cost more up front and much less per user.
Off-the-shelf costs are easy to see and easy to underestimate: SaaS products commonly cost £10–£120 per user per month, and a 25-person team on a few mid-tier tools can pass £15,000 a year, every year, before setup and consultants.
For custom work, these are DataVolve’s typical ranges for a small senior team. They are indicative and fixed in writing after scoping:
| Project | Typical cost (GBP) | Typical cost (USD) | Time to live |
|---|---|---|---|
| Automation between two systems | £650–£2,500 | $800–$3,000 | 3–10 days |
| Internal tool that replaces a spreadsheet | £1,500–£5,000 | $2,000–$6,000 | 2–3 weeks |
| Single business module: inventory, purchasing, pipeline or payroll | £4,000–£12,000 | $5,000–$15,000 | 2–4 weeks |
| AI agent (chat or voice) | £2,500–£10,000 | $3,000–$12,000 | 2–4 weeks |
| Custom CRM with automation and reporting | £8,000–£24,000 | $10,000–$30,000 | 3–6 weeks |
| Multi-module ERP platform | £12,000–£48,000+ | $15,000–$60,000+ | 6–16 weeks, phased |
Running costs after launch are usually hosting (often £15–£250 or $20–$300 a month) plus maintenance at 15–25% of the build cost a year. For the full breakdown, including VAT and R&D tax relief, see the UK cost guide, or the custom software development cost guide for prices in dollars.
UK-specific things to check
In short: keep accounting MTD-compatible, know where personal data lives, and check VAT on the quote.
- Making Tax Digital. HMRC says VAT-registered businesses must use compatible software to keep VAT records and file VAT returns. Making Tax Digital for Income Tax applies from 6 April 2026 to sole traders and landlords with qualifying income over £50,000. Keep your accounting software MTD-compatible and let other systems feed it, rather than replacing it.
- UK GDPR. Any system that holds customer or staff data needs a lawful basis, sensible retention and controlled access. Ask where the data is hosted; a UK or EU region is available on every major cloud.
- Access from outside the UK. If a supplier’s team outside the UK can see personal data, you need a transfer safeguard such as the ICO-approved International Data Transfer Agreement. A good supplier raises this before you do.
- VAT on the build. Check whether quotes include VAT, and how the reverse charge applies if the supplier is outside the UK.
This is general information, not legal or tax advice; check the detail with your accountant. For how we handle these points on UK builds (UK-region hosting, transfer paperwork and fixed prices in pounds), see custom software development for UK businesses.
For US businesses
In short: the same framework applies; budget in dollars and plan around your accounting package and time zones.
Nothing in the buy, build or hybrid logic changes in the US. The categories are the same, QuickBooks is a common accounting package to connect to, and the first question is still which manual process costs the most.
Practical differences are budget and working hours. The USD ranges above are our typical figures for US clients, and our engineering team supports clients in the US as well as the UK, with weekly demos throughout the build. See software development for US businesses for how that works, and the dollar cost guide for a fuller breakdown.
Decision framework: which system to fix first
In short: put a rough number on your three worst problems and fix the biggest one first.
Sequencing is where most money is wasted. Companies buy the system a competitor mentioned instead of the one their own numbers point to. Use this test:
Choosing the next business system
- List your three most expensive recurring problemsIn plain words: “We lose about four enquiries a week because nobody follows up.” “Stock counts are wrong so we over-order.”
- Put a rough number on eachFour lost enquiries a week at a £500 average order is around £8,000 a month.
- Fix the biggest number firstNot the loudest department; the biggest number.
- Check what you already pay forCan an existing tool, configured properly or connected by automation, fix it before you buy or build anything new?
- Start with the smallest release that moves the numberOne module or one automation, live in weeks, measured against the figure from step 2.
- Connect outward from thereThe second system is cheaper because the data already exists.
Then match the problem to a starting point:
| If you are losing… | Typical symptom | Start with |
|---|---|---|
| Revenue | Slow or missed follow-up, leads in inboxes, no pipeline view | A CRM and follow-up automation |
| Margin inside operations | Wrong stock, over-ordering, jobs that lose money unnoticed | The ERP module nearest the leak, usually stock or purchasing |
| Time | Retyping, chasing, monthly report marathons | Automation between the tools you already have |
| Calls and enquiries out of hours | Voicemails, lost bookings, slow callbacks | An AI agent on the phone or website, connected to your calendar and CRM |
Our ERP vs CRM guide covers the choice between the two biggest systems in more detail. If the leak is revenue, the fix is often process before software: see how to automate lead follow-ups, and for where new enquiries should come from, how to generate qualified leads for a small business.
A practical business software checklist
In short: ten checks to run before you buy, renew or build anything.
- List every tool you pay for, its monthly cost, how many seats are actually used, and its renewal date.
- List every spreadsheet that is updated weekly or more, who updates it and why the main system cannot do it.
- Write down where each type of data lives: customers, orders, stock, invoices, staff. Mark anything held in two places.
- Map one end-to-end process, from enquiry to paid invoice, and mark every point where someone retypes data.
- Put a monthly cost on your top three problems: lost sales, wasted hours or margin leakage.
- For each problem, check whether an existing tool can solve it with better configuration or an integration first.
- Decide buy, build or hybrid per process, not for the whole business at once.
- For anything new, confirm it has an API and connects to your accounting package.
- Check security and ownership: individual logins, MFA, backups, data location and who owns the accounts and code.
- Agree the one number that should move, and review it 30 and 90 days after go-live.
How to choose a software partner
In short: ask what you will see working and when, who owns the code, and what they would advise you not to build.
Whether you are configuring a packaged tool or commissioning custom business software, ask these before you sign:
- What will I see working, and when? A serious answer is a working first release in a couple of weeks, not a three-month silence.
- Which business number should move? If nobody will name a metric, nobody is accountable for it.
- Who owns the code and the data? It should be you, in writing, in a repository and cloud account in your name.
- What happens to our existing data? Migration is where timelines die. Ask for the plan.
- What does year two cost? Hosting, support and changes. A cheap build with an expensive support contract is not cheap.
- How will it connect to what we keep? Name your accounting package, your e-mail and your payment provider.
- What would you advise us not to build? A supplier who says yes to everything is selling hours, not outcomes.
Red flags: a fixed quote before anyone has asked about your process, no demos until the end, a feature list instead of your workflows, and a “big bang” launch that switches every team over one weekend. Our guide on how to choose a software development company goes further.
The short version
In short: standard tools for standard jobs, custom where you are different, everything connected.
Use proven off-the-shelf tools for accounting, e-mail and payroll. Put a CRM in place before leads start slipping. Build custom only where your process is genuinely yours, and connect everything so nobody retypes data. Then fix the next most expensive problem.
DataVolve has been building business software since 2021 and has delivered 75+ projects. We build custom business software for SMEs in the UK and US, including custom CRM systems and AI automation, usually alongside the tools a business already runs. You own the code, cloud accounts and domain from the first commit, you see a working demo every week, and you get a written, scoped plan within 24 hours of a call. If you want a second opinion on what to do first, tell us what is slowing you down.