Goodspeed ↗
Recognizable situations before services; specific packages and visible pricing. Borrow the buyer-language stories and scope clarity—not its client logos, results or scarcity claims.
Head to head
Choose two concepts. These panels show their narrow layouts; open either full-size to judge its desktop composition.
No concepts shortlisted yet. Choose “Shortlist” on any design.
Design research · refreshed November 10, 2026
Borrow the principles. Not the costume.
Our earlier research covered seven agency sites. This round revisits useful references and adds adjacent service/design businesses. Appearance does not prove conversion performance.
Main Street Operator ↗
Field-business relevance and a human founder presence. Borrow the respect for people doing the work—not the name, testimonials or operating claims.
Designjoy ↗
A legible service model, straightforward process and practical FAQs. Borrow the clarity—not an unlimited-service promise or a pricing model Jax cannot support.
Instrument ↗
Confident typography, space and work-first presentation. Borrow visual hierarchy—not enterprise positioning or a portfolio we do not have.
Clay ↗
Large visual surfaces, confident typography and room to breathe. Borrow the art direction—not enterprise claims, client logos or project imagery.
Cohere ↗
A short opening promise, editorial hierarchy and clear routes into deeper pages. Borrow the pacing—not its product positioning or customer proof.
Treg ↗
An interactive hero object makes a complex connection visible. Borrow the visual explanation—not its sculpture, code, identity or tool-provider claims.
Clay.com — the workshop-animation reference
Clay.com ↗ is the source of “GTM engineers build on Clay,” distinct from Clay.global above. Its hero uses a pre-rendered looping video. Jax Workshop uses original locally rendered 3D artwork and selectable business-function examples, not Clay’s assets or customer proof.
What Arthur recommends for agency websites
Make the intended customer and benefit clear immediately, pair a real-world problem with a specific potential fix, explain the offer and price, and answer objections. These are hypotheses to test—not proof of conversion. Use customer proof only when it actually exists.
Watch the Liam Ottley × Arthur interview ↗ · Read the research notes ↗
Nate Herk’s useful design principles
Brand system before page generation; intentional visitor journey; purposeful motion; screenshot and mobile verification; specific feedback instead of endless “make it better” iterations.
Design-process article ↗ · Forced-iteration experiment ↗ · Full research note
How to review
- Pick two or three directions, rather than trying to choose a final website immediately.
- Be specific: “the headline size from 03, the colors from 01, the stories from 05.”
- Say what feels wrong too: too corporate, too beach rental, too busy, too much software.
- Use Export feedback and send the JSON back. Notes stay in this browser; they are not automatically sent or synced to us.