LANDING SPRINT · 14 DAYS
DWG 03 / 05 · PRODUCTION

A page that closes the spend already aimed at it.

Wireframe, copy direction, design, and production build of one page that converts, on the CRO and GEO playbook from the first wireframe. Live this quarter, while the budget pointed at it is still in market. For teams who know what they need.
A-02 · WHERE THE SPEND LANDS

Your ad spend is already committed. This is the page that turns it into pipeline or wastes it.

Committed whether the page converts or not.
The paid campaign and the outbound are bought and pointed at this page, and the budget is committed whether the page converts or not. When the page cannot close, you keep paying for traffic that bounces, and the pipeline that spend was supposed to produce never arrives. The only question is whether the page earns it back.

Conversion built in from wireframe one.
So the Sprint builds conversion structure in from the first wireframe, and builds the page with clean, crawlable structure that AI assistants can read, instead of bolting either one on after launch.

Live before the spend burns another fortnight.
Fourteen days because one person handles the entire chain, so the page is live before the campaign burns another fortnight against a page that cannot convert. The trade is scope: one page, scoped tightly, shipped on a deadline.

TYPICAL PROJECT · 6+ WEEKS

5 handoffs. 6+ weeks. Telephone game.

Each handoff loses context. By the time it’s live, half the original intent has been refactored out of the page.
THE SPRINT · 14 DAYS

0 handoffs. 14 days. No drift.

One brain from brief to launch. Everything decided in phase 1 still readable in phase 4.
SECTION B · METHOD · FIG. 02

Fourteen days. Four phases. No drift.

Each phase has a fixed deliverable and a fixed handoff point. No phase opens until the previous one closes. Fourteen days is the deadline because the campaign spend is already running. Read this as a production schedule, because that is what it is.

Send a URL and a quick sentence.

Send the URL of your site, and a brief sentence on your project. We’ll assess the depth of engagement on a call. Kickoff within a week of signing. Page live fourteen days later.

FIX-LIST TRIAGE · ORDERED BY IMPACT

One page.
Everything it needs to perform.

Not a Figma file you have to hire someone else to build. A live page on your domain, on your platform, with your analytics wired up and schema already in the markup.
INSIDE THE CUT

When you want a deeper engagement:

DELIVERABLE 02 · 5 TESTS

Designed for conversions, built for handoff.

Run before launch. Highlight reel and last-mile fix list applied before you ever ship a pixel.

What’s installed, where events fire, how to edit the copy or swap the hero image without breaking anything. Plus a 30-minute live walkthrough with whoever maintains it.

PLATFORMS · YOUR STACK · NOT MINE

Built where your team already operates.

If your stack is something else, ask.

A-07 · PRE-KICKOFF

What usually comes up before the first call.

Seven questions that have come up on almost every Sprint scoping call. Short answers here, the rest on the 15-minute call.
Q.01
What if I need more than one round of revisions?

Each phase includes one revision round. We can work with you to scope out additional rounds either hourly or fixed.

Q.02
What platforms do you build on?

WordPress, Webflow, HubSpot, Shopify, Framer, Next.js, or static HTML. If your stack is something else, ask: most modern platforms are workable. Custom React or app-embedded pages are a different engagement.

Q.03
Who writes the copy?

Depending on the tier - we can work with copy provided by you - or we can create the copy to meet your goals for you.

Q.04
Can you run A/B tests on the page after launch?

Not as part of the Sprint. Ongoing CRO testing is a separate engagement, scoped after launch. The Sprint ships a page built on conversion principles: optimizing further over time is its own thing.

Q.05
What if I want to extend the engagement after launch?

Most clients do. Common follow-ons: a CRO Audit on the broader site, a second Sprint for a related page, or ongoing UX work. Scoped case by case after the Sprint ships.

Q.06
Should I do a CRO Audit before the Sprint or after?

If the new page is replacing an existing underperformer, audit first. If the page is for a new offer with no baseline, just ship the Sprint.

Q.07
What makes this a good fit?

You have a specific offer, product launch, webinar reg, lead magnet, campaign, that needs a dedicated page now. And you have an existing brand, or you're comfortable with a clean default system in order to faciliate a sprint.

A-08 · READY WHEN YOU ARE

Send a URL and a sentence. 15-minute call back within 48 hours.

Send the URL of your site, and a brief sentence on your project. We’ll assess the depth of engagement on a call. Kickoff within a week of signing. Page live fourteen days later.

Send a URL

One page, one sentence. I’ll reply with the first few things I’d fix, usually within a day.

    Start a project

    Pick what you are starting and where. I will come back with scope and a kickoff date.