Custom software
or off the shelf?

Start with the work, then choose the software.

Ready-made software gives you an existing product to configure. Custom software is designed around your operation. Both can be sensible choices for a small or medium-sized business. The useful question is whether your essential work fits the product, and what happens when it doesn’t.

Before booking demonstrations, follow one real job through your business. For a distributor, that might be an enquiry becoming a quote, an order, a stock reservation, a delivery and an invoice. Note who handles each step, where information is copied, and which exceptions need the owner’s attention. Include returns and mistakes, because those often reveal more than the normal path.

Split what you find into three groups: essential to operate, useful to improve, and nice to have later. Be specific. “Inventory management” is broad; “reserve the same item across two branches without promising it to two customers” is a testable requirement.

Where each option makes sense.

Choose ready-made when the fit is already good.

If an established product handles your essential tasks with reasonable configuration, it may be the most practical route. A small team with straightforward workflows may get more value from a clear process and a well-configured existing tool than a new build.

Consider custom when workarounds are part of every day.

A custom system becomes worth exploring when several tools leave gaps between teams, important exceptions happen frequently, or people spend substantial time copying and reconciling information. The case is stronger when those gaps are measurable and your team can explain the process you need.

There is also a middle option: keep a specialist tool that works well and build around the missing workflow. For example, you might connect order handling to an existing accounting package. Any connection should be checked for supported access, costs and reliability before it becomes part of a proposal.

Compare the full cost over the same period.

A monthly subscription and a development proposal are different shapes of spending. Compare both over a period that suits your planning, with the same number of users and the same essential tasks. Ask each supplier to separate setup, ongoing fees, third-party charges and future changes.

• Getting ready: process mapping, cleaning records, moving data and staff time.
• Running it: subscriptions or hosting, support, backups, integrations and maintenance.
• Growing: more users, extra locations, higher usage and new workflows.
• Moving on: data export, documentation and assistance with a handover.

Measure today’s manual work too. As an illustrative example, three people each spending 30 minutes per working day copying information adds up to 7.5 hours in a five-day week. That is a starting point for investigation, not a savings promise: some review work should remain, and the new system will need oversight.

Make the demonstration about your business.

Give suppliers a short, anonymised example that follows your real process. Ask them to show the normal path and an awkward one: a partial delivery, a cancelled job, a return after payment, or a stock correction. Watch how many steps still happen outside the system.

Bring someone who does the work every day. They will spot details that an owner can miss, such as entering data on a phone, switching branches or finding an old customer agreement. Agree what a successful test means before the demonstration: which records must match, which approvals must happen and who needs to find the result.

For custom software, use a focused pilot to check the proposed workflow before expanding the build. Our design and delivery process explains how that moves from an initial map to a working system and team onboarding.

Questions worth asking before you sign.

1. Which of our essential tasks are included, and what will still happen elsewhere?
2. Who is responsible for moving and checking existing records?
3. Can we control what each person sees and changes, and review what happened?
4. Where is our data held, who can access it, and how are backups restored?
5. What happens when the system is unavailable or the usual support contact is away?
6. What do we own, what can we export, and what would a future handover involve?
7. How are requests for changes priced and agreed?
8. Who will train the team, and what support is included after launch?

Get the answers in the proposal or agreement. Terms such as “unlimited”, “fully owned” and “all included” need a clear explanation of scope and any recurring costs.

The right choice removes a specific constraint.

Choose the option that handles your essential work, has an understandable cost and gives your team a realistic route to adoption. If you cannot yet explain the problem or agree how to judge success, map the process first. More software will not resolve an unclear decision.

If the same information keeps moving between spreadsheets, start with our guide to replacing spreadsheets. If the workflow is already clear and standard tools leave important gaps, explore custom business software or tell us about the process you want to improve.