Independent software studio / Manchester

A small studio for difficult, worthwhile software.

DevMuse is Hayden Hewitt’s software studio. It gives complicated work the care of a product, with the person shaping it staying close from first question to finished system.

Founder-ledClient systemsOriginal products

Illustrated portrait of Hayden Hewitt
Hayden HewittFounder / 01

Why DevMuse exists

Better software starts by staying close to the real problem.

Too much important work is squeezed into generic tools or divided between people who only see one part of it. The result can look finished while remaining awkward to use, hard to change and detached from the organisation it serves.

DevMuse offers a more thoughtful route. We treat bespoke work with the care of a product: understand the operation, question the brief, design the whole system and carry those decisions through the build.

The aim is not software for its own sake. It is clearer work, fewer fragile workarounds and a result people can rely on.

Hayden Hewitt · Founder

One accountable person, backed by the right specialists.

Manchester / Independent / Direct

How the studio works

The thinking and the making stay connected.

Hayden leads the product thinking, design and technical direction, and remains involved through delivery. There is no sales hand-off and no anonymous layer between the conversation and the work.

His wider work covers platforms, moderation and operational systems. That perspective shapes how DevMuse approaches software: as part of a living organisation, not an isolated screen.

When a project needs more hands or a particular discipline, DevMuse brings in trusted specialists. Hayden remains responsible for the whole.

More about Hayden

The shape of the studio

One practice. Three places for the work to live.

Each part of DevMuse has a clear job. Client work stays focused, products pursue a strong idea, and the Workshop gives smaller experiments room to prove themselves.

How we work

Four principles used in the real work.

01

Understand before building

The first job is to find the real problem, including the awkward parts people have learned to work around.

02

Make complexity usable

Good software can support difficult work without making the people doing it feel stupid.

03

Show the working

Clear decisions, honest progress and visible trade-offs make better projects and better partnerships.

04

Build for real life

The work must survive ordinary days, imperfect data, changing needs and the people who actually use it.

Working together

Enough structure to protect the work. Not enough to hide behind.

  1. 01

    Start with what is stuck

    A polished specification is not required. A rough account of the problem gives us somewhere honest to begin.

  2. 02

    Shape the useful outcome

    We make the boundaries, risks and important choices clear before effort disappears into the wrong solution.

  3. 03

    Keep the work visible

    You see working evidence, understand the trade-offs and know what happens next throughout the project.

Work with DevMuse

Bring the difficult problem. We will start by making it clear.

Start a conversation