Content Playbook

Your team already ran the experiments. Then it forgot the results.

Your team already ran the experiments. Then it forgot the results.

Your team already ran the experiments. Then it forgot the results.

Content Playbook turns your A/B and content test history into best practices your team can actually use — organized by where they live in the product, backed by tests you’ve already run.

Content Playbook turns your A/B and content test history into best practices your team can actually use — organized by where they live in the product, backed by tests you’ve already run.

Content Playbook turns your A/B and content test history into best practices your team can actually use — organized by where they live in the product, backed by tests you’ve already run.

Content Playbook journey view showing test results mapped to funnel stages

Watch a 3-minute demo

Book a call

How it works

Upload your tracker

However messy. The tool reads your experiment history, isolates the content and copy tests, and ignores layout, pricing, and design tests.

It synthesizes

Conservative by design — it only draws conclusions your data supports, flags contradictions instead of resolving them falsely, and refuses to invent a principle from thin evidence.

You get a playbook

Best practices organized by funnel stage, each backed by the specific tests that earned it. Plus a stakeholder-ready view of how content shapes the user journey.

Where it came from

Where it came from

Content Playbook started as an internal tool at Care.com that turned a year of A/B tests into the content team’s working strategy library, mapped to the enrollment journey. It’s now a repeatable engagement any product team can run on their own data.

Content Playbook started as an internal tool at Care.com that turned a year of A/B tests into the content team’s working strategy library, mapped to the enrollment journey. It’s now a repeatable engagement any product team can run on their own data.

What makes it defensible

It reports what your tests measured — not what it imagines users felt.

It reports what your tests measured — not what it imagines users felt.

It tells you what to stop doing, not just what works. Losses are findings too.

It tells you what to stop doing, not just what works. Losses are findings too.

When the data contradicts itself, it says so. A tool that only produces tidy wins isn’t telling you the truth.

When the data contradicts itself, it says so. A tool that only produces tidy wins isn’t telling you the truth.

How it works as an engagement

How it works as an engagement

This is a done-for-you setup and handoff. I standardize your test tracker, configure the tool on your own infrastructure with your API key, run the first synthesis with your team in the room, and train whoever owns it internally. You refresh it quarterly. No ongoing dependency on me. Your key, your hosting, your playbook.

This is a done-for-you setup and handoff. I standardize your test tracker, configure the tool on your own infrastructure with your API key, run the first synthesis with your team in the room, and train whoever owns it internally. You refresh it quarterly. No ongoing dependency on me. Your key, your hosting, your playbook.

Who it’s for

Who it’s for

Content designers, UX writers, PMs, and growth leads at product-led companies who want to know what their org already learned before designing something new. Works best with teams that have an existing experiment tracker — however messy.

Content designers, UX writers, PMs, and growth leads at product-led companies who want to know what their org already learned before designing something new. Works best with teams that have an existing experiment tracker — however messy.

See what your test history already knows.

See what your test history already knows.

Book a call