What does a design or branding studio's website need?

The one portfolio that is also the exhibit

Every business is judged on its website. A design studio is judged twice — once on the work it shows, and once on the thing showing it. You are the only trade where the buyer evaluates the medium and the message at the same time.

That double judgement produces a specific, very common failure: the site is exquisite and says almost nothing. Enormous images, a great deal of white space, project pages that are a silent grid of the finished logo. It wins the craft argument and loses the buying one.

The reason is simple. That page is written for other designers, who admire execution. The person with a budget is not admiring execution — they are trying to work out whether you can solve their problem, whether the project will end, and what it will cost.

What a case study is for

The portfolio piece most studios publish is a gallery. The one that wins work is an argument with three parts:

The problem. What was actually wrong. Not "the brand needed refreshing" — "they were being quoted alongside two competitors and losing on perceived scale."

What you did, and why. The decisions, briefly. This is where craft belongs, and where you separate yourself from someone who makes things that look similar without knowing why.

What changed. The result. Sales, enquiries, a successful raise, a price rise the market accepted, a rebrand that survived a merger. If you have a number, use it. If you cannot share one, a client sentence is the next best thing.

Most studios have the middle section and nothing else. Reverse the emphasis: the result should be the largest, most visible element on the page, and the prettiest picture should support it.

The objection nobody puts in writing

Buyers of design are frightened of two things, and neither is aesthetic.

That it will not end. Everyone has heard the story of the rebrand that ran nine months and produced three rounds of nothing. A named process with a rough timeline — five stages, six to eight weeks, this is what happens in each and what we need from you — removes more doubt than another beautiful project ever will.

That they cannot afford you, or that you are cheap. Both are fatal and both come from an empty page. Without a signal, a serious buyer assumes you are out of range and does not enquire, and the wrong buyer arrives expecting a logo for very little. A starting-from figure or a typical project range costs you nothing and sorts your inbox — see should I put prices on my website.

Show fewer projects

Six well-argued case studies beat twenty galleries, for a reason that is not about taste.

A visitor does not scroll your whole portfolio. They look at two or three and form a view — and if the weakest is in the first three, that is the view they form. Every project you add dilutes the average and lowers the chance that the two they see are your best. This is the same arithmetic that applies to a freelancer's portfolio, and it is counter-intuitive enough that almost nobody acts on it: see what should a freelancer's portfolio have.

Cutting is also the cheapest improvement available to you. It takes an afternoon and costs nothing.

The uncomfortable part

The work you are proudest of is often not the work that sells.

Your favourite project may be the one with the most invention in it, done for a client who let you off the leash. The project that wins you the next five clients is usually the boring one in the sector your buyer is in, where the result was measurable and the story is legible to someone who is not a designer.

Show both. Lead with the second.

What this looks like in Helm

A design studio has a requirement that is genuinely awkward everywhere else, and it is worth naming plainly.

You want a site that does not look like a template — that is your entire product — and you want to add a case study on a Tuesday without briefing a developer and waiting three days. Almost every platform makes you pick: a template you can edit, or a custom build you cannot. Helm is deliberately both halves, and for a studio that trades on its own site being distinctive, that is the whole argument.

Case studies live in a repeater — reorderable and collapsible — so the tenth one goes in with the same fields as the first and appears in the shape the site was designed for. The result stays the prominent element because the design says so, not because someone remembered.

Version history keeps a snapshot at each publish, and restoring loads it back into the draft rather than straight onto the site, so an edit to a live case study is reversible.

And because the site is real source code rather than a proprietary format, it can leave with you. For a studio that may want to rebuild in three years, or hand a project to a client, that is a materially different position from being inside a platform that has no export — see what you can take with you.

The short version

Your site is graded twice, so make the argument as good as the artifact. Build case studies as problem, work and result, with the result the biggest thing on the page. Publish a process with a timeline and some sense of investment level. Show six projects rather than twenty. Lead with the legible result, not the one you enjoyed most.