About us
Evokes understands what must change before deciding what should be built. Experience taught us to begin with diagnosis.
Work
Data
People
Diagnosis
What must change?
Direction
Build what matters
The shift
Evokes began in 2004 by designing and delivering digital systems. Over time, the most important lesson came before the technology: the request an organisation brings is not always the need it actually has.
We saw the same pattern across sectors. A solution had already been chosen, while the underlying problem lived deeper in decisions, work, data, governance, or people.
So we moved upstream. Today, we diagnose first and build second. The result may be a full platform, a focused intervention, a clearer strategy, or a decision not to build at all.
2004
Digital design and delivery.
The recurring pattern
The stated solution and the real requirement were often different.
Today
Diagnosis before commitment.
What experience taught us
Three principles keep the work anchored to the real need.
01
A brief rarely contains the whole problem. We look at the decisions, workflows, data, governance, and people around it.
02
What appears to be a technology problem may begin in operations, accountability, or the way information moves.
03
The right answer may be a platform, a focused intervention, a clearer decision, or no build at all.
Evokes today
Our work spans strategic consultancy, architecture, build and run, and cyber security. These are not disconnected services. They are stages of one accountable response to a problem understood properly.
Depending on what the evidence shows, we can advise, shape the solution, deliver it, and stay with it in operation.
01
Strategic consultancy
02
Architecture
03
Build and run
04
Cyber security
People behind the work
Evokes is built around people who can move between the strategic and the practical: understanding an institution, challenging assumptions, and staying close enough to delivery to remain accountable for the outcome.
Founder & Chief Executive Officer
Gihan founded Evokes in 2004 and has led its evolution across more than two decades of technology change. His work sits where institutional ambition, operational reality, and technology decisions meet.
That perspective shaped the way Evokes works today: investigate the organisation behind the brief, make the problem legible, and commit only to the intervention the evidence supports.
Whether you have a defined brief or only a sense that something is not working, we start by listening.