# Build, buy or customise enterprise software?

> Build, buy or customise: three routes to enterprise software for a dealer-led business, what each costs after go-live, and how to test one first.

The business OS · The Intellsys team · 18 November 2026 · 6 min read

Building enterprise software gives a business exactly what it asks for, and it then owns that code for ever. Buying gives a finished product that works its own way. Customising starts from a configurable platform and shapes it to the business's own journeys, roles and territories. For a business that sells through dealers, the right choice depends on how different its process really is, and who will keep the system running in year three.

## The short answer

- Build when the process is your advantage and you can staff a team to maintain it for years.
- Buy when your process is close to how most businesses work and you are willing to adapt to the product.
- Customise when your journeys, roles and territories are your own but the parts underneath are common.
- Compare the cost of year three, not the cost of go-live.
- Test any route on one real journey with real dealers before signing for the whole network.

## Build, buy or customise: the three routes in plain terms

The words are used loosely in proposals, so pin them down first.

| Route | What you get | What you give up | Who keeps it running |
| --- | --- | --- | --- |
| Build | Software made to your exact process | Time to first use, and every future change | Your own team or a contracted one, for as long as it lives |
| Buy | A finished product, ready to use | Your process, wherever it differs from the product's | The vendor, on the vendor's roadmap |
| Customise | A configurable platform shaped to your journeys and roles | Some freedom at the edges, where the platform has its own shape | The platform owner for the core, with your configuration on top |

None of the three is the grown-up answer. Each is right for some businesses and expensive for others.

## When each route is right for a dealer-led business

The question underneath is how much of your process is genuinely yours. It is easy to overestimate, and worth asking someone outside the sales team.

- **Build: the process is the product** Your way of selling is why customers choose you, and nothing configurable comes close.
- **Build: you can staff it** You can keep engineers on it for years, not only for the launch.
- **Buy: you sell like most** Your enquiry, quote and order steps match how the product already works.
- **Buy: speed matters more than fit** You need something working this quarter and will adapt your teams to it.
- **Customise: your structure is unusual** Dealer roles, territories and journeys differ, but leads, quotations and catalogues are common parts.
- **Customise: you need many views** Head office, dealers and the field each need their own screens on the same records.

*Six signals for each route. Most dealer-led businesses find their structure is unusual while the parts beneath it are not.*

A vehicle maker's journey from enquiry to test ride to booking to retail is its own. The lead form, the call log and the quotation underneath it are not. That combination is the usual case for customising. The steps of that particular journey are in [the test ride booking process](https://intellsys.cloud/blog/test-ride-booking-process).

## The costs that arrive after go-live

The proposal shows the launch. The real cost of enterprise software shows up later, as the business changes and the system has to follow.

- **Month one** Every route looks fine. The first dealers are onboarded and the team is watching closely.
- **Month six** The business adds a new role, such as a regional manager for a new state. Who changes the system, and how fast?
- **Year one** A new product line needs new forms and dispositions. A bought product may not allow them; a built one needs a release.
- **Year two** The engineer who wrote the dealer module leaves. A built system now depends on whoever can read the code.
- **Year three** The vendor changes its pricing or roadmap, or the platform ships an upgrade. Your configuration has to move with it.

*Where the cost of each route shows up after launch. The year-two and year-three questions decide most choices in hindsight.*

Ask every option to answer the month-six question in writing: who makes the change, how long it takes, and what it costs.

## How to test a route before you choose it

A slide deck cannot tell you how a system behaves when a dealer in a small town uses it on a phone at seven in the evening. A short pilot can.

1. **Pick one journey** Choose the one that costs you most, often enquiry to dealer to sale.
2. **Use five real dealers** Mix a large city dealer with small-town ones, and their own staff.
3. **Change something mid-pilot** Add a disposition or a field, and time how long it takes to reach them.
4. **Move a territory** Shift a district from one dealer to another and check who sees what afterwards.
5. **Get the data out** Export the records and their history, to be sure you are not locked in.

*A five-step pilot that tests what each route costs to change, not only what it looks like on launch day.*

The third and fourth steps are the hardest to fake in a demonstration. They are also the ones that predict year three. When the pilot turns into a rollout, the onboarding work is the same whatever the route; it is laid out in [the dealer onboarding checklist](https://intellsys.cloud/blog/dealer-onboarding-checklist).

## Questions to ask before you sign

Whichever route you lean towards, put these to whoever will build, sell or configure it.

- [ ] **Who changes a form** Name the person and the time it takes to add a field for every dealer.
- [ ] **Who owns the code** Say who can fix it if the original team is gone.
- [ ] **What it sits beside** Confirm how it connects to the ERP and the systems you are keeping.
- [ ] **How access works** Show how a dealer sees only their own territory's records.
- [ ] **What happens at upgrade** Explain how your configuration survives the next version.
- [ ] **How you leave** Show the export of every record and its history.

*Six questions that separate a route that fits from one that only demos well. Each answer should be a name or a number.*

The difference between the kinds of system you might end up with is set out in [business operating system vs CRM vs ERP](https://intellsys.cloud/blog/business-os-vs-crm-vs-erp), and the wider idea in [what a business operating system is](https://intellsys.cloud/blog/what-is-a-business-operating-system).

> **How Intellsys OS handles it.** Intellsys OS takes the customise route. Each business gets a workspace with the capabilities it needs switched on, or a customised platform built for it on Intellsys OS. As we put it: "It bends to your business, instead of bending your business to it."

## How Intellsys OS handles customisation

In Intellsys OS a business defines its own journeys, activities, forms, dispositions, roles and territories, and gets a workspace with the capabilities it needs switched on. Where a business needs more, a customised platform is built on Intellsys OS for it.

Ampere, for example, runs on ABOS, a customised platform built on Intellsys OS: the dealer journey from enquiry to test ride to booking to retail, a mobile app for sales officers, a support desk and a training app. A business switches on the modules it needs, and its own team shapes objects, forms, journeys and roles without code, so a new capability is a setting, not a project. How a workspace is set up is on [the workspace page](https://intellsys.cloud/platform/workspace).

## Questions people ask

### Is it better to build or buy enterprise software?

Build when your process is what makes you different and you can keep a team on it for years. Buy when your process is close to how most businesses work and you will adapt to the product. If your structure is your own but the parts are common, customise.

### What does customising enterprise software mean?

It means starting from a configurable platform and shaping it to your business: your journeys, forms, dispositions, roles and territories. The common parts underneath, such as leads, quotations and catalogues, come from the platform, so you are not writing them yourself.

### What is the hidden cost of building your own software?

The cost that arrives after launch: every change to forms, roles or territories needs engineering time, and the system depends on the people who know its code. When they leave, the business inherits software that few can safely change.

### How do you compare build, buy and customise fairly?

Run the same short pilot on each: one journey, five real dealers, one change made mid-pilot, one territory moved, and a full export at the end. Then compare what each route costs to change in year three, not what it costs to launch.

---

[Request a demo](https://intellsys.cloud/demo) · [Blog](https://intellsys.cloud/blog)

This is the Markdown version of https://intellsys.cloud/blog/build-buy-or-customise-enterprise-software. Intellsys is built by GrowthJockey, a full stack venture architect.
