Launch Preppers
A pre-launch review is not a 15-minute "looks good to me" call. It's a structured review of your product, your landing page, your legal pages, your marketing presence, and the parts around them that affect launch readiness. I test the way a real user would on day one, then I write down what's broken, what's confusing, and what's working. The result is a PDF report you can hand to your team and start fixing immediately.
The review is built around six pillars. Each pillar covers a group of related sections. Not every section applies to every tool, and sometimes I add custom sections for unique cases. What you see below is the default. What you actually get depends on what your product needs.
Pillar 1
This is where most launches fail. Your team has been looking at the same screens for months. You know where the buttons are. You know what every label means. New users don't, and they leave before they figure it out. I test as a first-time user and write down every moment of confusion.
The first 30 seconds. Does your landing page load fast and look professional, or does it have broken images and dead links? Does your dashboard make sense the moment I log in, or do I sit there wondering what to click? First impressions decide whether I keep using your tool or close the tab.
Can a new user actually do the thing your tool is supposed to do? I try to complete the core workflow without reading docs. If I get stuck, I write down where and why. If a button does nothing when clicked, I report it. If a feature is hidden three menus deep, I flag it.
What happens after signup? Is there a welcome flow, a tour, a checklist, anything? Or does the user land on an empty dashboard and have to figure it out alone? Onboarding is where free trial users either commit or quit, and most SaaS tools get it wrong.
Layout, hierarchy, color, typography, spacing, consistency. Not a graphic design critique, a usability one. Does the interface guide the user, or does it fight them?
Tested on a real Android device, not a browser dev tool resize. If your site or app breaks on mobile, I'll show you exactly where with screenshots. If you're a developer tool that doesn't need mobile, I'll skip this section.
Pillar 2
A polished interface doesn't matter if the product underneath is thin. This pillar looks at whether your tool actually does what it claims, how well it integrates with the rest of a user's stack, and whether someone can figure things out without emailing support every five minutes.
Are the core features present and functional? Are advertised features actually built, or are some still placeholder buttons that do nothing? Are the features competitive with what's already on the market?
Can your tool talk to the other tools your users already use? Native integrations, API access, webhook support, Zapier or Make compatibility. If your tool is an island, users will pick a competitor that isn't.
Are the docs complete, accurate, and easy to navigate? Are there video walkthroughs for visual learners? Is there a chat bubble or contact form for help? When I email support, do I get a useful response or a canned reply?
Pillar 3
The boring stuff that breaks launches. Slow pages. Broken buttons. Missing images. 404 errors on links from your own homepage. None of it is glamorous, all of it kills trust on day one.
How fast does your site and app load? I run it through GTmetrix and report the scores. I also test on real-world conditions, not just on a fast connection from a data center. Slow tools lose users before they even sign up.
Every bug I find gets a section with steps to reproduce, screenshots, and where applicable a video recording. Hard-to-explain bugs get a screen capture link so your developers can see exactly what happened. The last review I delivered had 14 bug reports.
Your landing page is your tool's first sales pitch. Dead links, missing images, inactive buttons, broken forms, unclear value propositions, missing CTAs. I test every element. If the landing page is broken, no amount of product polish behind it will save the launch.
Pillar 4
Your product can be strong and still fail at launch because the business around it isn't ready. Confusing pricing, missing legal pages, no clear roadmap, no idea what the competition is doing. This pillar covers the parts of your business that users see before they hand over a credit card.
Is your pricing page clear? Can a user understand what they get for each tier in under 30 seconds? Are the limits explained (per month or total? per user or per account?)? Are AI credits, storage, or seat limits ambiguous? Pricing confusion is one of the top reasons users bounce.
Privacy Policy, Terms of Service, Cookie Policy, Affiliate Disclosure where relevant. I check that each one exists and is linked from the footer. I do not assess legal validity, that's a lawyer's job, but I will flag missing pages that could create compliance issues in regions like the EU.
Do you have a public roadmap? Is it up to date? Users like knowing what's coming next. A stale or missing roadmap signals that the product is not actively being developed.
Quick comparison against the main competitors you listed during scoping. Where are you stronger? Where are you weaker? What features do they have that you don't, and does it matter for your target user? This is not a deep market research report, it's a sanity check.
Pillar 5
You can't launch a SaaS tool by just publishing the website and hoping. People need to find you, and the places they look need to have something to find. This pillar covers the parts of launch that happen outside your own product.
Meta tags, Open Graph tags, schema markup, sitemap, robots.txt, canonical URLs, page speed, mobile-friendliness. The basics that determine whether Google can index your site properly. Most pre-launch SaaS sites get this wrong because the founders are focused on the product, not the marketing.
Social media presence on Facebook, X, LinkedIn, YouTube, Instagram. Review site listings on G2, Capterra, GetApp, Trustpilot, Software Advice, Product Hunt. Google Business Profile if applicable. I check whether each one is set up, claimed, and ready for launch. Empty social accounts and missing review site listings are visible to anyone who searches your tool name. Both of those signal "not ready" to potential users.
Pillar 6
The synthesis. After grading every section, I pull it all together into a clear recommendation. Are you ready to launch, or not? What needs to be fixed before you ship? What can wait until after launch? This is where you get the honest answer most consultants will not give you.
A short list of what's working and what isn't. No fluff. Three to five strong points on each side.
The big picture verdict. If I were a paying user who just signed up, would I keep using this tool or ask for a refund? I have told clients their product was not ready to ship. I will tell you the same if it's true.
A ranked list of what to fix first. Critical issues that block launch, high-priority fixes for the first week, medium-priority improvements for the first month, and nice-to-haves for later. You leave the report knowing exactly what to work on next.
Not every review is the same
The six pillars above are the default. Your review might skip sections that don't apply to your product. A developer-focused CLI tool probably doesn't need a Mobile Responsiveness section. A solo SaaS without a team blog might not need a deep SEO audit. And sometimes a product has unique elements that need a custom section I don't usually include.
What you actually get is shaped by your product. We talk through it on the call and agree on scope before any work starts.
Ready to find out what's broken before your users do?
Book a 30-minute call. We'll talk about your product, your launch timeline, and what kind of review makes sense. No pressure, no upsell, no template pitch. If a review isn't the right fit for where you are, I'll tell you.