The three practical options
- Keep existing software
The product already solves the important problem and the remaining inconvenience is small. - Connect existing software
The products work individually, but people copy information or coordinate steps between them. - Build something bespoke
The available products force the business into a poor workflow or cannot support a valuable requirement.
There can also be a hybrid answer: retain established products for jobs such as accounting or CRM, then build a focused portal or workflow around them. The decision should start with the business process rather than a preference for a particular technology.
How do integration and bespoke software compare?
| Area | Keep existing software | Integrate products | Build bespoke software |
|---|---|---|---|
| Initial cost | Usually lowest if no material change is needed. | Depends on APIs, data and workflow complexity. | Usually the largest initial commitment because the application must be designed, built and tested. |
| Implementation | Configuration and process changes may be enough. | Requires mapping, rules, failure handling and testing across suppliers. | Requires discovery, design, development, data work, testing and launch. |
| Fit | Limited to the product's intended model. | Improves flow between products but does not remove their individual constraints. | Can follow the business workflow closely where that difference is valuable. |
| Control | The supplier controls the product roadmap. | You control the connection, subject to both suppliers' APIs and terms. | You can control the application roadmap, within the ownership and licence terms agreed. |
| Maintenance | Mostly subscription, configuration and user administration. | The connection needs monitoring and changes when either side changes. | The organisation owns hosting, maintenance, support and future development decisions. |
| Vendor dependency | Dependent on one main product. | Dependent on connected products and their interfaces. | Less tied to a product workflow, but dependent on maintainable code, infrastructure and capable support. |
When should you keep the software you already have?
Keep it when it performs the core job reliably, staff can use it and the remaining manual work is occasional or needs human judgement. A configuration change, better training or a simpler process may produce more value than a technical project.
Existing products can bring mature features, documented processes, regular updates and a broad support base. Replacing those advantages to remove a minor inconvenience is rarely a sound case for bespoke development.
When is integration the right answer?
Integration suits a sound process spread across capable products. Typical examples include sending website enquiries into a CRM, passing approved orders to accounting software, or returning booking availability to a customer-facing website.
- Each system has a clear role and remains worth keeping.
- The same data is copied or checked repeatedly.
- A reliable API, export or supported connector exists.
- There is a clear source of truth for shared records.
- The time saved and errors avoided justify ongoing monitoring.
Check the practical factors that affect software integration cost before assuming that two familiar products will be simple to connect.
When is bespoke software worth considering?
Bespoke software becomes relevant when the workflow itself is distinctive, important and poorly supported by available products. It may bring customer, staff and administration tasks into one system, enforce business rules, preserve an audit history or expose a focused portal.
It is a weak choice where requirements are unclear, the process changes every week, an established product already fits, or the organisation cannot own ongoing decisions and maintenance. The wider bespoke versus off-the-shelf comparison covers those trade-offs in more detail.
A simple decision framework
- Describe the outcome: what should become faster, clearer or more reliable?
- Map the current workflow: include hand-offs, repeated entry, decisions and exceptions.
- Check the products: can configuration or one better product solve it?
- Test integration: do the retained systems expose the data and actions required?
- Value the gap: is the unresolved problem important enough to justify bespoke ownership?
- Compare the full life: include subscriptions, integration monitoring, hosting, maintenance and future changes.
If repeated work is the trigger, first review the signs that manual administration has become excessive. Explore Automation & Integrations for connecting suitable systems, or Bespoke Applications where a purpose-built workflow is justified.