Launch Preppers
Pre-launch SaaS review
Pre-launch reviews that find the broken buttons, the confusing onboarding, the missing legal pages, and the 30 other things your team stopped noticing six months ago.
Kim Hald, solo SaaS reviewer. I also write internal product reviews for AppSumo's launch team, where my job is to be direct about whether a tool is ready for their platform.
Most SaaS founders test their own product. The problem is obvious: you built it, so you know where everything is. Your users don't. They click the wrong button, miss the onboarding entirely, get confused by your pricing page, and leave. A pre-launch review catches what you can't see anymore because you've been staring at it for months.
I review your tool the way a real user would on day one. Except I write down everything that's wrong, grade it, and hand you a report.
Here's what I look at:
First impressions, ease of use, onboarding flow, UI/UX design, mobile responsiveness.
See full breakdown ->Product DepthCore features, integrations, documentation quality, and whether your support actually helps.
See full breakdown ->Technical HealthPage speed, performance in normal use, your landing page, and the bugs I find.
See full breakdown ->Business ReadinessPricing clarity, legal pages, product roadmap, and how you stack up against competitors.
See full breakdown ->Go-to-MarketSEO basics, social media presence, review site listings, Product Hunt readiness.
See full breakdown ->The VerdictPros, cons, overall assessment, and a prioritized list of what to fix first.
See full breakdown ->What you actually get.
A PDF report. Not a summary email, not a slide deck, not a 15-minute call where I tell you "it looks great, maybe fix a few things."
The last report I delivered was 34 pages. It covered 12 graded sections from first impression to competitor analysis, included 14 bug reports with screenshots and video recordings, and ended with a prioritized list of suggestions ranked by impact.
You also get:
Video recordings of bugs that are hard to explain in text. I test on desktop (Windows, Firefox) and mobile (Android, Brave), and when something breaks, I capture it.
A follow-up window after delivery where you can ask questions about anything in the report by email. If something is unclear or you need more detail on a specific finding, I'll clarify it.
Want to see what a real review looks like? I have an anonymized sample report from an actual client engagement. Names, URLs, and branding have been removed, but the structure, depth, and tone show the kind of report you can expect.
34 pages. 12 graded sections. 14 bug reports. Real findings from a real tool.
An anonymized pre-launch review of the installation, control, and removal friction around a useful product core.
The product could perform its central job well. Its result was useful, and one configurable part of the workflow gave customers a practical way to adapt repeated actions to their own needs....
Read case study
A risk-based way to connect technical testing with the customer journeys that decide whether a SaaS is ready to launch.
Learn how to build a risk-based SaaS testing plan that connects functional, security, performance, usability, and acceptance evidence to customer journeys.
Read article
A practical way to inspect the full SaaS work path, from public promise and access to recovery, handoffs, and repeat use.
Learn how to inspect SaaS UX across the public promise, access, setup, recurring work, uncertainty, recovery, and team handoffs before launch.
Read article
A practical guide to diagnosing stalled use, defining repeatable value, and measuring whether a SaaS earns a place in real work.
Learn how SaaS product adoption stalls after activation, then define a value event, diagnose workflow friction, and measure recurring use and retention.
Read articleYour launch gets one first impression.
Users who hit a broken feature on day one don't come back to check if you fixed it. They leave, and they tell people. A pre-launch review finds the problems while you can still do something about them.
If you're building a SaaS tool and launch is on the horizon, let's talk. A 30-minute call is enough to figure out if a review makes sense for your product.