Conversion Path Audit

The Conversion Path Audit is the flagship work at Service Routepoint. It is for product, design, and growth pairs who already have an app in market and can name the step they care about — yearly plan, account creation, first saved item — but cannot honestly say which earlier screen loses people.

Who it is for

Teams that own a live conversion sequence and can grant access to session recordings, current event names, and a walkthrough of the build on a staging or production account. We work most often with subscription apps, marketplace apps, and utilities that added a paywall after launch. We do not take pre-launch prototypes with no traffic.

Result

You receive a written path: each screen in order, the event that marks it, the stalls we could evidence, and the two or three changes worth making first. The document is meant to be argued with in a working session, not filed as a score.

Included

• Kickoff at the Manchester studio or a scheduled call, using the screen list you send in advance
• Reconstruction of the conversion path from recordings and event names you already collect
• A drop-off note for each stall we can evidence, tied to a screen and a timestamp range
• One readout with the pair who can change those screens
• A short appendix listing event names that cannot currently reconstruct the path

Excluded

• Building or hosting analytics software
• Running paid acquisition
• Redesigning the entire app
• Ongoing monitoring after the readout, unless you book a later clinic

Provider and process

Work is led by a path reviewer from Service Routepoint, with a second reader on the written path before the readout. Week one is reconstruction. Week two is evidence and draft. Week three (when needed) is the readout and a revision pass on the written path.

Duration, place, preparation

Plan two to three weeks. Briefings can be at Office 6, 76 Placeholder Street, Manchester ZZ2 2AE. Distributed teams join remotely. Before kickoff we need: a current screen list, access to recordings, the event dictionary, and one person who can answer “what did we intend this prompt to do?”

Constraints

We will not invent a conversion rate target. If recordings are sparse, the written path will say so and we will lean harder on event names and a live walkthrough. If legal or privacy rules block recording access, say that on the briefing — we can work from event exports and a supervised account tour instead.

Price

Fixed project fee after the scoping call. The fee reflects the number of distinct paths (for example free user versus returning subscriber) and whether a second language build must be read. We do not sell monthly licences.

Next step

Request a briefing and name the screens between first open and the step you care about.