Skip to content

Defending a finding with ten minutes on the agenda

Ten minutes forces hard choices about what to leave out. What survives the cut, what goes in the appendix, and the two sentences that have to open it.

Three platforms, three answers, one budget to defend. Your GA4 export already holds the answer, and the first finding is free and never leaves your browser. Get your first finding free

By , Founder & CEOUpdated 3 min read

Ten minutes is enough if you decide in advance what you are not going to say. Most presentations fail by covering the method thoroughly and running out of time before the decision.

The ten minutes

MinutesContent
0 to 1The design and its limits, in two sentences
1 to 4The per-channel table, read aloud once
4 to 6The gap against platform numbers, with the ratio
6 to 8The decision you are asking for
8 to 10Questions

The two opening sentences

The first names the design: this is an observational causal estimate, not a test. The second names the limit: three channels could not be measured at their current spend, and they are listed at the bottom.

The table

Per channel: estimate. Read it once, aloud, slowly. Do not walk through the method for each channel; if someone wants that, it is minute eight.

Point at the widest interval yourself before anyone else does.

The gap slide

Have the ratio ready: the sum of platform-claimed revenue for the window divided by what the store actually took. Above one is expected and the size is the point. This is the two minutes that most often changes how a room reads its dashboards afterwards, and it needs no statistics. Method in the claim ratio.

The ask

Make it specific and small. Not "we should change our attribution philosophy" but "hold this channel's budget steady for four weeks so we can read it properly", or "reduce this one by a third and re-read in a month". A small concrete ask survives a short meeting; a large abstract one does not.

The structure for a cut recommendation is in which channels to cut, for the CFO.

What goes in the appendix

The method. The window justification. The channel-by-channel notes. All of it belongs in a document you can send afterwards, and almost none of it belongs in ten minutes.

The failure mode to avoid

Spending seven minutes establishing that the method is sound and two minutes on the finding. The room does not need to be convinced of causal inference. It needs a bounded claim and a specific ask.

Frequently asked questions

  • How do I present attribution in ten minutes?
    One minute on the design and its limits, three on the per-channel table read aloud, two on the gap against platform numbers, two on a specific ask, two for questions. The method itself belongs in an appendix.
  • What should the first two sentences say?
    The first names the design, such as an observational estimate rather than a test. The second names the limit, such as which channels could not be measured. Both in the first minute, before anyone raises them.
  • What kind of ask survives a short meeting?
    A small concrete one: hold this channel steady for four weeks so it can be read properly, or reduce that one by a third and re-read in a month. Large abstract asks about measurement philosophy do not survive ten minutes.

Go deeper: Incrementality testing, explained.

Sixty-second versions of these ideas: Causality Engine on YouTube Shorts.

Have an audience of ecommerce operators? Earn 20% recurring commission by recommending the €99 read.

Keep reading

Terms in this article

Browse the full glossary

Your platforms guess.
We run the math.

Upload a GA4 export and see what each channel caused, next to last-click, in 1–2 minutes. The read is yours to keep.

The free finding runs in your browser. Your file never leaves it. The full read is €99, refundable within 30 days, no questions asked. Prices exclude VAT.