Book a Technology Review

Home/Services/Bespoke Software

Build · Pillar 01

Bespoke software built around how your business actually runs.

When the off-the-shelf system dictates the process instead of supporting it, the cost shows up as workarounds, spreadsheets and people. We write the system that fits the operation you already have.

What is bespoke software development?

Bespoke software development is the design and build of an application for one organisation rather than for a market. Instead of configuring a licensed product and accepting its assumptions, the data model, workflow and interface are written around how that business already operates — and the organisation owns the resulting source code outright.

  • Built for one operation, so no process is bent to fit a licence.
  • No per-seat fee that grows every time you hire.
  • The code, data and hosting sit in your accounts from day one.

Why it matters

The workaround is the real cost.

Almost nobody replaces a working system for fun. What usually happens is quieter: the licensed platform covers 70% of the job, and the other 30% moves into spreadsheets, shared mailboxes, WhatsApp groups and one person who knows how it really works. That 30% is where the margin leaks.

It is also where the risk sits. A process held together by a spreadsheet and an individual is a process that cannot be audited, cannot be handed over, and cannot absorb a 30% increase in volume. We are usually called in at the point where growth has made that obvious.

What we look for first

Where the hours go

Before anything is designed we map the process as it is actually performed — not as the policy says. The gap between the two is almost always where the build pays for itself:

  • The same data is keyed into two or three systems every day.
  • A critical report is assembled by hand, monthly, by one person.
  • New starters need weeks of shadowing to learn the undocumented steps.
  • Your licence cost rises with headcount whether usage rises or not.
  • A change you need has been on the vendor roadmap for two years.
  • Nobody can tell you where a given order actually is without asking.

Scope

What a bespoke build covers.

Every engagement starts with the process, not the technology. These are the parts we are normally asked to cover; a phase can be any subset of them.

  1. Process discovery

    On-site sessions with the people doing the work, mapping the real workflow, exceptions included, before a line of code is written.

  2. Data model & architecture

    The schema your business actually needs, designed to survive ten years of change rather than to suit this quarter’s feature list.

  3. Application build

    Web application with role-based access, audit trails and an admin layer your own team can operate without a developer.

  4. Integration with what stays

    Accounts, payroll, ERP, email and anything else you are keeping, joined up so data is entered once and only once.

  5. Testing & parallel running

    Automated test coverage on the logic that matters, then a period running old and new side by side before anything is switched off.

  6. Handover & documentation

    Written architecture notes, a runbook and the credentials. You are never dependent on us to keep the system alive.

Deliverables

What you actually end up with.

Deliverables are listed in the scope document before the phase starts, so “done” is a defined state rather than an opinion.

  1. A system that matches the operation

    The workflow in the software is the workflow your team already uses, with the exceptions handled rather than pushed into a spreadsheet. Training time drops because there is nothing counter-intuitive to learn.

  2. The source code, in your repository

    Pushed to an account you control, under a licence that gives you the right to take it to any other developer. No escrow arrangement, no source-available compromise.

  3. One place the numbers come from

    Reporting built on the same data the operation runs on, so the board pack and the shop floor cannot disagree about what happened last month.

  4. A documented, transferable asset

    Architecture decisions, data dictionary, deployment runbook and test suite, written for a developer who has never met us. This is what makes the system an asset rather than a dependency.

Is this the right answer?

When bespoke software is worth doing — and when it is not.

We would rather lose a project at this stage than six weeks in. If the right-hand column describes you, say so and we will tell you what we would do instead.

Worth doing when

  • Your process is a genuine commercial advantage and no product supports it.
  • Licence costs scale with headcount while the value you get from them does not.
  • The workaround — spreadsheets, rekeying, one person who knows — is now a risk.
  • You need to own the system because it is central to how the business competes.

Probably not when

  • A well-established product already fits and you want it customised to match old habits.
  • The real problem is that nobody has configured the system you already pay for.
  • You are below roughly 25 staff and the process is not unusual.
  • You want it finished in six weeks because a contract starts then.

How we deliver

Four phases, each priced before it starts.

We do not sell an open-ended day rate. Each phase has a written scope, a fixed price and a date, and the next one is only commissioned once the previous one is signed off.

  1. Phase one

    Discovery & scope

    Two to three weeks on site and in your data. Output is a written specification, a data model, wireframes and a fixed price for the build. It is a deliverable you own whether or not you continue with us.

  2. Phase two

    Core build

    The smallest version that does real work, built first and shown fortnightly. You see working software from week three, not a status report.

  3. Phase three

    Integration & parallel run

    Connections to the systems you are keeping, data migrated, then a deliberate period where old and new run together and the numbers are reconciled.

  4. Phase four

    Cutover & handover

    Switch, support through the first full cycle — month end, payroll, whatever matters — then documentation, credentials and a named contact for the warranty period.

