Our Story
Engineering judgement,
backed by operating experience.
Our mission.
Perception IT was founded in 2010 to solve complex infrastructure and operations problems without separating design from long-term responsibility.
The company works across physical infrastructure, cloud platforms, operational data, observability and service management.
What drives us.
Operational responsibility
We design with support, ownership and maintenance in view from the start.
Engineering judgement
We adapt methods and platforms to the operating context instead of forcing a stock answer.
Long-term partnership
We stay accountable through implementation, handover, support and improvement.
Our journey.
2010 — Founded
Perception IT founded around enterprise infrastructure, systems management and operational support.
Technical governance
Delivery broadened across observability, ITSM, telecom operations, cloud platforms, IoT and data systems.
Engineering delivery
Engagements span assessments, implementation, migration, managed operations and technical governance.
24/7 support
Authorised enterprise partner routes complement independent multi-vendor engineering experience.
Local presence, distributed delivery.
Teams work from Lahore and Fleet, with remote delivery and support shaped around the engagement.
Lahore
Engineering delivery, platform operations and technical support.
Liberty Gate Plaza, Tariq Road, Gulberg III
Fleet
Client engagement, consulting and technical leadership.
12a Fleet Business Park, Sandy Lane
Technical leadership
Founder’s enterprise delivery experience since 2000
Founder and technical lead
David Pridmore
Founder, CTO & CEO
David is a senior infrastructure and observability consultant with experience across major telecommunications, banking, government and technology organisations.
His experience spans major telecommunications, banking, government and infrastructure organisations, including BT, Barclays, RBS, Deutsche Bank, DEFRA, Lloyds Bank, Jazz, Pakistan Stock Exchange and Helios Towers.
That experience shapes a practical approach: understand the operating context, make ownership explicit and design for the years after implementation.
Know how the work will be owned.
Bring us an operational problem that needs clear technical ownership.
Get in touch