Get a demo
Email & lifecycle

Experiment log template for a CRO test summary

Summarize a test with the hypothesis, the result, the call, and the next test — the summary a team trusts because it leads with the call, not with the chart.

Use this templateBook a demo
  • AgentKai
  • JobReporting
  • CategoryEmail & lifecycle
  • Integrations
    • Notion
    • Google Docs
    • Looker
    • Mixpanel
    • Slack
  • Last updatedAugust 2026
  • AuthorNarayan Prasath
KaiComplete
  • Notion
  • Google Docs
  • Slack

Summarize the pricing page CTA test we just closed.

  1. Pulled the hypothesis"Claim trial" beats "Start free trial" by 15% click
  2. Drafted the result12% lift, 95% confidence, 2-week test
  3. Named the callShip — "Claim trial" is the new default
  4. Named the next testTest "Claim trial" vs "Claim your trial" next

The log led with the call — ship "Claim trial" as the new default — and named the next test. The team shipped the call and queued the next test in the same meeting, which is the cadence that turns a test into a program. A log that ends with the call keeps the program moving.

An experiment log template is the summary a team trusts because it leads with the call. It fixes the shape — the hypothesis, the result, the call, the next test — so the summary reads as a decision, not a chart. A test that ends without a call is a test that wasted a week; the template makes the call the point of the log.

What is an experiment log template?

A reusable summary shape for a CRO test — the hypothesis, the result, the call, the next test — that a team can act on. The template fixes the shape so the summary reads as a decision, not a chart.

Build the summary

  • Hypothesis stated as a prediction
  • Result with the metric and the confidence
  • Call — ship, iterate, or kill — in the first sentence

Ship the program

  • Name the next test
  • Log the call so the next test learns from it
  • Ship the summary on the cadence the team expects

How does a cro experiment log differ from a results log?

A results log records what happened; an experiment log records what to do next. The results log is for the archive; the experiment log is for the next test. The call is the part that makes the log useful, because a test without a call is a test that wasted a week.

What call belongs in an experiment summary email?

Ship, iterate, or kill — one of the three, named in the first sentence. The call is the part that earns the log, because the team needs to know what to do next, not what happened. A summary that hedges the call is a summary that wastes the next week.

Why does a test log template need a next test?

Because the next test is the part that keeps the program moving. A log that ends with the call stops the program; a log that ends with the next test keeps it going. The next test is the part that turns a one-off into a program.

How the experiment log template fits your stack

The agent reads the experiment results and the hypothesis, drafts the call and the next test, and ships the summary to the team. It pairs with the experiment hypothesis brief and the weekly marketing report templates.

  • Notion
  • Google Docs
  • Looker
  • Mixpanel
  • Slack

Who uses this experiment log template

CRO teams
Turn tests into a program, not a results archive.
Growth leads
Ship the call, not the chart.
Founders
Know what to do next, not just what happened.

How to run this experiment log template in Metaflow

  1. Pull the hypothesis

    The prediction the test was designed to check.

  2. Draft the result

    The metric, the confidence, the delta.

  3. Name the call

    Ship, iterate, or kill — in the first sentence.

  4. Name the next test

    The test the call makes possible.

What you provide

  • The hypothesis
  • The result
  • The confidence
  • The next test idea

What you get back

  • Experiment summary
  • Call — ship, iterate, kill
  • Next test
  • Log entry

Why use this experiment log template?

  • Leads with the call, not the chart

  • Hypothesis stated as a prediction, not a question

  • Names the next test, not just the result

  • Pairs with the hypothesis brief and weekly report templates

Experiment log template FAQs

What is an experiment log?

A summary of a test with the hypothesis, the result, the call, and the next test — the shape a team can act on. The log leads with the call, not the chart, which is why it keeps the program moving instead of becoming a results archive.

What call belongs in an experiment summary?

Ship, iterate, or kill — one of the three, named in the first sentence. The call is the part that earns the log, because the team needs to know what to do next. A summary that hedges the call wastes the next week.

How is an experiment log different from a results log?

A results log records what happened; an experiment log records what to do next. The results log is for the archive; the experiment log is for the next test. The call is what makes the log useful.

Why does the log need a next test?

Because the next test is what keeps the program moving. A log that ends with the call stops the program; a log that ends with the next test keeps it going. The next test turns a one-off into a program.

Similar email sequence templates

A/B test template

Observation, hypothesis, primary metric, sample size, and the decision rule — all written before the test starts.

Marketing report template

What changed, why it changed, and what to do about it — with noise filtered out before anyone reads it.

Content performance report template for stakeholders

Ship the metrics, the takeaways, and the next moves — the report a stakeholder trusts because it leads with what changed, not with a wall of charts.

All Email sequence template

Twenty-two lifecycle and RevOps workflows — activation flows, nurture tracks, scoring models, pipeline definitions, and weekly reporting.

GTM automation

The product page for this motion.

Key takeaways

  • Lead with the call, not the chart
  • Hypothesis as a prediction, not a question
  • Name the next test, not just the result
Use this templateBook a demo