Bespoke software built around how your business actually runs.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.