Launches almost always go out with something missing. The problem is not the gap itself but not knowing which gaps can wait and which cannot. The twelve questions below exist to separate the two: you do not need to answer yes to all of them, but you do need to be able to explain why every "no" can wait.
What is a pre-launch audit?
A pre-launch audit is a single-session review of a brand's verbal, visual, technical and operational readiness before it goes live. Its purpose is not perfection but catching, in advance, the mistakes that would be expensive to fix after launch.
Ideally it is run two weeks before launch. Any earlier and unfinished items blur the picture; any later and there is no time to fix what it finds.
The twelve questions
Positioning and message
- Can you describe the brand in one sentence? One sentence covering who you serve, what you do and why you do it better. Ask three people on the team separately; if the answers differ, it is too early to launch.
- Is it clear which question you answer? What problem will a customer call you to solve? If that is not written down, the messaging will be scattered too.
- Is what you don't do defined? Out-of-scope areas should be written down. Brands that start with "we do everything" spend their first year on the wrong customers.
Identity and application
- Does the logo work in every context? Test it separately at small size, in one colour, on a dark background, as a favicon and inside a circular social profile. The most common problem is a horizontal logo cropped by the circular frame.
- Is the file pack complete? Are logo versions, colour codes, font files and basic templates in one accessible folder?
- Is the brand name written the same way everywhere? Is there consistency across capitalisation, spacing, abbreviation, the domain, social handles and the legal entity name?
Digital readiness
- Is the site fast on mobile? Most launch traffic arrives on mobile. A slow page damages the first impression in a way communication cannot repair.
- Is the search basics setup done? Title and description tags, structured data, a sitemap, a robots file that allows indexing, and analytics. The number of sites that launch with a forgotten "noindex" tag is higher than you would think.
- Do AI search engines describe the brand correctly? Ask conversational search tools about your brand. If their definition differs from yours, the description blocks and structured data on the site need to be sharpened.
Operations
- What happens when an enquiry arrives? Test the form, phone and messaging channels individually: who receives it, how fast is it answered, and what happens if it is not?
- Does the team give the same answer? Answers to questions on price, scope and timing should be written and shared. This is the inconsistency that spreads fastest after launch.
- Is there a plan for the four weeks after launch? A launch is a period, not a day. If the four weeks after the announcement are empty, the interest it creates goes unanswered.
How to read the result
| Number of "no"s | Meaning | Recommendation |
|---|---|---|
| 0–2 | Ready | Put dates on the gaps and launch |
| 3–5 | Risky but manageable | Close the gaps in the first three questions, then go |
| 6+ | Too early | Postpone; the problem is not preparation but foundation |
The weights are not equal: a "no" in the first three questions is heavier than one in question ten. A launch made with positioning unresolved requires a far more expensive correction later.
Three items most often postponed that should not be
- The post-enquiry flow. The site is ready, but who receives a form submission stays unclear. An enquiry lost in launch week does not come back.
- Handing the file pack to the team. The identity is ready but the team still uses the old deck. A launch begins the day the files in the team's hands are replaced.
- Measurement setup. When analytics are installed after launch, the data from the most valuable period is gone. Setup must be finished beforehand.
How we work at Circle
In launch projects we run this audit with the brand, screen shared. The part that takes longest is usually the first question: the one-sentence description. The moment everyone in the room can say the same sentence, the remaining eleven items become technical work.
Frequently asked questions
Does everything have to be ready to launch?
No. What is required is knowing the gaps and putting a date on the ones that can wait. An unknown gap is a risk; a known gap is a plan.
Who should run the audit?
Someone who can look at the brand from outside. A team working inside the project cannot see the gaps it has got used to, so include a fresh pair of eyes.
Is a soft launch a good idea?
Where uncertainty is high, yes. Opening to a narrow audience and collecting feedback makes the wide announcement sturdier. But a soft launch needs a plan too; going live quietly is not a launch.
When should the first measurement be taken?
Four weeks in. Data read earlier is distorted by the announcement effect; four weeks shows the real level after the wave of interest passes.
Next step
Run these twelve questions on your own launch. If more than three come back "no", get in touch to review your pre-launch preparation together.
