This is a fictional example built to show the format, scoring model, and evidence standard of a Product Truth Audit. It is not derived from any real client engagement.
31 / 60
Loopline's core loop works once a user is past onboarding, but the checklist bug in F-01 is actively costing activated signups, and the pricing-page 404 in F-02 is costing paid conversions outright. Neither requires a rebuild — both are fixable within a day of focused work. The bigger structural gap is operational readiness: there is no visible error tracking, so the team likely does not know how often F-01 and F-03 are happening in production right now.
Reproduced on Chrome desktop and Safari iOS: completing step 2 of onboarding (connect a workspace) does not update the checklist state. Users we simulated as first-time signups re-attempted the step three times before abandoning.
"Start free trial" on /pricing points to /signup-trial, which returns a 404. The correct route is /signup?plan=trial.
Measured with Chrome DevTools network throttling (Fast 3G / 4x CPU slowdown). The delay is dominated by a client-side data fetch waterfall — three sequential requests before any dashboard content renders.
Two test accounts hit different behavior at the same usage threshold — one was blocked, one was not. This points to a backend limit check that isn't applied uniformly, but confirming the cause needs backend access.
We forced three API failures (offline toggle, malformed request) and saw no user-facing error state and no evidence of server-side capture. Confirming this needs read access to the error-tracking dashboard, if one exists.
Marketing site buttons use 8px radius; in-app buttons use 4px. Minor, but it reads as two different products stitched together.
Reminder: everything on this page — the product name, scores, and findings — is fictional and built for illustration. Real reports are built from a live review of your product and will not resemble this one.