Custom Business Software: When It Pays Back, and When Not

Custom business software is built around one company’s way of working: its quoting, its scheduling, its production, its service. Done well, it removes manual steps, prevents errors and lets the business do things competitors cannot. Done in the wrong place, it costs more than the product it replaced. GBCORP estimates payback in the scoping week, in figures the business recognises, before recommending a build.

The payback estimate

Cost of ownership over five years

Building is often less than half of what software costs over its life. Hosting, support, security updates, small changes and occasional larger releases continue every year. A sound estimate shows all five years. Software built on a maintained engine costs less to own, because shared parts are kept current for every client rather than paid for by one.

When custom software does not pay back

When the process is the same as everyone else’s and a product already does it. When volumes are small, so hours saved are few. When the process is still changing every month and the software would chase it. In those cases GBCORP recommends a product, a configured platform or waiting, and says so in writing.

Checklist for a payback estimate

• Count the hours the process takes each week, by role.
• Count errors per month and what each costs.
• List work the business turns away today.
• Get a fixed quotation for the first release.
• Ask for running costs over five years, not one.
• Set the month by which payback should show.

The numbers to expect

Scoping in one week, priced on its own, ending with a payback estimate and a fixed quotation. A first release in eight to twelve weeks. Support at a known monthly figure. A payback review six months after launch. Customised or more complex functionality is quoted separately before any work starts.

A worked example

Consider a print company that prepares quotes by hand from a price book and a calculator, taking an estimator half an hour per quote and producing errors that show up as lost margin. The payback estimate counts estimator hours, the cost of quoting errors found in credit notes, and quotes not sent because estimators were busy. A quoting tool with the price book built in is quoted at a fixed price. The estimate shows payback within the first year; the six-month review confirms faster quotes, fewer errors and more quotes sent.

Revenue the business could not take before

Payback is not only savings. Custom software often lets a business take work it previously turned away: quotes answered the same day, orders accepted outside office hours, customers served in more locations without more staff. These gains are harder to estimate, so GBCORP counts only the work the business can show it lost, and treats anything beyond that as upside.

Owning what was paid for

Custom software is an asset only if the business owns it. Code in the business’s repository, documentation, tests, cloud and data in its name: these make the software maintainable by any competent team and keep its value on the business’s side of the balance sheet. Without them, the business has paid for a dependency.

Lower running costs on an engine

Sign-in, payments, notifications, consoles and store compliance on GBCORP’s engine are maintained once for every client. A business pays for its own features, not for the upkeep of the parts every system needs.

Changing the software as the business changes

Businesses change, and their software must follow. Rules that change often are designed as console settings rather than code, so the business adjusts them without a release. Larger changes are releases, priced before they start.

Measuring after launch

The figures used in the payback estimate are measured again after launch: hours, errors, work accepted. The six-month review compares them with the estimate, and the next release is chosen by the same method.

Ownership terms

Code in a repository the business controls, documented with every release. Cloud, data, domain and accounts in its name. No credentials retained by GBCORP after a hand-over unless a support contract requires them.

Comparing with a product subscription

A fair comparison sets five years of a product subscription, including the extra staff time its gaps cause, against five years of custom software, including building and running it. Sometimes the product wins clearly. When the gaps cost hours every week, custom software often wins within the five years.

Questions we hear first

How fast should custom software pay back?

It depends on the process; a well-chosen first release often shows its saving within the first year.

Can we start small to test the estimate?

Yes. The first release targets the largest saving, and its figures test the estimate before more is built.

What makes custom software last?

Tests, documentation, a maintained engine underneath and code in your own repository.

What if the estimate is wrong?

The six-month review shows it, and the next release is redirected or the project stops.

Where to start

The GBCORP software development hub sets out the method; the GBCORP Custom App Development product is the priced starting point. For how custom work is scoped and owned, read custom software development, scoped, priced and owned.

GBCORP operates across 17 countries on 4 continents through six pillars: AI & IT, Innovation, Sustainability, Infrastructure, Premium Business, and EV's & Solutions.