What we mean by small business here
'Small business' covers everything from a two-person workshop to a company with a few hundred staff. This guide is mostly about the upper part of that range: companies with roughly 20 to 300 people, several roles, more than one location or team, and a daily operation that has outgrown the tools it started with.
If you're under ten people, custom software is rarely the right first move. Good off-the-shelf tools, used well, will carry you a long way. We'll say that more than once in this guide, because it's true, and because buying custom too early is one of the most expensive mistakes a small company can make.
When custom software makes sense
Custom pays back when the way your company works is specific, and the tools you have keep forcing people to work around them. These are the common signals.
- The company runs on spreadsheets that only one or two people fully understand.
- Work moves between roles through chat groups, email threads and phone calls, and things fall through the gaps.
- You pay for several SaaS tools that each cover part of the process, and people copy data between them every day.
- You can't answer basic questions, like who hasn't paid or which jobs lose money, without someone building a report by hand.
- Your process is part of why customers choose you, and standard tools would make you work like everyone else.
- Field staff, managers and the office need very different views of the same work.
- You're planning to grow, and the current setup would need more admin staff just to keep up.
When it doesn't
Custom is the wrong answer more often than people in our industry admit.
- Your process is standard, and a well-known tool already does it well. Accounting is the classic example.
- You haven't yet settled how you want to work. Build after the process stabilises, not before.
- The problem is discipline, not tools. If people don't update the current spreadsheet, they won't update a new system either, unless it's much easier.
- The payback isn't visible on paper. If you can't point to hours saved, mistakes avoided or growth enabled, wait.
- You don't have anyone who can own the project on your side for a few hours a week.
What small businesses usually build
Every system is different, but most custom projects for companies of this size take one of a few shapes, often combined into one system.
- An information system: the operational backbone, covering jobs, projects, sites, stock, documents and approvals, with a clear owner for each step.
- A CRM: leads, deals, clients and follow-ups built around how you actually sell, connected to the work that follows the sale.
- An HR system: hiring, onboarding, shifts, attendance, leave and payroll preparation, with a phone view for staff.
- A client portal: customers see their orders, jobs, documents and invoices without calling the office.
- AI staff: a receptionist that answers calls, a caller that works lead lists, a clerk that files, invoices and chases payments.
- Internal tools: smaller utilities for one team, like a quoting calculator or an inspection checklist.
Your options compared
There's more than one way to get software built. Each has a place, depending on your budget, your appetite for risk and how central the system is to the business.
- A stack of SaaS tools. Upfront: low. Ongoing: subscriptions per user and per tool. Fit: good for standard processes. Risk: data scattered, integration work never ends, costs grow with headcount.
- Low-code or no-code, built in-house. Upfront: low. Ongoing: platform fees. Fit: good for simple workflows. Risk: depends on one enthusiastic employee; permissions, performance and lock-in become issues as usage grows.
- A freelancer. Upfront: lower than an agency. Ongoing: hourly. Fit: good for bounded tasks. Risk: single point of failure, availability, and limited coverage of design, security and data migration.
- A software agency, hourly billing. Upfront: estimate, not a price. Ongoing: hourly. Fit: can be good. Risk: budget drift, long discovery phases, and you pay for the learning curve.
- A software agency, fixed price with early working software. Upfront: a fixed number per phase. Ongoing: support plan. Fit: exact. Risk: you need to choose the partner well and own the code.
- An in-house developer. Upfront: recruitment. Ongoing: salary. Fit: good once software is core to the business. Risk: one person carrying the whole system, and hard to hire well without technical knowledge.
How the process should look
A good custom software project for a small business is short, concrete and visible. If you're weeks in and haven't clicked anything, something's wrong.
It starts with the real material: your spreadsheets, chats, forms and exports, shown on a shared screen. The builder maps how work actually moves and where it gets stuck. From that, a fixed scope and price: roles, hand-offs, integrations and data migration, written down.
Then something working, fast. With us, a first working version on a sample of your own data lands within 24 hours of kickoff. It's small but real. From there the system grows in short loops, with the people who'll use it clicking through each new part. Data gets migrated and checked, one team goes live first, the others follow, and a support period covers the first months of real use.
Our article on the custom software development process goes through each step in more detail.
How long it takes
Timelines depend on scope, but for a small or mid-sized business they should be measured in weeks, not years. A single-company system with up to five roles is typically live in three to four weeks with us. A full system with the AI layer, integrations and a client portal takes six to eight weeks. Groups of companies are rolled out in phases.
The main thing that slows projects down is rarely the build. It's waiting for decisions, data and feedback. Having one person on your side who can answer questions within a day makes more difference to the timeline than anything on the builder's side.
Be wary of the opposite problem as well. A quote that promises a full company system in a few days is either a template with your logo on it or a demo that will need months of work to become real. A first working version in 24 hours is possible because it's deliberately small; the full system still needs weeks of careful work with your team.
What it costs
Custom software costs are driven by roles, hand-offs, integrations, data migration and whether there's an AI layer. For small businesses, market prices range from a few thousand for a single internal tool to six figures for group-wide systems.
Our prices are public. Core is €18,000 for one company, one system, up to five roles, full data migration, phone and desktop access, an owner dashboard and three months of support. Maxxed is €48,000 for unlimited roles, the AI layer, up to four integrations, automations, a client portal and six months of support. Empire starts at €120k for groups of companies. Extra integrations are €4,500 each, and Maxxing Care is €2,900 per month after the support period ends.
To be direct: if your whole problem could be solved by a €50-a-month tool, Core is too much. It's designed for companies where the current chaos costs more than that every year, in staff time, mistakes and missed revenue. Our article on how much custom software costs explains how to run that comparison for your company.
How to reduce the risk
The fears around custom software are reasonable. Each has a practical answer.
- 'We'll be locked in to the developer.' Own the code, the data and the documentation, and make sure hosting is in an account you control or can take over.
- 'The budget will explode.' Insist on a fixed price per phase, and a written definition of what counts as a change.
- 'Nobody will use it.' Involve the users from the first week and launch with one team before the whole company.
- 'Our data is a mess.' Budget for migration and cleanup; it should be part of the price, not a surprise.
- 'What if they disappear after launch?' Ask for a support period in the contract and a clear plan for afterwards.
- 'Is it secure?' Ask about access control, backups, audit logs and monitoring before signing.
What happens after launch
Launch is not the end of a custom software project. It's the point where real use starts showing what nobody thought of. The first three months usually bring a steady stream of small changes: a field that should be required, a report that needs one more column, a step that turned out to be unnecessary.
That's normal and healthy. It means people are using the system. What matters is that those changes are quick and already paid for. Our plans include three, six or twelve months of support and changes, depending on the plan, and Maxxing Care continues after that for companies that keep evolving.
Plan for the longer term too. Your company will change: new services, new locations, new rules. A custom system should change with it, which is one of the main reasons to build rather than buy in the first place.
Owning your code and your data
For a small business, ownership is the single most important contract point. The system will hold your clients, your prices, your people and your history. You need to be able to take it elsewhere if the relationship ends.
Check three things. The data is yours from day one, and you can export it in a usable format at any time. The source code and documentation are handed over when the project is paid. The hosting and domain are in an account you control, or can be transferred to you without the builder's permission. With us, all three are standard.
Security, hosting and hardware
A small business often has no IT department, so the software partner ends up responsible for more than the code. Make sure someone owns hosting, backups, updates and monitoring, and that you know who that is.
If the system replaces paper and spreadsheets in the field, people will need devices that work there. We can deliver laptops, phones, rugged tablets, scanners, network and servers, set up and connected to the system so everything works on day one. We also run security audits, hardening, access control and 24/7 monitoring for the systems your company depends on.
How to choose a partner
Look for someone who asks how your company works before talking about features, gives you a fixed number, shows working software early, and tells you when something isn't worth building. Ask to see real interfaces, even with invented data. Ask who will actually do the work. Ask what happens in the first two weeks.
Our hiring a software agency checklist has the full list of questions.
Where to start
Write down the five things that go wrong most often in your company, the tools and spreadsheets involved in each, and what they cost you in a typical month. That list is the first draft of your scope.
If you'd like to do it with us, apply and tell us how things run today. We'll map it, give you a fixed price, and show you a first working version on your own data within 24 hours of kickoff.