01What a creative studio website needs

A creative studio website is not a brochure. It is where a potential client decides whether the studio understands their problem, and where the team shows how it thinks. That calls for things a corporate website rarely needs:

  • A project archive that grows every month, with filters by discipline, client or year.
  • Case studies with their own structure: context, problem, process, result.
  • Video, large images and motion without slow pages.
  • Several languages, each with its own URLs and metadata.
  • Forms that arrive organised in the CRM or the team’s inbox, not a generic mailbox.
  • Sometimes, an area where the client reviews deliveries or approves versions.
Fig. 1 · Where a rigid template falls short

02Where a rigid template falls short

A template handles well what its author planned for: a few pages, a gallery and a form. Problems start when the studio wants to step outside that mould:

NeedRigid templateCustom platform
Presenting the workPredefined grids and galleriesDesign built for each type of project
Case studiesOne generic page per projectIts own content model, with optional sections
Performance with videoDepends on the theme and pluginsLoading and formats decided from the start
Languages and SEOWhatever the template allowsURLs, metadata and structured data per language
IntegrationsAvailable plugins or connectorsDirect connection to CRM, calendar or invoicing
Client areaUsually noneCustom access, deliveries and approvals

The table does not say templates are bad. It says their limits were set by someone else. When the studio changes the way it works to fit the template, the tool has stopped doing its job.

03Performance, Core Web Vitals and SEO

Google measures page experience with Core Web Vitals. According to web.dev, a page is considered good when, at the 75th percentile of visits, the main element renders within 2.5 seconds (LCP), the page responds to interaction within 200 milliseconds (INP) and layout shift stays at 0.1 or less (CLS). On a studio website, with video and large images, these numbers depend on how the files are served, not on the design.

A custom platform lets you decide from the start the image and video formats, what loads first and what loads later. It also lets each project have its own URL, title, description and structured data in each language, which is what search engines and AI assistants read to understand what a page is about.

04Case studies that convert

A client with a serious project is not just looking for nice images: they are looking for proof that the studio understands problems like theirs. A useful case study explains the context, the problem, the studio’s role, the process, the solution and, where there is real, approved data, the impact. If there are no figures, the result is described qualitatively; inventing them costs credibility.

On a custom platform, the case study is a content model with optional fields: if a project has no impact data, that section simply does not appear. The archive stays consistent even when each project has different information.

05Internal workflows: from the website to production

The website can take over part of the studio’s admin work. A briefing form that collects what is needed and creates a record in the CRM. A client area where deliveries are shared and approvals are logged. A call booking connected to the team calendar. Each piece saves emails and reduces errors.

These connections are designed with the same rules as any integration: minimum permissions, a log of what happens and a named owner. When AI is involved, for example to summarise a briefing, a person reviews it before anything reaches the client. I cover this in the guide on connecting AI with n8n, Make and existing tools.

Fig. 2 · When a template is enough

06When a template is enough

A template makes sense when the studio is just starting, when the website only has to exist and give a contact, or when the budget is better spent elsewhere. It also works for testing a new positioning before investing more. In those cases, my advice is to choose a clean template, look after URLs and copy, and avoid piling on plugins.

When the studio already has a site and is unsure whether to keep it, the criteria to redesign or rebuild a website are in a separate guide.

07How I approach a custom platform

I start with a diagnosis: what the website has to do for the studio, who will maintain it and which tools are already in use. With that in writing, I propose a small, useful first phase, usually the project archive and case studies, and leave integrations and the client area for later phases. Each phase is delivered working, so the studio uses it before the next one arrives.

How I organise each phase is set out in my online platforms service; if the job is renewing an existing site, see my website redesign service.