The Dispatch Agency

Overview

Dispatch needed an agency site that communicates offer, proof and next step quickly — without the maintenance drag of a heavier stack.

I designed and built the site in Framer, structured around marketing-owned updates.

The problem

Most agency websites bury the offer. Visitors arrive knowing they need help and leave still unsure what the agency actually does, who it is for, or what engagement looks like. The information exists — it is just distributed across pages nobody reads in order.

Dispatch also had a practical constraint: the marketing team needed to ship updates themselves. Any solution requiring developer time for a new case study would fail within a quarter.

Constraints

Marketing-owned updates, real performance expectations, and a portfolio presentation that needed to feel editorial rather than generic agency chrome.

Approach

I structured the site around three questions in order: what do you do, does it work, and how does an engagement start. Services establish the offer, selected work supplies proof, and a direct booking path handles the next step. The structure is deliberately conventional because it matches how buyers actually evaluate agencies — the differentiation lives in execution, not in novel navigation.

Case studies were treated as the primary conversion asset rather than an afterthought. Layouts prioritise scannability and storytelling: what the client needed, what was done, what changed. That structure gives the team a repeatable format for publishing new work without redesigning each time.

Everything is built on Framer-native components the team can extend. Adding a case study means filling a CMS entry, not rebuilding a page — which is what keeps a portfolio current after the agency that built it has moved on.

Performance

Staying in Framer avoided the plugin accumulation that degrades most agency sites over time. Fewer moving parts means fewer things to update, fewer security surfaces and a site that stays fast as it grows.

Making case studies the conversion asset

For an agency, case studies do more selling than the services page ever will. Prospects skim services to check relevance, then go straight to proof. Despite that, case studies are usually the least considered part of an agency site — inconsistent, hard to publish, and often abandoned after the first three.

The structure here treats them as the primary asset. Each follows the same shape — what the client needed, what was done, what changed — which makes them faster to write, easier to scan, and consistent regardless of who publishes them. Consistency matters more than variety: a reader comparing three case studies is looking for the pattern, not the novelty.

Publishing without a developer

Any solution requiring developer time for a new case study fails within a quarter — the work backs up, publishing stops, and the portfolio silently ages. Content lives in Framer CMS collections, so adding a case study means completing a CMS entry, not building a page.

Why the structure is deliberately conventional

The navigation and page order here are unremarkable by design. Buyers evaluating agencies follow a predictable path, and making them learn a novel structure adds friction at exactly the wrong moment. The differentiation lives in the writing, the work and the visual execution — not in making people hunt for the services page.

Outcome

A sharper agency presence with clearer positioning and a conversion path that does not bury the call to action — plus a publishing workflow the marketing team owns outright.

Live at thedispatch.agency.