The work comes in three shapes. All of them start the same way: a short call about the number you’re trying to move.
A structured walk through your funnel: where users leak, which segments diverge, and what your data already knows. The deliverable is a findings readout and a prioritized test roadmap: what to test first, and why. This one is my hands — I do the analysis, you get the roadmap. It’s built for your team to run with or without me. Scope is set on the intro call.
The program starts with the audit and keeps going. The same funnel walk and prioritized roadmap, then the machinery to run experimentation as a standing discipline rather than an occasional event: cadence, win thresholds, segmentation tracks, and the ideation loop that feeds them. Depending on your team, I build the first tests myself or train your people to run the cycle without me. The goal is a program that outlives the engagement.
For when the constraint is process rather than conversion: hours going where they don’t need to. The engagement starts with a walk across your teams and workflows — where the time goes, what the handoffs cost, and where the openings are. AI takes the load where it earns the place; simpler fixes take the rest. What gets built ships with review and measurement, so the gains are counted rather than assumed. The 82% in Chapter 02 started with that walk.
Not everything fits one of the three shapes. If your situation sits outside them, or something else on the site caught your attention, I’m happy to talk it through. Same short call.