HOW WE WORK

Positioning comes before pixels. Everything else follows from that.

Sixty-plus engagements have taught us one thing repeatedly: the projects that go badly are almost never badly designed. They are badly decided. So we settle what the work has to claim before anyone opens a design file, and we keep the same senior team on it through to launch.

Sixty-plus engagements have taught us one thing repeatedly: the projects that go badly are almost never badly designed. They are badly decided. So we settle what the work has to claim before anyone opens a design file, and we keep the same senior team on it through to launch.

Sixty-plus engagements have taught us one thing repeatedly: the projects that go badly are almost never badly designed. They are badly decided. So we settle what the work has to claim before anyone opens a design file, and we keep the same senior team on it through to launch.

One team

strategy to launch

20 hrs

fastest full site, designed and launched

0

handoff between disciplines

60+

teams shipped

A brief is a starting position, not a specification.

Most projects arrive with the problem already diagnosed: we need a redesign, we need a rebrand, we need a migration. About half the time the diagnosis is wrong, and the actual problem is one layer up. We would rather find that out in week one than deliver the wrong thing beautifully.

So the first phase is genuinely allowed to change the scope. On Primefold that meant a full competitive scan and message architecture before a single screen. On Xpander it meant using a migration as the chance to simplify a CMS structure rather than reproduce it.

1. Scoping

What is actually going wrong, what success looks like, and what we would not take on.

2. Positioning

Category, claim, proof and language rules. The argument the work has to make.

3. Direction

Two or three real visual routes, tested against the hardest screen, not the easiest.

4. Design

Full design in Figma, including the states and pages nobody enjoys designing.

5. Build

Production in Framer by the same team, with CMS structure and components built to last.

6. Handoff

QA, redirects, analytics, documentation, and a project your team can actually run.

What working with us looks like in practice.

We iterate more than most studios and we say so up front. On Primefold we kept reworking the homepage until the claim was sharp enough to carry the site, and both sides pushed on it every round. AG2 went the other way: full design and development in under twenty hours, because that project genuinely needed speed. We scope the process to the problem.

We iterate more than most studios and we say so up front. On Primefold we kept reworking the homepage until the claim was sharp enough to carry the site, and both sides pushed on it every round. AG2 went the other way: full design and development in under twenty hours, because that project genuinely needed speed. We scope the process to the problem.

Fast when it should be

AG2: complete design and development in under 20 hours, launched.

Slow when it matters

Primefold: as many rounds as the argument needed, because the argument was the deliverable.

Long when it earns it

Create Video: a partnership running since 2020, still shipping.

How we communicate

Shared Slack channel, work in progress shared early, and direct answers about what is going badly. No status theatre.

What we need from you

One decision-maker who can say yes, access to a real customer or two, and honesty about internal disagreement.

Typical agency rhythm

Kickoff, silence, a big reveal, defensive feedback rounds, and a launch nobody feels ownership of.

How we run it

Continuous visibility, ideas killed early rather than defended late, and a client who has been in every meaningful decision.

Questions people ask before starting

How long does a project take?

A focused landing page: two to three weeks. A full marketing site: six to ten. A 200-page migration: months, mostly planning.

Who actually does the work?

The senior team you meet. We do not sell a founder and staff a junior.

Can you work with our in-house team?

Often the best setup. We handle the parts you are missing and hand back a system your team can extend.

Do you do build-only?

Yes. If your design and positioning are settled, we will scope a build and skip the strategy phase.

What if we disagree with the direction?

Good. That usually means the positioning is not settled yet, and that is a much cheaper problem to fix in week two than week ten.

What happens after launch?

Documentation, a handoff session, and an iteration window. Most clients keep working with us; none are locked in.

Want to know what your project actually is?

Bring the problem rather than the brief. The first conversation is usually about whether the thing you asked for is the thing you need.

Bring the problem rather than the brief. The first conversation is usually about whether the thing you asked for is the thing you need.

Start a project