How a review actually works
Hiring a stranger to test your unreleased product is a leap of faith. You want to know what happens after you book the call, what I need from you, how long it takes, and what shows up in your inbox at the end. Here is the whole process from first contact to final report, with no surprises.
Step 1: Book a call
Pick a slot on my calendar. The call is 30 minutes, free, and there is no commitment to book a review afterwards. We use this time to figure out if a review makes sense for where you are in your launch.
On the call, I want to understand:
What your tool does and who it is for. Where you are in the launch process: alpha, beta, or about to ship. What you are most worried about getting wrong. What your timeline looks like. Whether there are specific areas you want me to focus on or skip.
By the end of the call, I will have a clear picture of your product and you will have a clear picture of what a review from me would actually look like for your specific situation. If a review is not the right fit, I will tell you. I would rather lose a sale than waste both of our time.
Time: 30 minutes.
Step 2: Scoping and quote
After the call, I send you a written scope and a quote within 24 hours. The scope spells out which sections of the review apply to your product, which I am skipping, and any custom sections I am adding. The quote is a fixed price based on the scope, not an hourly rate that can balloon.
Pricing depends on the size of your product, the number of user flows I need to test, the depth of testing you want, and the turnaround time. A simple single-purpose tool takes less time than a multi-product platform with admin dashboards, integrations, and complex billing. I size every quote based on what your product actually needs.
If the quote works, you reply yes and we book a start date. If not, no hard feelings.
Time: 24 hours after the call.
Step 3: Access and kickoff
Before testing starts, I need a few things from you:
Login credentials for a test account, ideally with the same permissions a real paying user would have. If your tool has multiple plans, give me access to the tier you want me to evaluate. If there is a free trial signup flow, I will go through it as part of the review.
Documentation links, if any. I will read your docs the way a confused user would, but it helps to know what is officially available.
Contact info for whoever I should reach out to if I get fully stuck. I try not to bother you during testing, but sometimes a tool is so broken I cannot proceed without asking a question.
A list of competitors you want me to compare against in the Competitor Analysis section. Two or three is plenty.
Any specific concerns or known issues. If you already know your onboarding is rough, tell me. I will still test it, but knowing where you suspect problems helps me focus.
Once I have everything, I confirm the start date and the testing begins.
Time: Usually within a few days of accepting the quote, depending on your availability.
Step 4: Testing
This is the part where I actually use your product. I test on desktop and mobile, in two browsers, across multiple sessions over several days. I do not bang through it in one afternoon. Spreading the testing across days catches things you would miss in a single session, like state issues, email confirmation flows, and bugs that only show up after a few uses.
While I test, I take notes, screenshots, and video recordings of bugs that are hard to capture in text. Everything goes into a structured outline that becomes the report.
I usually do not contact you during testing. The whole point is that I am acting as a regular customer who just signed up. A regular customer does not get to ping the founder when something is confusing. They figure it out, give up, or close the tab. I do the same, then I write down what happened. If I find a critical issue I think you need to know about immediately, or if the product is so blocked that I cannot continue, I will email you. Otherwise you will not hear from me until the draft is ready.
Time: A typical review takes about a week of testing. Larger products or rush requests can shift this either direction, but a week is the baseline.
Step 5: Draft report
When testing is done, I write the report. Every section gets a star rating, a clear explanation of what I found, screenshots where helpful, and where relevant, a specific suggestion for how to fix it. The bug reports section includes steps to reproduce. The suggestions section is prioritized, so you know what to work on first.
The draft comes to you as a PDF. I do not deliver Google Docs, Notion pages, or shared workspaces. A PDF is final, portable, and you can hand it directly to your developers or your team without worrying about access permissions.
Time: 3 to 5 business days after testing wraps.
Step 6: Delivery and follow-up
You get the final PDF report by email. After that, you have a follow-up window where you can ask me questions about anything in the report. If something is unclear, if you want more detail on a specific finding, or if you need help understanding why I rated something a certain way, just email and I will clarify. The follow-up is included in the price of the review, not an extra service.
If you want me to retest specific things after you make changes, that is a separate engagement, but I will quote it at a reduced rate because I already know your product. Most clients do not need this. Some do.
Time: Final report delivered, follow-up window open for two weeks.
The whole process, end to end
For a typical engagement, here is how it usually breaks down:
Day 1: Discovery call Day 2: Scope and quote sent Day 3 to 5: You review the quote, accept, and provide access Day 6 to 12: Testing Day 13 to 16: Draft report written Day 17: Final PDF delivered Day 17 to 31: Follow-up window
So roughly two to two and a half weeks from first call to final report. Faster turnarounds are possible if your timeline is tight, slower is fine if your launch is further out. We agree on the schedule during scoping and stick to it.
Ready to start?
Book the discovery call. We will figure out the rest from there.