Client notes

Client notes

These notes come from booked Conversion Path Audits and clinics. They mention specific screens and constraints. They are not marketplace ratings.

Extended note: the restored trial clock

A Leeds subscription team asked for a Conversion Path Audit on the journey from a push re-open to the yearly plan. Checkout completed when people reached it. Recordings showed a restored cart that reset the remaining trial days two screens earlier. The paywall copy still spoke as if the original trial were intact. The written path named that restore state, the event that failed to distinguish it, and the copy block that needed a different sentence. The engineering pair already suspected the restore; they did not have it written against the paid step.

Extended note: permission before the core action

A Glasgow utility app booked a Drop-off Clinic on the notification permission. The clinic was useful and also slightly awkward: the prompt fired before anyone had saved a first item, so the refusal looked like a conversion problem when it was a sequencing problem. We wrote that the stall was real, and that moving the prompt would not, by itself, lift the later paid step. They still needed a separate reading of the paywall. That reservation stayed in the stall note.

Shorter notes

“The audit spent most of its time on the back-stack after a crash, which was not the screen we had asked them to look at. That was the right call. The paywall itself was ordinary.” — Product designer, Bristol marketplace app

“I wanted a single number for the board. They refused and sent a path with three stalls instead. Our engineer used the appendix on event names the same week.” — Product manager, Manchester

“The clinic ran long because we argued about what ‘account created’ meant. The written stall note still shows that disagreement, which is more honest than a smoothed version.” — Engineer, Edinburgh