01The group's technology function
We turn business ambition into dependable technology.
NexMadar provides the operational technology, cybersecurity, platforms, automation, AI and research capability that helps group companies run, adapt and grow.
02Origin
A support desk that became a capability.
For more than fifteen years, the same team has carried the group's technology — first keeping it running, then deciding how it should work, and now building what comes next.
First
It started with keeping things running.
Networks, workplaces, mail, access, the first business systems. The work was measured in whether people could do their jobs that morning — and that standard never left.
Then
Reliability earned a wider brief.
As the group grew, technology stopped being something bolted on after a decision and became part of making it. Core platforms, finance and operations systems, and customer processes were shaped with the business rather than handed to it.
Since
Proximity became the advantage.
Sitting inside the group means knowing how a delivery run, a service call or a month-end close actually behaves. That context is the difference between a system that satisfies a specification and one that survives daily use.
Now
The brief includes what comes next.
Automation, AI and emerging technology are part of the remit — held to exactly the same operational standard as everything already in production. Nothing reaches the business until it can be secured, supported and explained.
Founding year, tenure wording and any dated milestones: [APPROVED CONTENT NEEDED]
03Concept to reality
How a business idea becomes a system people rely on.
Seven stages, in order. Each one closes with something the business can read, test or use — not a status update.
- 01
Understand
Listen before proposing anything.
We spend the first part of any request with the people who live with the problem — the operational need, the risk, the bottleneck, the opportunity someone can see but cannot yet act on. Solutions offered before this point tend to solve the wrong thing well.
Leaves this stageA shared description of the problem, written in the language of the business.
- 02
Define
Agree what a good outcome looks like.
Outcomes, users, processes, constraints, governance and the conditions that would count as success. Scope is set here deliberately, because it is far cheaper to argue about a definition than about a delivered system.
Leaves this stageAgreed outcomes and success criteria, with the constraints named openly.
- 03
Design
Draw the path before building it.
Architecture, experience, integration points, data flow, security requirements and sequencing. The design accounts for what already exists in the group — not a clean sheet, but the real estate of systems the business already depends on.
Leaves this stageAn architecture and roadmap, with security and integration decided rather than deferred.
- 04
Build
Develop, configure, integrate, test.
Whether the work is new development, platform configuration or connecting systems that were never designed to speak, the discipline is the same: build in increments the business can see, and test against the criteria set in Define.
Leaves this stageA working, tested solution and the documentation needed to run it.
- 05
Secure
Protect it as a condition of release.
Identity and access, application and endpoint protection, information handling, monitoring and continuity. Security is treated as part of whether something is finished, not as a review it has to pass afterwards.
Leaves this stageProtection, access control and continuity arrangements in place before go-live.
- 06
Operate
Keep it dependable in daily use.
Support, monitoring, maintenance, change and documentation. Most of a system's life is spent here, which is why the way something will be operated shapes how it gets designed in the first place.
Leaves this stageA supported service with a known owner, a known process and a known route for help.
- 07
Evolve
Look further than the current request.
Emerging technology, AI, automation and new ways of working are evaluated against real group problems. Some are adopted, some are set aside for now, and saying so plainly is part of the work.
Leaves this stageAn evidenced view of what to adopt, what to watch, and what to leave alone.
04Capabilities
Four responsibilities, held together.
These are not four service lines competing for attention. They are one capability, and the order matters: nothing is built that cannot be secured, and nothing is secured that cannot be operated.
Run reliably
The technology people touch every working hour — kept steady, supported by a team that answers, and recoverable when something goes wrong. This is the floor everything else stands on.
- IT operations
- Infrastructure and workplace technology
- End-user support
- Service management
- Business continuity
What this enablesTeams start the day able to work, and know where to go when they cannot.
Protect what matters
Systems, identities, information and the continuity of operations. Protection is designed into how technology is built and run, so that security decisions are made once — early — rather than repeatedly under pressure.
- Cybersecurity
- Identity and access
- Security monitoring
- Risk reduction
- Secure technology practices
What this enablesThe business can act quickly without quietly accumulating risk.
Build and connect
The platforms the group runs on and the connections between them. Most operational friction lives in the gaps between systems, so integration and workflow are treated as first-class design work, not as wiring.
- ERP
- CRM
- Mobile applications
- Business applications
- Systems integration
- Data and workflow design
What this enablesInformation moves once, correctly, instead of being re-entered along the way.
Evolve intelligently
New capability, introduced on the group's terms. AI, automation and emerging technology are tested against real problems and adopted only where the value is clear and the result can be governed and supported.
- AI
- Automation
- AI agents
- Digital transformation
- Technology research and development
- Emerging technology evaluation
What this enablesThe group adopts what genuinely helps, and can explain why it adopted it.
05Group enablement
Many businesses. One dependable technology foundation.
Each company in the group has its own operations, customers and pace. Shared technology capability means none of them has to solve identity, security, integration or support alone — and improvements made for one become available to all.
Brothers Gas
Gulf Gas
Medquips
Balloonee
Freeze Refrigerants
ICE Refrigerants
iEngineering
Glowei
06Run and move
Two obligations, one team.
Keeping the business running.
- Stability of the systems operations depend on
- Support that answers and follows through
- Service continuity through change and disruption
- Secure day-to-day operations
- Platforms that behave the same on a busy day
Helping the business move forward.
- ERP and CRM evolution as operations change
- Mobile solutions for work that happens away from a desk
- Automation of the repetitive and error-prone
- AI applied to defined, worthwhile problems
- Research and honest experimentation
Innovation earns its place when it is secure, useful, governed and sustainable to operate. Anything that cannot be supported on a difficult day is not yet finished.
07Vision
Technology should not only support the business. It should help the business see further.
Most technology work is spent answering questions the business already knows how to ask. The more valuable position is one step earlier: connected systems and trustworthy information that let leaders notice a pattern, a cost, a risk or an opportunity while there is still time to act on it.
We intend to keep applying AI and automation the same way we introduce anything else — to defined problems, with a person accountable for the outcome, and with the reasoning open to inspection. The purpose is to remove work that should never have needed a person, and to give the people who remain better ground to stand on.
Research is part of the responsibility, not a side interest. Emerging technology gets evaluated against real group operations, and we say plainly what is ready, what is not yet, and what we would not recommend at all.
08Start a conversation
Have a business challenge, operational need or technology opportunity?
Bring it early and unfinished. The most useful conversations start before a solution has been chosen.