Why a sprint beats a month-long redesign
The 7-day sprint exists because most landing page problems are not design problems. They are messaging problems wearing a design costume. A week forces you to fix the message first, because there is no time to polish a wrong one.
The order that works: day 1 rewrite the message, days 2–3 design, days 4–5 build, day 6 polish, day 7 handoff. Move a wrong message forward and you will redesign twice.
Day 1: the message is the design
Start with one sentence: who it is for, what it does, why it matters. Then the four blocks — headline, proof, offer, next step. Write them as plain text before any design work. If the words do not stand alone, neither will the page.
The single highest-leverage change in most sprints: cutting features from the hero. One outcome, not three.
Days 2–3: design against the words
Layout comes from the message hierarchy, not from inspiration. The headline gets the biggest type, the proof gets its own row, the CTA gets contrast. Every element earns its position or it leaves.
Typography and spacing carry 80 percent of the polish. A strict type scale and a consistent grid do more than any illustration.
Days 4–7: build, then measure
Handoff includes the code, not just a Figma file. You should own the build: it stays fast, it stays accurate, and you can update it without a designer.
Launch day is day 8 of the work. Set up one conversion event — a click, a form, a booking — and give it two weeks before judging.