23 October 2026
In short
What software work do businesses at Birmingham Business Park actually need?
Occupiers at Birmingham Business Park usually run global systems chosen elsewhere, so the local gap gets filled with spreadsheets. GTX Digital builds the local layer properly, without touching the system the group reports from, one phase at a time.
- A global system is optimised for comparability, not for your market.
- Shadow IT is not indiscipline. It is a requirements document.
- Build beside the global system and never fork its master data.
- A local build must survive a group migration, so keep your own history.
- The approval you need is usually about data, not about software.
Think this applies to your business?
We will tell you straight whether it is worth doing, what it would take, and what we would do instead if it is not.
UK operation, systems chosen elsewhere? Book a technology review. Bring the three spreadsheets your team could not work without.
A global system is a compromise by design. It has to work in fourteen countries, which means it fits none of them exactly, including yours.
What is actually here
Birmingham Business Park sits at junction 6 of the M42 in Solihull, and describes itself as the Midlands' most established out-of-town office park.
Its own material gives around 2.4 million sq ft of offices and more than 150 businesses, naming Rolls-Royce, IMI, Canon and Goodyear. An agent listing gives older figures of 1.9 million sq ft and over 100 occupiers.
The agent KWB reported the M42 and Solihull area taking 45% more office space in the first half of 2026 than in the second half of 2025, across 18 deals — the most in a half since 2023, on its account. KWB trades in that market, which is worth holding in mind.
What matters for software is the occupier profile. These are UK operations of international businesses, and their core systems were chosen somewhere else.
Shadow IT is a requirements document
Every UK team in this situation has spreadsheets, and they are usually treated as a governance problem.
They are better understood as evidence. Each one exists because a real process had no home in the global system, and somebody solved it rather than waiting.
| The spreadsheet | What it proves |
|---|---|
| A parallel pipeline | The global stages do not match how you sell |
| A local price or discount sheet | The pricing model does not reflect your market |
| A manual reconciliation | Two systems disagree and nobody owns the join |
| A tracker for a local process | The process exists and the system does not know |
Read them before writing a single requirement. The columns tell you the missing fields and the formulas tell you the rules nobody encoded.
The maintainer knows what is missing
Worth saying, because global programmes routinely ask the wrong people.
The person who can describe the gap precisely is whoever maintains the spreadsheet. Not the manager. Not group IT. The maintainer.
Start there and the requirements take an afternoon instead of a workshop.
Keep it small enough to be obviously safe
A local build gets approved on the strength of how little it threatens.
One process. Read-only where possible. No new master data. A named owner. A page describing what data moves and where.
Described that way, approval is usually quick.
Described as a platform, it becomes a governance conversation lasting a quarter, and by then the spreadsheet has grown another tab.
Build beside it, never fork it
The approval conversation is about data, not software, and that is the key to getting a yes.
Three commitments make a local build acceptable to a group IT function. The global system remains authoritative for the records it owns. The local layer creates no second version of a customer, product or order. And anything the group reports on continues to come from the group's system.
Inside those constraints there is usually a great deal of useful work, and it is work nobody else is going to do for you. The CRM-specific version is in CRM integration for Birmingham Business Park businesses.
Assume a group migration
This is the practical design warning.
Global systems are replaced, upgraded and reconfigured on somebody else's schedule, and local adaptations are the first casualty.
So a local build should hold its own history and read from the global system rather than living inside it. Then a migration costs you a mapping exercise instead of your institutional memory. We do this as bespoke software development, with the local engagement on the Solihull page.
The integration is usually read-only
A reassuring thing to tell a group IT function, and usually true.
Most local value comes from reading the global data and adding to it, not from writing back. Reading is lower risk, easier to approve, and simpler to support.
Where writing back is genuinely needed, keep it narrow, explicit and logged, and expect the approval to take longer than the build.
Reporting for two audiences
A UK operation has to answer the group in the group's definitions and manage itself with its own.
Those are two reports from the same data, which is entirely workable. It becomes a problem only when the two are maintained separately, because then they diverge and somebody has to explain why.
Derive both from one source and the question disappears.
Local compliance is local
Group systems are rarely built around UK-specific obligations, and the gap tends to be filled by a person who knows.
Whatever that is in your sector — a statutory return, a reporting duty, a documentation requirement — it belongs in a system rather than in somebody's diary.
It is also usually the easiest project to get approved, because nobody argues with a compliance requirement.
Where this fits locally
Solihull mixes international head offices, automotive engineering and logistics within a few miles, and the junction 6 office market serves the corporate end of that.
We work with professional services and retail and e-commerce businesses across the borough, and the local picture is on the Solihull page.
The neighbouring park, and what it looks like when a brand owns the data but not the operation, is in software development for businesses at Blythe Valley Business Park.
A reasonable first step
Ask your team which spreadsheet they would protect if told to stop using it.
That one is doing real work that your systems do not. Open it, read the columns, and you have your first phase.
Nobody will have to be persuaded it is needed. Somebody is already maintaining it by hand. Talk to us.
Common questions
What kind of businesses are at Birmingham Business Park?
Large international businesses running UK operations. The park’s own site describes roughly 2.4 million sq ft and more than 150 businesses, naming Rolls-Royce, IMI, Canon and Goodyear; an agent listing gives older figures of 1.9 million sq ft and 100+ occupiers.
Can a UK team commission its own software?
Often yes, for things the global system does not cover, provided the master data stays where the group put it. That distinction is usually what gets a project approved.
What about the spreadsheets we already rely on?
They are the specification. Read them before writing requirements, because they describe precisely what the global system does not do.
Next step
Start with a technology review, not a proposal.
A short, structured conversation about where your systems are costing you time, margin or growth — and what the realistic options are. No pitch deck.