What you receive

The things that actually land.

Artefacts, not adjectives. Everything below is listed in the scope document before a phase starts, so “done” is a defined state rather than an opinion.

  1. A written specification

    From the discovery phase: the process as performed, the data model, wireframes and a fixed build price. Yours whether or not you continue with us.

  2. The source code

    In a repository in your organisation’s account from the first commit, with the intellectual property assigned to you in the contract.

  3. Infrastructure in your tenancy

    Cloud resources provisioned in accounts you own and control, with the credentials handed over rather than held by us.

  4. An automated test suite

    Covering the business logic that matters, so a future developer can change the system without guessing what they have broken.

  5. Architecture and data documentation

    Decisions, diagrams and a data dictionary written for a developer who has never spoken to us.

  6. A deployment runbook

    How to release, how to roll back, what to monitor and who to call. The difference between an asset and a dependency.

Proof

Where this has been built before.

Each one describes what was actually built rather than how it felt, and says plainly where we do not have the figures to claim a result.

  1. PaidDesk

    A multi-tenant UK accounting platform and the site that sells it: invoicing, credit control, payroll, a customer portal, Stripe Connect and an in-app assistant, on a one-time licence.

    Read it

All 6 case studies

Golden Triangle

Why the Golden Triangle changes the brief.

The corridor between Birmingham, Nottingham and Northampton is dominated by logistics, distribution and advanced manufacturing. That shapes what bespoke software has to cope with here.

  1. Multi-site by default Sites, not a site A business in this corridor typically runs two or three locations plus a vehicle fleet. Stock, labour and compliance have to reconcile across all of them, which single-site software never anticipates.
  2. Shift patterns Round the clock Distribution and food production run nights and weekends. A system that assumes a 9-to-5 working day gets its date handling wrong on the first bank holiday.
  3. On site when it counts In the room Discovery that decides a data model does not work over video. Being based in the Triangle means we can be on your floor for the sessions that matter.

We work across Birmingham, Solihull, Coventry, Nottingham, Derby, Leicester, Northampton, Milton Keynes and Wolverhampton, and we are used to the operating realities of businesses sitting on the M1, M6, M42 and A14.

Technology

What we build it with.

Boring, well-supported technology, chosen so that any competent developer can pick the system up in five years. Novelty is a risk you would be carrying, not us.

  • TypeScript
  • C# / .NET
  • PHP / Laravel
  • Python
  • PostgreSQL
  • SQL Server
  • Azure
  • AWS
  • SSO & MFA
  • Automated test suites

Questions

Bespoke software, answered plainly.

The questions we are actually asked in a first meeting, including the uncomfortable ones.

Ask us a question Email us

How much does bespoke software development cost in the UK?

A useful bespoke system for a mid-sized business is normally a five to low six-figure investment, delivered across phases rather than as one bill. GTX Digital prices each phase against a written scope, so the first commitment is a discovery phase of a few thousand pounds that produces a specification and a fixed build price. You decide whether to continue once you have a real number rather than an estimate.

How long does it take to build custom software?

A first working version that does real work is typically 8 to 14 weeks from the end of discovery, with discovery itself taking two to three weeks. Larger programmes run longer but are still broken into phases that each deliver something usable, so value arrives before the whole thing is finished.

Is bespoke software cheaper than an off-the-shelf licence?

Rarely in year one, often by year three. A licence is a predictable annual cost that scales with headcount; a bespoke build is a capital cost with a much smaller running cost. The honest comparison also has to include the workarounds — the spreadsheets, the rekeying and the people absorbing the gap — because those are a real cost of the licensed option that never appears on its invoice.

Do we own the source code?

Yes, entirely. Code is pushed to a repository in your organisation’s account from the first commit, infrastructure sits in your cloud tenancy, and the contract assigns you the intellectual property. You can take the system to another developer at any point without asking us.

What happens if GTX Digital stops trading?

You keep working. Because the code, data, hosting and documentation are already in your accounts, and because we write the handover notes for a developer who has never met us, there is no key that only we hold. This is the main reason we insist on it rather than offering source-code escrow.

Can you work with the systems we are keeping?

