About us

Built over twenty years. Changed by what we learned.

Evokes began as a digital delivery company in 2004. Experience changed the questions we ask, the work we accept, and the responsibility we take.

Signal

Work

Signal

Data

Signal

People

Diagnosis

What must change?

Direction

Build what matters

How Evokes changed

Delivery taught us to look earlier.

When Evokes started, our work centred on designing and building digital systems. We began with the brief and delivered against it.

Years of delivery showed us that the brief was often only part of the picture. Important decisions had already been made. Processes had not always been examined. Different parts of an organisation could understand the same problem differently. A well-built system could still solve the wrong problem.

Evokes changed in response. We began spending more time understanding the organisation before defining the technology. This was not another service added to the company. It became the way the company works.

Evokes today

One team from the first question to operation.

Today, Evokes brings consultancy, architecture, delivery, operations, and cyber security together. The point is continuity: the people shaping a decision remain close to the work and accountable for what follows.

Explore what we do

People

The people responsible for the work.

Gihan Nadeera

Founder & Chief Executive Officer

Gihan founded Evokes in 2004. He began in interface design, the visible surface of systems, and moved steadily toward what sits beneath it: how organisations decide, where authority actually sits, and why a well-built system can still solve the wrong problem. The company followed the same path.

He works across banking, aviation, education, logistics and agriculture. The range is deliberate. Structural problems repeat, and reading one sector sharpens the reading in the next. He asks the same discipline of the team: no proposal without a diagnosis, and no handover that leaves the thinking behind.

Outside Evokes he writes on clarity and decision-making.

Tell us what you are working through.

A finished brief is useful, but it is not required. Start with the situation as you see it.

Start a conversation