Guides / Guide
How we run a product audit before a relaunchTwo weeks, then a written plan
What we look at in the two-week Relaunch audit, what you give us, what the written plan holds and how it turns into the rebuild and the relaunch.
Our product audit before a relaunch takes two weeks and ends in a written plan. We read what is live: the product as your users meet it, the code and data under it, and the brand and site around it. The plan says what to keep, what to fix and what to rebuild, in what order. The audit is the first part of the Relaunch project, not billed on its own. After it, the rebuild and the relaunch run from that plan, as set out on our pricing page.
Who a product audit before a relaunch is for
You have a product people use today, and you have raised. Somewhere along the way the product stopped matching the company. Maybe the first version was built fast by a freelancer or on a no-code tool and now every change takes longer than it should. Maybe the core flow works but loses people halfway. Maybe the brand still looks like the pitch deck from two rounds ago.
That is the situation our Relaunch package is built for. It is one of the two ways onto The Launch Path, and it differs from the other one in where it starts. A founder with an idea or a first version starts with product strategy, because there is little to learn from yet. You already have a product, users and usually data, so we start by reading all of that before we suggest changing any of it. Our guide to the path from idea to launch covers the other entry.
If you are not sure which one fits, say so on the apply form. We confirm it with you once we have read your answers.
Relaunch at a glance
Relaunch runs in three parts, each with its own outcome.
- The audit: two weeks on what is live, ending in a written plan.
- The build: the rebuild, from the plan, with a working build you can click through every week.
- The launch: the relaunch film and its cutdowns.
After the audit, the plan sets how long the build and the launch take. You leave with the relaunched product, its refreshed brand and a relaunch film. The code lives in our private repository while we work and is handed over to you at the end.
Payment follows the same shape as Zero to launch: 50 / 25 / 25, at kickoff, when the build starts and at launch, each on a sign-off with you. The audit is part of the project, not billed on its own.
There is no public price. We scope the rebuild from the audit plan itself, which is the main reason the audit comes first: until we have read what is live, any number we gave you would be a guess.
What you give us
The audit is only as good as what we can see. Before it starts, we ask for access to the things that tell us how the product is built and how it is used. The exact list depends on your product, but it usually covers:
- The product itself, with a test account for each kind of user it has, such as an admin and a regular member.
- The code repository, read only.
- The analytics you already collect, whatever tool it sits in.
- Error tracking and logs, if you have them.
- The services the product calls: payments, email, push notifications, any AI provider.
- App store listings and reviews, for a mobile product.
- Your brand files and the current site.
- Anything you have learned from users: support tickets, interview notes, survey results, a churn spreadsheet.
We also ask for time. We need one person on your side who knows the product’s history and can answer questions during the two weeks. A kickoff call at the start, a short check in the middle and a walkthrough of the plan at the end is the usual rhythm.
You do not need to tidy anything first. A messy repo or a half set up analytics account is useful information in itself.
What we look at
We look at the product from the outside in. We start where your users start, and only then open the code.
The product as your users meet it
We use the product the way a new customer would, from the first screen they land on to the moment it does its job for them. Then we do it again as a returning user. We map the core flows end to end and write down every place where the product slows people down, confuses them or undersells what it does.
For this pass we judge the screens against established usability principles, the method Nielsen Norman Group describes as a heuristic evaluation, where evaluators check a design against a set of guidelines that make systems easy to use. We check the basics of accessibility against WCAG 2.2, the W3C’s guidelines for making web content usable by people with disabilities: contrast, keyboard use, labels, text size.
What your users already tell you
Your users have been telling you things for a while, in your analytics, your support inbox and your store reviews. We read all of it and look for where the numbers and the complaints point to the same spot. A drop in a funnel step that also shows up in support tickets is a strong signal. One loud complaint with no trace in the data usually is not.
We also look at the market the way your users see it: what they would use instead of you today, and what people say about those tools. This is the same research our product strategy work starts from, only now there is a live product to hold it against.
The code, the data and the services
Then we open the repository. We read the code, the data model and the services the product calls before we form any opinion on rewriting it. Our development page puts the rule plainly: we read what is already there before we write a line.
What we want to know at this layer:
- Which parts of the code are sound and can stay as they are.
- Which parts work but will slow every future change, and need fixing.
- Which parts have to be rebuilt, and what depends on them.
- How the data is stored, and what a migration would involve if the model changes.
- Which integrations fail, and how often.
- Where the security risks are, such as leaked keys, outdated dependencies or weak access rules. We use the OWASP Top 10 as the checklist for common web application risks.
For the parts users feel directly, we measure speed. Google’s Core Web Vitals give three numbers for a web product: how fast the main content loads, how fast the page responds to input and how much the layout shifts while it loads. They are a fair, shared yardstick, and they make it easy to show you the before and after once the rebuild is done.
The brand and the site
Last, we look at how the product presents itself: the name, the mark, the type and color, the voice of the copy, and the site people find before they find the product. A brand made before the company knew who its best customers were can stop fitting as the company grows. We check whether the brand still fits the people actually paying you, and whether the site says what the product does today.
The written plan
The audit ends with one written plan. It is the document the rebuild starts from, so we write it to be argued with. Every recommendation in it traces back to something we found and can show you.
The plan covers:
- What we found, flow by flow and layer by layer, with screenshots, data and the code references behind each point.
- What to keep, what to fix and what to rebuild, with a reason for each.
- The new MVP line: what ships in the relaunch, and what waits until after it, with a written reason for each item that waits.
- The order of the work, cut into weekly slices so the first week of the rebuild already ends in something you can open.
- What happens to your users and their data on the way, including any migration and how the switch to the new version works.
- What the brand and the site need, from a light refresh to new work.
- The scope and price of the rebuild and the relaunch.
We walk you through it on a call at the end of the second week. You can question any part of it, and we change it where your answers show we got something wrong.
If a few focused fixes would do more than a full rebuild, the plan says so, and the scope reflects it.
From the plan to the rebuild
The plan then becomes the brief for the build. The same team that wrote it carries it into the work, so nothing is lost in a handover between the people who looked and the people who build.
The build stage covers three services that run together:
- App development rebuilds the product itself, for the web or for mobile. Where we found a no-code or freelance build that slows you down, we keep what works and rebuild the rest.
- Web design rebuilds the site to match the product and the refreshed brand, on the same tokens, so the two stay in step.
- Development handles the server, the data and the integrations, including any migration the plan calls for.
The brand work from the plan runs alongside, through our branding service. A refresh keeps what your users already recognize and fixes what no longer fits. New work starts from the positioning the audit confirmed.
Every week you get a working build you can open on a link or install on your phone, with a short note on what changed, what to try and what is still rough. Your feedback shapes the next week’s slice. We wrote more about why we show a working build every week, and it matters even more on a relaunch. You have a live product to compare against, so you can judge each week’s build against what your users have today.
The MVP line from the plan can move as we learn. When it does, we write down what changed and why, and agree what it means for the plan before anyone starts on it.
The relaunch
A relaunch has a different job from a first launch. Your current users need to understand what changed and why it is better for them. New users need a reason to look again at a product they may have already dismissed.
The launch stage makes the films that carry that story. With a launch film, you record a few takes on a phone from our script, and we set them wherever the story needs to be. We make one master film and cut it down for every channel you relaunch on. Product films are made from the real interface of the rebuilt product, so what people see is what they get when they open it.
When the product, the site and the films are ready, we set the relaunch date with you. Then the code, the brand guide and the documents from every stage move to you.
Questions to answer before the audit
Rough answers are fine. Whoever audits your product, these are worth thinking through before the first call.
- What made you decide the product needs a relaunch now? Name the moment or the number.
- Which flow matters most to your business, and where do people drop out of it?
- What do your best users love about the product today, the part a rebuild must not break?
- What do your support tickets and reviews keep coming back to?
- Who built the current version, and is anyone from that team still around to answer questions?
- Who on your side will make the call when the plan and your instincts disagree?
- Is there a date driving the relaunch, such as a raise, a conference or a contract?
If you can answer most of these, you are ready for a product audit before a relaunch. Tell us about the product on the apply form, and we will come back with whether Relaunch fits.



