Custom software or off the shelf: how to choose

Choose software by testing it against the work your business needs to do. A ready-made product may cover that work well. You may need a connection between the tools you already use. A custom application becomes worth considering when important requirements remain difficult to meet.

These options can sit together. Your business could use Microsoft 365 for email and documents, an accounting product for finance and a custom application for a particular customer service or internal process.

Test an existing product with your own examples

Give a supplier a realistic task and ask them to demonstrate it from beginning to end. Include the people who will use the software. A demonstration with your products, records and approval steps tells you more than a tour of every available feature.

Check what is included in the proposed plan. A feature may require a different licence, a paid extension or a separate implementation project. Ask who configures it, trains the team and supports it once it is in use.

An existing product is often a sensible choice for an established task such as email or accounting. Confirm the fit and the service around it, including access to your data if you later move.

Look at connecting what already works

Sometimes the problem sits between two systems. Staff may be copying a completed shipment into accounting because the information does not move across on its own. Replacing either system could add disruption without addressing that gap efficiently.

For MTE Xpress, we developed a separate connection between Shiplogic and Sage for invoice synchronisation. Review, retry and catch-up controls help deal with records that need attention. The business kept the existing logistics and accounting tools while adding a connection for a specific operational need.

Before choosing this route, check the providers’ supported interfaces, access permissions and limits. Include the handling of failed or repeated requests in the scope. Our guide to business system integrations explains those decisions.

When does a custom build make sense?

A custom build is worth exploring when the experience or process you need is central to the business and available products leave substantial gaps. Describe those gaps precisely: who is affected, how often it happens and what the current workaround involves.

ViaVia needed a product built around community travel, with invitations, trust connections, journey requests and trip chat. We developed the website and app while connecting external services for parts such as authentication and subscriptions. The delivered product combines custom work with existing services.

A store can use the same approach. BigBore combines a custom storefront and management work with Medusa commerce and connected payment, accounting, delivery and email services. “Custom” describes the work needed around the business; it does not mean every underlying component has to be invented.

Compare the whole commitment

Ask for a breakdown of setup, configuration, data migration, integrations, training and recurring services. For custom development, include hosting, third-party subscriptions, maintenance and future changes. Custom software can still depend on licensed services and outside providers.

Compare the support arrangements too. Who fixes a problem that crosses two systems? Who applies updates? How are changes reviewed before they reach customers? Include these responsibilities in the agreement.

Security needs attention in either route. A custom application is not automatically safer than a commercial product. Consider the information involved, access controls, development and update practices, and the recovery arrangements appropriate to the work.

Questions to answer before you choose

• Can the proposed solution complete our most important tasks?
• Which requirements need configuration, an extension or new development?
• Can the required systems connect through supported methods?
• Who controls the accounts, data and any custom source code under the agreement?
• What are the recurring costs and support responsibilities?
• How would we export our records or change provider?

If you are weighing up options, bring your current tools and a few examples of the work they need to support. We can review the gaps through our custom software service or existing software improvement service before agreeing the next step.