Menu

Custom software vs off-the-shelf software: how to decide, and who owns what you commission

Comingwave team · 7 minute read · published · updated

A manager standing at a glass wall covered in coloured notes, comparing two columns of options with a colleague.

Custom software vs off-the-shelf software is a choice between fit and speed. Off-the-shelf software wins when your process is like everyone else's and a proven product already does the job. Custom software wins when the way you work is different enough that standard products force workarounds, or when the software is itself part of what you sell. Most businesses end up with a mix. This guide covers when each wins, the full cost of ownership, lock-in, integration, and who owns software you commission in Australia.

What the two terms mean

Off-the-shelf software is a ready-made product, usually paid for by subscription, that many businesses use in the same form: accounting packages, email, payroll, standard CRMs and booking tools. You configure it. You do not change how it works.

Custom software is built for one business, to match its process, data and rules. It may be a complete system, or a smaller piece that connects or extends the products you already use.

When off-the-shelf software wins

  • The process is standard. Bookkeeping, payroll and email work the same way in most businesses. There is nothing to gain by building your own.
  • You need it now. A subscription product can be in use quickly, with no build stage.
  • Rules change often. Where tax or award rules shift, a vendor that updates the product for all its customers carries that work for you.
  • The upfront budget is small. You pay as you go instead of funding a build.
  • Others are already using it. Staff, bookkeepers and advisers may know the product, which shortens training.

When custom software wins

  • Your process is your advantage. A wholesaler with unusual pricing rules, or a transport operator with its own way of allocating jobs, loses something when it is squeezed into a generic product.
  • Staff are bridging gaps by hand. If people retype data between systems or keep side spreadsheets to cover what the product cannot do, that labour is a cost you are already paying.
  • No product covers the whole job. Some combinations, such as bookings, stock and delivery in one flow, are not sold as one package.
  • The software faces your customers. A marketplace, a booking platform or a client portal is part of your service, and you will want control over how it behaves.
  • Subscription costs are scaling against you. Per-user pricing that was reasonable for a small team can look different for a large one.

The middle path

The choice is rarely all or nothing. A common and sensible arrangement is to keep off-the-shelf products for standard functions, such as accounting and email, and commission custom software only for the part that is specific to you, connected to the rest through integrations.

Total cost of ownership

Comparing a subscription fee with a build quote is misleading, because neither is the full cost. Total cost of ownership means everything you spend to have the software working over the years you expect to use it.

Off-the-shelf costs

  • Subscriptions, which grow with users, features and plan tiers.
  • Setup, configuration and data migration.
  • Add-ons and third-party connectors.
  • Training.
  • Staff time spent on workarounds for what the product does not do.
  • The cost of leaving, if you later outgrow it.

Custom costs

  • Discovery, design, build and testing.
  • Data migration and training.
  • Hosting and monitoring.
  • Ongoing maintenance: security updates, fixes and changes as the business changes.
  • Your own time for decisions, feedback and acceptance testing.

Write both lists out for the same period and the same number of users. Off-the-shelf usually costs less at the start and keeps costing for as long as you subscribe. Custom costs more at the start and then settles to hosting and maintenance. Which is lower over time depends on your numbers.

Lock-in and data export

Lock-in is how hard it is to leave. Both options carry it in different forms.

With off-the-shelf software, your data sits in the vendor's format, under the vendor's price list and product roadmap. Before you commit, confirm that you can export everything, including history and attachments, in a common format or through an API (a documented way for two programs to exchange data), and find out what happens to your data if you cancel.

With custom software, the risk is dependence on whoever built it. That risk is managed by contract and by practice: you own the code, it is kept in a repository you can access, it is written in widely used technologies, the hosting accounts are in your name, and there is documentation another developer could pick up.

Integration

Whichever way you go, the software has to exchange data with the rest of the business: the accounting package, email, the website, reporting. Check which integrations a product offers ready-made and how complete they are, because a connector that only moves part of the data leaves the rest to manual entry. Custom software can be built to integrate exactly as you need, provided the other systems offer an API. Either way, decide which system holds the master copy of each kind of record.

A decision table

QuestionPoints to off-the-shelfPoints to custom
How standard is the process?Much the same as other businessesSpecific to you and central to how you compete
How soon is it needed?Straight awayThere is time to scope and build in stages
How is it funded?Ongoing subscription suits the budgetAn upfront investment can be justified
How many workarounds exist today?Few or noneSide spreadsheets and retyping between systems
How many users?A small or stable teamA large or growing number on per-user pricing
What must it connect to?Ready-made connectors cover itSeveral systems with specific data flows
Who uses it?Internal staff doing standard tasksCustomers, as part of your service

If the answers split, that usually points to the middle path: standard products plus a small custom piece.

Who owns commissioned software in Australia

Many business owners assume that paying for software means owning it. Under Australian guidance, that is not the default when a contractor writes it.

Software is protected by copyright. The Australian Government's copyright guidance on business.gov.au lists computer programs among the things copyright protects, and says protection is free and automatic under the Copyright Act 1968, with no registration needed.

On ownership, IP Australia's page Who owns intellectual property? says that employers own the IP their employees create in relation to the business, but that IP created by a contractor is the property of the contractor unless otherwise stated in the contract. The business.gov.au guidance on hiring contractors puts it the same way: if you want your business to own the IP rights, the contract must clearly say this.

So before commissioning software, make sure the written agreement covers:

  • who owns the code, designs and documentation, and when ownership passes to you
  • any third-party or open-source components and the licences they come under
  • any pre-existing code the developer reuses, and your rights to keep using it
  • access to the source code repository and the hosting accounts
  • who owns the data, and how it is handed over.

IP Australia recommends a signed written contract before work starts and professional advice before entering such agreements. This article is general information, not legal advice.

Where Comingwave fits

Comingwave is an Australian technology company that provides technology and business solutions to small and medium enterprises. We build custom software, connect off-the-shelf products through our business systems and integrations work, and help businesses weigh the options through IT consulting and digital transformation planning. Quotes are written and agreed before work starts, and clients own their code, data and documentation. To discuss which path suits you, request a free first consultation.

Key takeaways

  • Use off-the-shelf software for standard processes and custom software where your process sets you apart.
  • Compare total cost of ownership over the same period, not a subscription fee against a build quote.
  • Check data export before buying a product, and code ownership before commissioning a build.
  • In Australia, a contractor owns the IP they create unless the contract says otherwise.
  • A mix of standard products and a small custom piece is often the right answer.

Frequently asked questions

Is custom software always more expensive than off-the-shelf software?

It usually costs more at the start, because you fund the build. Over the full period of use the comparison depends on user numbers, subscription tiers, add-ons and the staff time lost to workarounds, so compare total cost of ownership before deciding.

Can I start with off-the-shelf software and move to custom later?

Yes, and many businesses do. Make the move easier by choosing products that let you export all of your data in a common format, and by keeping a written record of your process and the gaps you find.

Who owns software a contractor builds for my business?

IP Australia says IP created by a contractor is the property of the contractor unless otherwise stated in the contract. If you want to own the software, the written agreement must say so clearly.

What is vendor lock-in?

It is the difficulty of leaving a product or supplier. With subscription software it comes from data formats and pricing. With custom software it comes from depending on one developer. Data export rights, code ownership and documentation reduce it.

Can custom software work with Xero or MYOB?

Custom software can exchange data with other systems that offer an API. Agree which system holds the master copy of each record, and have the integration tested with realistic data before going live.

Need help with your business technology?

Tell us what you need. We reply within one business day.

Get a free quote