C
Carl
Strategic Sales Advisor
Two journeys. One point of convergence.
The founder journey and the Avelo journey are not the same story.
They intersect — but each has its own origin, purpose and progression.
The Founder Story
Gurj Chaggar MBCS
Gurj's founder journey spans more than twenty years across technology, operations, service delivery and business transformation. His career has taken him through frontline IT support, infrastructure, service management, project delivery, team leadership and consultancy — from supporting users and critical systems to leading teams, managing projects and improving the way organisations work.
That experience built a practical view of technology: the problem is rarely that a business has no systems. More often, it has too many systems that do not communicate properly, too many manual hand-offs between teams, and too little visibility over where time, money and control are being lost.
Working across different environments, including enterprise operations and NHS technology, reinforced the same lesson repeatedly: transformation only matters when it improves the real process underneath. New software alone is not the answer. The value comes from understanding the bottleneck, connecting what already exists and introducing automation in a way people can trust.
Avelo grew from that principle. Gurj built the company to bring systems, data, workflows and AI together under one governed architecture — preserving human authority while giving organisations the ability to operate with greater speed, visibility and control.
He sees Avelo not as another software product, but as the architecture that sits between intelligence and the real world: connecting existing technology, governing how AI acts, and turning operational evidence into measurable action.
Meet the Team
The people behind Avelo.
Avelo brings together technology, sales, finance, people and marketing around one goal: helping organisations operate with greater clarity, control and confidence.
The Avelo Story
Built from one operational question.
Avelo did not begin with a piece of software. It began with a question:
Where is the business losing time, money and control — and can we prove it?
That question shaped the architecture. Discovery became the intelligence layer. Avelo One became the operating layer. Controlled AI became the mechanism connecting people, systems and actions without removing human authority.
Evidence before assumptions
Claims need operational support.
Human authority
AI operates inside defined controls and approvals.
Modular deployment
Deploy only what the business case supports.
Auditability
Actions, approvals and outcomes remain traceable.