Bespoke software or off-the-shelf: which fits your business?

When an existing product is the better starting point

If your requirement follows a common process, an established product may cover most of it. Compare what it can do today with your essential requirements, not a list of every feature you might want. Try the actual workflow with the people who will use it.

Check user permissions, export options, support, integrations and pricing as usage grows. A subscription price is only part of the cost: setup, moving data, training and maintaining workarounds also take time. Do not assume a feature is included because the product describes itself as a CRM or an all-in-one platform.

When integration is enough

You may already have useful tools that simply do not share information. Connecting a website form to a CRM, assigning an owner and notifying the right person can remove repeated work without replacing the whole system.

Before automating, define which system owns each piece of data. Decide how duplicates, failed requests and changed records will be handled. Check that the providers expose the required APIs and that their terms and usage limits support the intended workflow.

When bespoke software deserves consideration

A custom build is worth exploring when an important workflow cannot be supported well by existing tools, or when the customer experience itself is your product. Examples include a tailored configurator, a customer portal with specific permissions or an operational board connected to stock and approvals.

Bespoke software also creates responsibilities. Someone must own maintenance, monitoring, access control, backups and future changes. Establish these arrangements before the build. A custom system is not automatically cheaper, faster or more effective than a suitable existing product.

Compare the options using the same requirements

• Workflow fit: can a user complete the essential journey without a workaround?
• Integration: can the system exchange the required data reliably?
• Access: can customers, staff and managers see only what they should?
• Data: can you import existing records and export them if you leave?
• Total cost: include setup, licences, usage, maintenance, support and changes.
• Ownership: clarify access to accounts, code, documentation and infrastructure.
• Continuity: decide what happens if a provider, integration or developer becomes unavailable.

Define a small, complete first release

Choose one workflow from beginning to end, such as enquiry to reviewed quote. Define its users, required data, status changes and exceptions. A first release that completes one useful job is easier to evaluate than a collection of unfinished dashboards.

Agree acceptance criteria in everyday language. For example: a customer submits requirements, the team sees the record once, a responsible person is assigned, and failed notifications can be retried. Decide what evidence will demonstrate that the workflow works before expanding it.

Use a real project to make the discussion concrete

GAJO’s Mobile Tyre Van City work connects a customer website and configurator with CRM and operational processes. It is an example of a business-specific journey extending beyond a brochure website. The case study describes the system and distinguishes enquiry value from completed sales.

For your project, bring the current process, the systems involved and the most frustrating handovers. We can discuss whether an integration, an existing product or a bespoke application is the appropriate next step. Scope, costs and support arrangements are agreed around those requirements.