We started with websites. The problems kept being somewhere else.

A design practice in Singapore. Over a hundred projects in, the pattern was hard to miss: what a business asks for and what is actually costing it money are rarely the same thing.

Start with the problem

How we changed our minds

We stopped starting with the brief.

For the first two years we did what most studios do. A company asked for a website, we made a good one, we handed it over. Some of them worked. Some of them changed nothing, and we could not always tell in advance which would be which.

What separated them was almost never the design. It was whether the thing we fixed happened to be the thing that was broken. When it was, the site paid for itself. When it was not, we had made a better-looking version of a business that still could not answer an enquiry inside a day.

So we stopped starting with the brief and started with the business.

Service design is a discipline. Not a workshop.

Service blueprints, journey mapping, ecosystem mapping. Methods for seeing how work really moves through an organisation, and where it breaks. They come from a formal training, not from a book skimmed on a weekend.

It is the reason we start with the problem instead of the brief. A brief tells you what someone thinks they need. A blueprint tells you what is actually happening, including the parts nobody mentions because they are used to them.

What a diagnosis looks like.

This is how these usually go, not one specific client.

01
A fabricator calls about a website.
Enquiries are down, the site looks dated, and a competitor has just relaunched. That is the brief, and it is a perfectly reasonable one. We do not start there.
02
We follow one job all the way through.
From the first email to the invoice. Who opens it, who prices it, what they need before they can, and how long it sits between each pair of hands. We do this with the people doing the work.
03
The delay turns out to be in the middle.
Quotes take three days, and two and a half of those are spent waiting for one person to confirm material pricing from a spreadsheet only he maintains. The website had nothing to do with it.
04
We build for the bottleneck, not the brief.
A pricing tool the estimator can run himself, so quotes go out same-day. Then the site, because it was genuinely dated. In that order, because the order is what makes the second one worth paying for.

Sometimes the answer is a website after all, and we say so. The point is not that the obvious answer is always wrong. It is that nobody had checked.

We would rather stay than finish.

A project ends. A business does not. The first job costs more, because that is when we work out how everything runs. We only do that once.

The second thing we build costs less than the first, because we already know how the work moves. Over a few years that adds up to a lot less than starting again with a new studio each time.

You do not have to commit up front. Do one piece of work first, then decide.

How this works in practice.

The commercial terms, before you ask.

You own everything.

Code, accounts, domains, files, documentation. In your name from day one.

We host most of our clients.

One supplier, one invoice, one person to call when something breaks. It means we can fix things instead of asking someone else to.

We build on standard tools.

Nothing private, nothing locked. Anyone competent can pick up what we have made.

Documentation is a deliverable.

Not a favour, and not something you have to ask for at the end.

We carry professional indemnity insurance.

Ask any studio quoting you five figures whether they do.

If we stop working together, we migrate you out properly.

You are not stranded. That is a design decision, not a promise.