For most Irish SMEs, the answer is to buy off-the-shelf software for anything that works the same way in every business, such as accounting, payroll, email and HR. Build custom software only for the workflows that make you different, or the ones no product handles without constant workarounds. In practice the strongest setup is usually a hybrid: standard tools at the core, connected by a thin layer of custom integration and automation.
Below: how to sort each of your systems into the right category, what each path costs over five years rather than the first quarter, and the Irish and EU factors that should shape the decision.
The short version: buy the commodity, build the differentiator
Every business runs on two kinds of process. The first kind is commodity. Your VAT returns, payslips and calendar invites work the same way as everyone else’s, and regulation often requires them to. Nobody wins customers because their payroll is bespoke. These areas have mature products built by teams of hundreds, already updated for Revenue’s latest rules, so building your own is almost always a mistake.
The second kind is differentiating. This is the way you quote a complex job, schedule technicians across three counties, assess a claim or onboard a new client. Doing it better than competitors is part of why you win work. Forcing it into a generic tool tends to erode that edge, because the tool encodes someone else’s idea of how the process should run.
The hard part is that most SMEs have a large grey zone between the two. A CRM is commodity until your sales process involves site surveys, engineering sign-off and a tender portal. At that point the CRM covers 60% of the job and staff fill the other 40% with spreadsheets and email. Most build vs buy decisions are really made in this grey zone, and it is where the third option below usually wins.
What off-the-shelf software really costs
Off-the-shelf software looks cheap because the price is visible and small. Take an illustrative example: a tool at €35 per user per month across 25 staff costs €10,500 a year. Over five years that is €52,500 before any price rises, add-on modules or the jump to the ‘business’ tier you need for single sign-on or audit logs. That can be excellent value; just compare it honestly against the alternatives rather than treating it as free.
The workaround tax
The larger cost is rarely the subscription. It is the hours staff spend bending the tool to fit the business: exporting to Excel, re-keying data between systems, keeping a ‘real’ list in a shared spreadsheet because the system’s version is never quite right. None of it shows on a P&L. If four people each lose half an hour a day to re-keying, that is 10 hours a week, or roughly one and a quarter working days. For a structured way to find these hidden costs, see our guide to identifying which business processes to automate first.
Lock-in and roadmap risk
When you buy, you also accept the vendor’s roadmap. The features you need may never arrive, while the ones you rely on can be deprecated or moved to a higher tier. Ask early whether you can export all your data, including history, attachments and audit trails, in a format another system can read. A vendor that makes leaving painful has more pricing power over you every year you stay.
Where off-the-shelf clearly wins
For accounting, payroll, email, document storage, e-signature and standard HR, buying is the right call nearly every time. These products absorb regulatory change for you, meet security standards most SMEs could not justify building to, and come with support. Building any of these yourself is a distraction from the work that actually earns money.
What custom software really costs
Custom software flips the cost profile. You pay a larger amount up front, own the result, and pay no per-seat fees. In exchange you take on responsibility for keeping it running.
The build is the smaller part
A focused internal tool, such as a quoting system that pulls from your price list and pushes to your accounting package, can be a matter of weeks for a competent team. A broad operational platform that replaces several products is a matter of months, and it is far riskier. The common mistake is not the build estimate but forgetting maintenance after launch: dependency updates, security patches, API changes in the systems it connects to, and new features as the business evolves.
Budget a meaningful slice of the original build cost every year for upkeep. If nobody owns that budget, the system decays into the legacy problem someone else has to untangle.
The bus factor
A common failure in SMEs is a custom system that one person understands, often a contractor or a self-taught staff member, and when they leave the knowledge goes with them. Any custom build should come with documentation, automated tests, version control you own, and hosting in an account in your company’s name. If a supplier hosts your system in their own cloud account and holds the only copy of the code, you do not own custom software. You rent it, with worse terms than SaaS.
Where custom clearly wins
Custom software is worth it when three conditions hold together. The process is central to how you make money, no product fits it without heavy workarounds, and the process is stable enough that you are not rebuilding every six months. Done well, custom systems become more valuable over time, because each new feature builds on clean data and well-understood logic. We explain that principle in how to build software systems that compound over time.
The option most SMEs should start with: buy and integrate
The build vs buy framing hides the option that usually delivers the best return. You keep the tools you already pay for and build a small amount of custom software to connect them and automate the work in between.
Consider a typical Irish services firm. It might run Xero or Sage for accounts, a CRM, Microsoft 365 and a job management tool. Each is fine on its own. The waste sits in the gaps, where a won deal is retyped into the job system, a finished job is retyped into an invoice, and a customer email is read, summarised and forwarded by hand. Integration code that moves data automatically through APIs or webhooks removes the re-keying without replacing anything. An AI agent can then handle the unstructured parts, such as reading inbound emails, extracting purchase order details or drafting replies for human approval.
This approach has three advantages. It is cheap relative to a full rebuild, it is reversible because you can swap out any one tool without collapsing the rest, and it leaves vendors to carry the commodity burden. The custom layer stays small enough to understand, test and hand over. Older systems without modern APIs are still workable; our piece on integrating LLMs into legacy enterprise systems covers the patterns.
Custom software vs off the shelf: side-by-side
| Factor | Off-the-shelf | Custom build | Buy and integrate |
|---|---|---|---|
| Upfront cost | Low | High | Low to moderate |
| Ongoing cost | Per-seat fees that rise with headcount | Maintenance and hosting, flat with headcount | Subscriptions plus light maintenance |
| Time to value | Days to weeks | Weeks to months | Weeks |
| Fit to your process | Generic; you adapt to it | Exact, if specified well | Good; gaps closed by automation |
| Regulatory updates | Vendor handles | You handle | Vendor handles core; you handle glue |
| Lock-in risk | Vendor lock-in | Supplier or key-person lock-in, unless you own code and hosting | Lower; components are swappable |
| Competitive edge | None; competitors buy the same tool | High where the process differentiates | Moderate to high |
A build vs buy checklist for Irish SMEs
Run each system or process through these questions. Answered honestly, the decision is usually obvious.
- Is this process the same in every business like ours? If yes, buy. Stop here.
- How much time is lost to workarounds today? Measure it in hours per week, not impressions. If the figure is small, the current tool is good enough.
- Can the gap be closed by integrating tools we already have? If your existing products have APIs or webhooks, integration is usually the cheapest fix.
- Is the process stable? If it changes every quarter, keep it in configurable tools until it settles.
- Who will own it in three years? Name the person or supplier and the maintenance budget before you build anything.
- Do we own the code, data and hosting account? If you will not, renegotiate or walk away.
- Where does the data live, and who processes it? Map this for GDPR before choosing, not after.
- What does a five-year total cost look like for each option? Include subscriptions, price rises, staff time, maintenance and the cost of switching later.
Irish and EU factors that change the maths
GDPR and data residency
As a controller, you are responsible for how personal data is processed, whether the software is bought or built. With off-the-shelf tools, check where data is hosted, which sub-processors the vendor uses, and whether a proper data processing agreement is in place. With custom software you control these choices directly, which can be an advantage if you handle sensitive client data and want everything kept in an EU region. The Data Protection Commission publishes guidance for Irish organisations. We cover the AI-specific angles in data security and privacy in AI projects.
The EU AI Act
If your custom system or a purchased tool uses AI to make or support decisions about people, such as hiring, credit or access to services, the EU AI Act may impose obligations depending on the use case and risk category. Most SME automation, like summarising emails or extracting invoice fields, sits at the low end of that spectrum. Classify each use case early anyway; designing in human review and logging from the start is far cheaper than retrofitting them.
Grants and supports
Irish SMEs have access to state supports for digitalisation and innovation through Enterprise Ireland and the Local Enterprise Offices. Eligibility and amounts change, so check current schemes directly before planning. Do not let a grant drive the decision, though. A subsidised system that does not fit your process is still a poor investment. For why a small, well-built system keeps paying off after the grant is spent, see how to build software systems that compound.
Failure modes to avoid
The first failure mode is the big-bang replacement. A business blames its patchwork of tools and commissions one custom platform to replace them all; eighteen months later it is over budget, half-finished, and staff still use the old tools. Replace one process at a time, and keep the old system running until the new one has proven itself.
The second is specifying the current mess. Teams often document how they work today, workarounds included, and ask for software that reproduces it. Fix the process first, then automate the fixed version.
The third is buying for features you will never use. Enterprise suites demo beautifully, but if your team uses 15% of the product, you are paying for the other 85% and absorbing its complexity in every screen.
The fourth is treating AI as a separate project. AI agents are most useful inside existing workflows, attached to the systems where the data already lives. If your integration layer is clean, adding AI is a small step. If your data is spread across untracked spreadsheets, no model will save you.
How D3X Solutions LABS helps
We are a Dublin engineering studio, and we usually start where this guide ends: with a map of your current tools, the hand-offs between them and the hours lost in the gaps. From that map we recommend, process by process, whether to keep, buy, integrate or build. Often the honest answer is that you need less custom software than you expected.
When building is the right call, we keep the custom layer small and well tested, running in cloud accounts you own, with code in your repository and documentation good enough for another team to take over. Our work covers integrations between existing SaaS tools, AI agents for unstructured work such as email triage and document extraction, and orchestration that ties them into one reliable workflow, designed with GDPR and the AI Act in mind from day one. For the reasoning behind keeping that layer small, see building software systems that compound.
If you are weighing a build vs buy decision right now, book a free 30-minute call. Bring one process that frustrates your team, and we will tell you plainly whether to buy, integrate or build.
Frequently Asked Questions
Is custom software worth it for a small business in Ireland?
It is worth it when the process is central to how you make money, no product fits it without heavy workarounds, and the process is stable. For commodity functions like accounting or payroll, off-the-shelf is almost always better. Many SMEs get the best return from small custom integrations between tools they already use.
How much does custom software cost compared to off-the-shelf?
Off-the-shelf has low upfront cost but per-seat fees that grow with headcount and rise over time. Custom software costs more up front but has no seat fees, though you must budget for ongoing maintenance every year. Compare a five-year total cost, including staff time lost to workarounds, rather than first-year price.
What is the difference between build vs buy and buy and integrate?
Build vs buy treats the choice as either replacing tools with custom software or accepting a product as it is. Buy and integrate keeps your existing products and adds a small custom layer that moves data between them and automates the manual steps. It is usually cheaper, faster and easier to reverse.
Who owns the code when a developer builds custom software for my business?
Ownership depends entirely on your contract, so make sure it assigns intellectual property in the code to your company. You should also hold the code repository and the hosting account in your company’s name. Without those, you are effectively renting the system from your supplier.
Does GDPR affect whether I should build or buy software?
GDPR applies either way, because you remain responsible as controller for personal data. With off-the-shelf tools, check hosting location, sub-processors and the data processing agreement. With custom software you choose these directly, which can help if you need data kept in the EU.
Are there grants for software development for Irish SMEs?
Enterprise Ireland and the Local Enterprise Offices run supports for digitalisation and innovation, but schemes and eligibility change over time. Check their current offerings directly before planning a project. Choose the right solution first and treat any grant as a bonus rather than the reason to build.
Want this working in your business?
D3X Solutions LABS builds AI agents and automation that pay back fast. Set up a free 30-minute call and we will map your first win together.
Get in touch
