GBCORP BLOG · IT SERVICES
Custom Software Development: Scoped, Priced and Owned
Custom software development is three promises: the scope will be written down, the price will be fixed before work starts, and the result will belong to you. Here is how GBCORP keeps each one.
Custom software development builds software around one business’s process. GBCORP does it on a shared core that already handles accounts, payments, notifications, multilingual text, roles, audit and reports, so the bespoke work is the process itself: screens, rules, integrations. The method below is the same for a staff app, a portal, a console or a platform.
The method, stage by stage
| Stage | What happens | Note |
|---|---|---|
| Scoping week | Workshops, screens, data model, integrations, written scope, fixed quotation, dated milestones | Priced on its own |
| Foundation | Core configured, cloud project in the client’s name, brand applied | Weeks 2–3 |
| Releases | Two weeks each, priced before they start, a build the client uses | From week 4 |
| Integrations | Each scoped and priced as an item, logged, with fallbacks | In the relevant release |
| Launch | Migration rehearsed, go-live on a quiet day, old process kept warm | Weeks 10–12 |
| Run | Support plan, monitoring, patches, further releases | Ongoing |
Reused or bespoke
Reused: sign-in and password rules, payments to the client’s gateway, notifications and e-mail from the client’s domain, multilingual text and right-to-left layouts, roles, audit history, reports, the design system. Bespoke: the screens users spend their day on, the business rules and pricing logic, the integrations with the systems that stay. The client pays for what is theirs.
Fixed prices, no hourly rates
A price per release agreed before it starts. Changes priced as changes, never absorbed silently. Customised or more complex functionality quoted separately before any work starts. An hourly rate rewards slowness; a fixed price rewards finishing.
Documentation and ownership
Every release ships with what changed, the data model, how integrations authenticate and how to deploy, written for the next team. Code in the client’s repository. Cloud project, domain and accounts in the client’s name. No credentials retained after a hand-over unless a support contract requires them.
Checklist before the scoping week
- The process, as it runs today, with its exceptions.
- The people who do it, available for the workshops.
- Systems that stay and whether they have interfaces.
- Markets, languages and currencies.
- The measure of success, taken before anything changes.
- Who in the business owns the software afterwards.
The numbers to expect
Scoping in one week. First release in eight to twelve weeks at a fixed price. Releases every two weeks. Support with response times in hours for critical issues. Running costs listed in the quotation: cloud project, accounts, support plan. Prices on the GBCORP e-shop as the starting point.
A worked example
A laboratory receives samples from clinics, runs tests and returns reports, all tracked on paper and in three spreadsheets. The scoping week maps sample intake, testing, reporting and billing, and produces a fixed quotation in three releases: intake and tracking with barcode labels, then results and reporting to clinics through a portal, then billing with an accounting integration. Accounts, roles, the portal and documents come from the core; the sample workflow and the result formats are bespoke. The first release ships in nine weeks; the paper goes; turnaround time per sample is on the console and falls by a third within a quarter.
Migration and go-live
Existing records are mapped to the new model in the scoping week, migrated in a rehearsal on a copy, checked on a sample, and migrated for real in a quiet window with the old system read-only. Training happens by role on the live system with the business’s own data in the week before go-live. Go-live is a quiet day with the old process kept warm for two weeks. Nothing is deleted until the new system has run for a month.
Judge the company by its own software
Ask which products the company runs itself, how many users, how long in production, and what the last three releases changed. A company that only builds for others has never answered for the failure at 2 a.m. GBCORP runs its own products on the same engine it builds client software with, and says so because it is checkable in the stores.
Security a business can explain
A dedicated cloud project in the client’s name. Every request checked on the server. User-supplied text escaped wherever it is shown. Secrets in a secret store. Server-enforced password rules with single-use reset links and rate limits. Backups, retention and audit history configured. Written down in a page the client can hand to a customer’s security team.
What the support plan includes
Monitoring, patches for libraries and platforms, operating-system and store updates where there is a mobile app, hours each month for small changes, response times by severity in writing, and a quarterly review of the numbers the software was built to move. Custom software without a support plan is a project, not a system.
Starting small
The first release covers 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. A year-long first phase is 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 with prices rather than a single large bet. Businesses that start small end up with more software, not less, because each release is approved on the evidence of the last.
Questions we hear first
Is custom software more expensive than a product?
Per feature, yes; per year, often not, with no per-seat licence and no workarounds.
Can custom software start from a white-label base?
Yes, and it usually should; custom releases cover only what differs.
How do we avoid scope creep?
A written scope, a fixed price per release, and changes priced as releases.
Who maintains it?
GBCORP under a support plan, or your team after a documented hand-over.
Where to start
The GBCORP software development hub sets out the method; the GBCORP Custom App Development product is the priced starting point. For choosing the company, read the questions that matter for a custom software development company.
GBCORP operates across 17 countries on 4 continents through six pillars: AI & IT, Innovation, Sustainability, Infrastructure, Business Lounge, and EV's & Solutions.