That is usually the point. Most builds replace one awkward part of a landscape and integrate with the rest — Sage, Xero, Microsoft 365, an existing ERP or WMS, a carrier API. Replacing everything at once is almost always the wrong call, and we will say so.

What happens after launch?

There is a warranty period covering defects at no cost, and after that you choose: a support arrangement with us, a retained development allowance for ongoing change, or nothing at all. Because the code, infrastructure and documentation are already yours, walking away is a real option rather than a theoretical one, and that is deliberate.

Can we start small and expand later?

That is the normal shape. Each phase is scoped and priced on its own and delivers something usable, so you can stop after any of them with a working system rather than a half-built one. Most clients commission phase two before phase one finishes, but that is their decision rather than a commitment made up front.

Who owns the data, and can we get it out?

You own it, it sits in your infrastructure, and export is built in rather than requested. We will give you a documented schema and a way to extract everything in a standard format. A system you cannot leave is a system that can be repriced against you later.

How do you handle change during the build?

Scope is agreed in writing per phase, and change inside that phase is handled as a priced change order before it is built, not as a surprise on the final invoice. Fortnightly demonstrations of working software are what surface the need for change early, when it is still cheap.

Client voices

What clients say.

  • GTX Digital has been brilliant to work with. They took the time to understand what we needed and built a solution that actually works for the business. The communication has been excellent throughout and it’s clear they understand both the technology and the commercial side.

    Tony ShinglerOmnia Resourcing
  • Really impressed with GTX Digital. They took the time to understand how our business works before recommending a solution. The whole process was clear, professional and much easier than expected.

    James Wilson
  • GTX Digital helped us connect several systems that were previously working separately. It has saved our team a lot of manual work and made our processes much more efficient. Great experience overall.

    Daniel Harris
  • We needed a bespoke software solution for our business and GTX Digital understood exactly what we were looking for. The communication throughout the project was excellent and the finished system works really well.

    Sophie Mitchell
  • Very professional team. They took the time to understand the problem before suggesting a solution, which we really appreciated. Everything was explained clearly and the project was handled extremely well.

    Michael Thompson
  • GTX Digital made a complicated technology project feel very straightforward. They kept us updated throughout and were always available when we had questions. Very happy with the final result.

    Oliver Bennett
  • We approached GTX Digital to replace an outdated system and they handled the whole process brilliantly. The new platform is much easier for our team to use and has made our day-to-day work considerably smoother.

    Emily Carter
  • Really good experience from start to finish. The team listened to what we needed, explained the technical side in simple terms and delivered a solution that works perfectly for our business.

    Ryan Edwards
  • GTX Digital helped us automate several repetitive tasks that were taking up far too much of our team’s time. Their approach was practical and the improvements have made a noticeable difference.

    Charlotte Morgan
  • We had several systems and APIs that needed to work together, and GTX Digital handled the technical side extremely well. They were organised, responsive and professional throughout the project.

    Thomas Cooper
  • Very happy with the service from GTX Digital. They didn’t try to sell us things we didn’t need. Instead, they focused on understanding our business and finding the right solution.

    George Richardson
  • GTX Digital helped us turn an idea into a working digital platform. The team were knowledgeable and easy to communicate with, and they made sure we understood everything throughout the development process.

    Hannah Walker
  • Excellent experience with GTX Digital. The project was well organised and we always knew what was happening next. The final system has made our internal processes much more efficient.

    Jack Anderson
  • We needed a technology partner who could understand both our business requirements and the technical side of the project. GTX Digital were a great fit and delivered exactly what we needed.

    Lauren Parker
  • The team at GTX Digital were fantastic to work with. They took a complicated requirement and broke it down into manageable stages. The final solution has saved us a lot of time and reduced repetitive work.

    Ben Foster
  • Highly recommended. GTX Digital combines strong technical knowledge with a very practical approach to business problems. Communication was excellent and we were very pleased with the finished product.

    Olivia Collins

Related services

Often scoped alongside this.

  1. Build

    Legacy Replacement

    Replacing the system nobody dares touch, without stopping the business.

    Explore
  2. Connect

    API Development

    APIs and integrations so data is entered once and moves on its own.

    Explore
  3. Automate

    Workflow Automation

    The rules-based work that eats a week, handed to software that does not forget.

    Explore

All 19 GTX Digital services

Next step

Start with a process review, not a specification.

Two hours with the people doing the work tells us more than a requirements document ever will. We will tell you honestly whether a bespoke build is the right answer — sometimes it is not.