Custom system or off-the-shelf tool? Start with the process.

An off-the-shelf tool can be an excellent choice. If it handles a core process, offers the integrations you need and lets the team work smoothly, there is no reason to rebuild it just to own the code.

The question changes when the company routinely works around the system. Data gets retyped, quotes get priced in a side spreadsheet, and delivery status gets confirmed by phone. That is the moment to ask how many of those workarounds are habit and how many come from a genuine mismatch.

Describe one complete scenario

Pick a process — say, from a client enquiry through to a finished job. Write down who takes part, what data they hand over and where the delays or mistakes appear. Only then map the features you need onto it.

Compare three routes

The first is configuring the current system better. The second is integrating your tools or adding a small supporting module. The third is a custom application. Compare them on the same scenario, and include migration, maintenance and how changes get made.

Define the scope of the first stage

A first release should close a useful process. A list of screens is not enough: decide what a user must be able to do end to end, and how you will tell whether the new way of working is genuinely better.

Prepare material for the conversation

Sample forms, an anonymised data export and a description of the daily friction are usually more useful than a long list of technologies. They help judge whether you need a new application or a well-planned change to what you already run.