Custom Software Development Company: The Questions That Matter

A custom software development company builds software around one business rather than selling the same product to a thousand. That is the right answer for a process no product covers, and the wrong answer for a process a product already handles well. GBCORP does both, which is why its first advice is often to configure rather than build, and why the questions below start with whether custom is needed at all.

When custom is worth it

Judge a company by its own software

The best evidence a company can build software that lasts is software it runs itself. Ask which products they operate, how many users, how long in production, and what the last three releases changed. A company that only builds for others and never operates has never had to answer for the 2 a.m. failure. GBCORP runs its own products on the same engine it builds client software with, and says so because it is checkable.

How scope and price are fixed

A scoping week priced on its own, ending in a written scope, a fixed quotation and dated milestones. A fixed price per release, agreed before the release starts. Integrations priced as separate items. Customised or more complex functionality quoted separately before any work starts. A day rate with a rough estimate is not a price; it is an invitation to keep paying.

What ownership means

Code in a repository the client controls. Cloud project, domain, store accounts and payment-gateway account in the client’s name. Documentation another team could use. No credentials retained after a hand-over unless a support contract requires them. Data exportable at any time. Put in writing, not implied.

Checklist before choosing

• Ask whether custom is needed, and expect an honest no where it is not.
• Ask which software the company operates itself.
• Ask for the scoping week as a priced, stand-alone item.
• Ask for a fixed price per release and a support plan with response times.
• Ask who owns each account after launch.
• Ask how the software will be measured, before and after.

The numbers to expect

Scoping in one week. A first release in eight to twelve weeks at a fixed price. Releases every two weeks after launch. Support with response times in hours for critical issues. The priced starting point for a custom build is on the GBCORP e-shop, and the scoping week turns it into a number for the whole programme.

A worked example

A wholesaler prices every customer differently, by volume, history and negotiated terms, and no product handles it. The scoping week maps the pricing rules and the order flow and produces a fixed quotation in two releases: an ordering portal with the customer-specific pricing engine, then an integration with the accounting system. The portal is built on GBCORP’s customer-portal foundation, so accounts, documents and invoices are configured rather than built, and the custom work is the pricing engine and the order screens. The portal ships in ten weeks; orders by phone fall by most of their volume within a quarter because customers see their own prices and stock.

What a support plan should include

Monitoring, so the company knows about a failure before the client does. Patches for the libraries and platforms the software depends on. Operating-system and store updates where the software has a mobile app. A number of hours a month for small changes. Response times by severity, in writing: hours for a critical failure, days for a cosmetic one. A quarterly review of the numbers the software was built to move. A custom software development company that offers no support plan is offering a project, not a system.

Documentation as a deliverable

Every release ships with its documentation: what changed, how the data model looks, how the integrations authenticate, how to deploy. It is written for the next team, not for the current one, because the point of documentation is that the client is not dependent on the company that wrote the code. A custom software development company that keeps the knowledge in its developers’ heads is keeping the client in the building.

Starting small

The first release should cover the one process that hurts most, in the smallest form that works, so the business is using the software within weeks and the second release is planned from real use. Custom software development companies that propose a year-long first phase are proposing a year without feedback. GBCORP’s scoping week deliberately cuts the first release to what can ship in eight to twelve weeks, and the rest becomes a dated plan rather than a single large bet.

Questions we hear first

Is custom software more expensive than a product?

Per feature, yes. Per year, often not, because there is no per-seat licence and the software fits without workarounds.

Can custom software start from a white-label base?

Yes, and it usually should. The base is tested; custom releases cover only what differs.

Who maintains it?

GBCORP under a support plan, or the client’s team after a documented hand-over.

How do we avoid scope creep?

Fixed price per release, changes priced as releases, and a scope document everyone can point to.

Where to start

The GBCORP custom app development hub explains the routes; the GBCORP Custom App Development product is the priced starting point. For software at group scale, read enterprise software solutions explained.

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