Frequently asked questions

It depends on the scope of your product. A simple single-purpose tool takes less time to test than a multi-product platform with dashboards, integrations, billing, and team accounts. I quote a fixed price after the discovery call once I know what I am actually testing.

What affects the price: the size of your product, the number of user flows I need to test, the depth of testing you want, and how fast you need it back. There is no standard package and no surprise hourly billing. You get one number, you decide if it works, that's it.

About a week of testing once I have access, then three to four days to write the report. From the discovery call to the final PDF in your inbox is usually two to two and a half weeks. Faster is possible if your timeline is tight. Slower is fine if your launch is further out.

Login credentials for a test account at the tier you want me to evaluate. A list of two or three competitors you want me to compare against. Any documentation or help center links you want me to check. A heads-up about any specific concerns or known issues. That is it. I do not need calls, syncs, or status updates while I work.

Yes. If you want an NDA in place before I see non-public product details, send me yours and I will review it before the discovery call. If you do not have one, we can use a simple mutual NDA template. Either way, your product details, login credentials, and the contents of the report stay between us unless you explicitly give me permission to use them in anonymized form as a case study.

SaaS tools across most categories. Website builders, CRMs, email marketing platforms, AI content tools, productivity apps, automation tools, browser extensions, developer utilities, and a long list of niche B2B tools.

That said, I only take reviews where I am comfortable with the product category and believe I can do a good, thorough job. If your tool is outside what I understand well enough to evaluate properly, I would rather say no than deliver a shallow review. If you are not sure whether your tool is a fit, ask on the discovery call.

That is what the discovery call is for. I do not have a blanket list of categories I refuse to work with. I do not automatically reject adult, gambling, crypto, or other categories some reviewers avoid by default.

What I care about is whether I can actually provide value for your specific product, whether I understand the category well enough to review it thoroughly, and whether there are legal or ethical issues that make the work a bad fit. If I do not think I can help, I will say so on the call and we both move on. No wasted time, no half-hearted engagement, and no subpar review just because I could have taken the job.

Critical bugs that block users from completing core workflows go in the report with the highest priority and a clear explanation of what is broken. If I find something that looks like a serious security issue, I will email you immediately rather than wait for the report. I am not a security researcher and I do not perform formal penetration testing, so my findings on the security side are limited to obvious things any user might stumble on. For real security testing, hire a security specialist. I will say so in the report if that is what you need.

The report is yours to use internally. Sharing the full report publicly is also fine if you want to, as long as you are not exposing private credentials, user data, or third-party information. Quoting from it in marketing materials is fine. If you want to use my name as the reviewer, check with me first so I know where it is being used and the quote is not framed as an endorsement. If you want to publish a stripped-down version of the report as a public credibility piece, that is a great use of it and I am happy to help format it.

You get a follow-up window of two weeks where you can email me with 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 a rating, just email and I will clarify. The follow-up is included in the price, not an extra service.

After the two weeks, the engagement is officially closed. If you want to come back later for a retest or a new review, we can talk about that as a separate engagement.

Yes, but it is a separate engagement. After you have made changes based on the report, I can run a retest focused on the issues I originally flagged plus any new areas you want me to look at. Because I already know your product, retests are quoted at a reduced rate compared to a fresh review. Most clients do not need a retest. Some do.

No. The work is done, the time was spent, the report exists. Refunds would mean I am working for free, and that is not a sustainable way to run a one-person service.

What I do offer is the follow-up window. If something in the report is unclear or you disagree with a finding, email me during the two-week follow-up period and I will explain my reasoning, dig into the issue further, or update the report if I genuinely got something wrong. I would rather fix a problem than leave you unhappy. But the engagement is paid in full at delivery, not contingent on you liking what I found.

If your product is in such early shape that you are worried a review will not be useful, that is exactly what the discovery call is for. I will tell you on the call if I think a review is not the right fit yet. Better to find out before you pay than after.

A QA contractor finds bugs. A UX designer evaluates the interface. A pre-launch review covers both, plus the things neither of them looks at: your landing page, your pricing clarity, your legal pages, your marketing presence, your competitor positioning, and the synthesis of how all of those pieces fit together as a launch.

QA tells you what is broken. UX tells you what is confusing. A pre-launch review tells you whether you are ready to ship. They are not the same job, and the right answer is usually all three at different stages. If you only have budget for one, a pre-launch review gives you the broadest coverage at the moment when broad coverage matters most.