What should you do after a brand sprint?
After a brand sprint, apply the new identity where customers see it most, starting with the website. A brand that only lives in a Figma file has cost money without changing how anyone sees your company. The sprint's applied screens are the bridge: they're the first designs of the new site.
The order for most startups is website, then pitch and sales decks, then product UI, then everything else. The website comes first because it's where investors, buyers and candidates check you out, often before they ever speak to you. Our hub on what a brand sprint is covers the sprint itself; this guide is about what comes next.
How do you go from brand sprint to website?
You go from brand sprint to website by turning the sprint's screens into a page plan, writing the remaining copy, designing the missing pages and building. The sprint has already answered the hardest questions: positioning, headline, type, color and how the hero looks.
Audit the sprint output
List which screens and sections exist from the sprint, and which pages the site still needs.
Plan the pages
Decide between one conversion page and a multi-page site, based on how your buyers decide.
Finish the words
Extend the sprint's headline and voice rules into full page copy. Words before layout, again.
Design the remaining pages
Use the sprint's styles and components so new pages match the approved screens.
Build and connect
Build the site, connect a CMS if you'll publish often, and set up analytics and forms.
Launch with care
If the old site has traffic, plan redirects and search checks before launch day.
When one team owns the sprint and the build, the first three steps are short, because the person who wrote the headline is the person who builds the hero. When the files go to a new developer, budget time for a handover so decisions aren't lost.
Should you build a landing page or a full website after the sprint?
Build a landing page if you have one audience, one offer and one action you want visitors to take. Build a multi-page website if buyers need to compare features, read about security, check pricing or see proof across several use cases before they talk to you.
Landing page | Multi-page website | |
|---|---|---|
Best for | Launch, waitlist, single offer, pre-seed | Series A sales, several audiences or products |
Pages | One conversion page | Home, product, pricing, about, blog and more |
Content updates | Occasional | Regular, through a CMS |
Designify price | $6,000 fixed | $8,000 for up to 6 pages, +$500 per extra page |
Built with | Custom design, Next.js, animated | Custom design, Next.js, CMS, animated |
Many pre-seed teams start with the landing page and add pages as the sales motion develops. That's a sensible sequence, as long as the first page is built so it can grow into a site. Delivery timelines for either package are scoped on the intro call.
What does the full path cost, from sprint to site?
With Designify, the path from brand sprint to website is fixed at every step: $3,000 for the sprint, then $6,000 for a landing page or $8,000 for a website of up to six pages. You know the total before you start.
- Brand & design sprint, with 10 explorations
- $3,000
- Landing page: custom design, Next.js, animated
- $6,000
- Website up to 6 pages, +$500 per extra page
- $8,000
- Retainer for ongoing design and development
- $6,000/mo
The sprint's 10 website or product explorations aren't a website, but they mean the build starts from approved designs rather than a blank file. If you're not sure we're the right team for the build, our $1,000 trial week lets you test how we work first. See our pricing for every package.
Hypothetical example: choosing the path after a sprint
For example, suppose a seed-stage startup finishes a sprint with a new identity and screens for a homepage hero, a features section and a pricing block. They're raising in a few months and sell to one buyer type. A $6,000 landing page built from those screens covers the raise.
Now suppose a Series A startup with three products and a sales team finishes the same sprint. Buyers need product pages, a security page and pricing. A $8,000 website of up to six pages, plus $500 for each page beyond that, fits better. Both start from the sprint's approved designs.
What should you check before launching the new brand website?
Before launch, check that the new brand is consistent everywhere visitors land and that the old site's search visibility won't be lost. The research we reviewed points to the Workfront rebrand, formerly AtTask, as an example of a rebrand that hurt organic visibility when the website side wasn't handled carefully.
- Redirects. Every old URL with traffic or links should point to its new equivalent.
- Search checks. Titles, descriptions and structured data carry over, and the new site is crawlable.
- Brand consistency. Favicon, social previews, email signatures and the deck match the site.
- Forms and analytics. Every form submits and every conversion is tracked before you announce.
For the full launch-day list, see brand launch website: what to ship on rebrand day. If the sprint followed a change of direction, rebranding after a pivot covers how to explain the change to existing customers.
What happens after the new website launches?
After launch, someone has to keep the site and brand current: new pages, updated copy, product changes and fixes. Decide who before launch day, or the site will slowly drift away from the brand you just paid for.
The options range from your own team editing a CMS to a monthly retainer with a design and development team; who updates your website after launch compares them. The first 90 days after launch covers what to measure and fix. And if you later outgrow a no-code site, Framer to Next.js migration cost explains what that move involves.
