Inigo AnguloContact
Work01How I think02Lab03Writing04
Writing / Kit

Checkout audit checklist: find the leak between the steps

ChecklistOptimizev1.0Updated November 5, 2026

A checkout and funnel audit checklist: rebuild the funnel per user, measure re-entry and time to convert, instrument the gaps, then test against a one page hypothesis. With a SQL sketch.

How to use it

  1. Run it before anyone proposes a redesign of payment. Payment is rarely the problem.
  2. The three numbers in step 1 decide where to look. Do not skip to experiments.
  3. Every experiment gets the hypothesis page before anything is built. No peeking, no winners called because the quarter is ending.
The checklist: checkout-audit.mdDownload
# 1. Rebuild the funnel per user (not per session)
- [ ] Every user who reached the final step in the period, events walked backwards.
- [ ] The same for users who reached checkout and did not convert.
- [ ] Entries per converter. Median above one: re-entry is your biggest surface.
- [ ] Time to convert. Hours, not minutes: the session model is lying to you.
- [ ] Exit step on the first visit: tells you where to put the memory.
- [ ] Watched session recordings of at least ten re-entries, with your own eyes.

# 2. Look for the gaps the stage counters miss
- [ ] Back button: two checkout entries, one person, counted as a drop.
- [ ] Tab switch: session timed out, the return starts again at step one.
- [ ] Return visit: cart, choices and progress lost between days.
- [ ] Price changed between visits, or between product page and last step.
- [ ] A form that cleared.

# 3. Check the commitment moment
- [ ] A returning visitor lands on the step they left, choices intact, one line acknowledging it.
- [ ] Cancellation terms and what happens after booking shown where the decision is made, not in a tab.
- [ ] Everything that can be asked after payment is asked after payment.
- [ ] The total on the product page is the total at the end. Any change explained before the button.

# 4. Instrument what you found
- [ ] checkout_reentry {step, hours_since_last_exit}
- [ ] cart_restored {items, age_hours}
- [ ] price_changed_since_last_visit {delta, reason}

# 5. One page per experiment, before anything is built
- We believe: <the change and the user behaviour it addresses>
- Because: <the evidence from steps 1 to 4>
- Primary metric: <one>   Guardrail: <one>
- Sample size: <n per arm>   Read date: <YYYY-MM-DD>
- If it loses: <what door this closes>
SQL sketch: funnel per user: funnel-per-user.sqlDownload
-- Assumes events(user_id, event, ts). Rename to your schema.
-- One row per user who reached checkout in the period.
with checkout_users as (
  select user_id,
         min(ts) filter (where event = 'checkout_start') as first_checkout,
         max(ts) filter (where event = 'purchase')       as purchased_at,
         count(*) filter (where event = 'checkout_start') as checkout_entries
  from events
  where ts >= date '2026-01-01' and ts < date '2026-02-01'
  group by user_id
  having count(*) filter (where event = 'checkout_start') > 0
)
select
  purchased_at is not null                                   as converted,
  count(*)                                                   as users,
  percentile_cont(0.5) within group (order by checkout_entries) as median_entries,
  avg((checkout_entries > 1)::int)                           as share_reentered,
  percentile_cont(0.5) within group (
    order by extract(epoch from purchased_at - first_checkout) / 3600
  )                                                          as median_hours_to_convert
from checkout_users
group by 1;

Prompt to use it

Paste with your event schema
Here is my analytics event schema (below). Write one query that rebuilds the checkout funnel per user, not per session, for <period>.
For converters and non converters separately, return: users, median checkout entries, share with more than one entry,
median hours from first checkout entry to purchase, and the most common exit step on the first visit.
State every assumption about event names. Do not invent columns that are not in the schema.

<paste the schema>

Why it looks like this, and where each part came from: Instrument the gaps, not the stages.

Changelog

More from the kit

Working on a funnel like this?

Finding the leak and proving the fix is what the conversion work looks like. Explore a conversion opportunity → Or email me.