- What do you need from me to start?
- A link to the product and one sentence about who you built it for; a test account helps if the core flow sits behind a login. No PRD, no analytics export: the teardown reads your product the way a new user does.
- Does a teardown cover the whole product?
- The scope is fixed: landing, onboarding, and one flow you name as core; the places where a new user decides to stay or leave. That frame keeps the findings specific and delivery inside 3–5 business days. Two flows that both worry you is a conversation before booking, not a bigger invoice.
- Can you also fix the problems you find?
- Yes, in a separate engagement. Every finding names the problem and the fix, with the evidence behind it, so your team can act without me. When you'd rather the fixing hands were mine, that conversation usually becomes a prototype sprint or a full build.
- What happens if the teardown misses the mark?
- One revision round. The teardown owes you findings that fit your product and leave you knowing what to fix first; if you read it and still don't know what to do on Monday, that's on me. What nobody can honestly promise is a conversion lift.