Runs natively on Claude Cowork & Codex

Repeatable growth motions you can actually explain

Automation can run a hundred plays. Polipo tells you which ones are worth running for your stage and motion — and why the last one worked — so every win compounds into the playbook you hand your team.

Cowork
Weekly GTM status report
/polipo give me a status report
Skill(polipo)
└  Successfully loaded skill
Pulled your GTM signals · benchmarks refreshed
Pulled funnel + outreach metrics
Benchmarks refreshed for seed-stage devtools
Read the active sprint commitment
Compared every gain against its baseline
Active sprint2 days left

5 sales-qualified leads by Friday. 3 in — on track.

Reply rate 15% — top third of the founder-led cold-outbound range for your stage (5–25%, 2026 data).

The positioning refinement's gain has held for 3 weeks → promoted to your playbook.

LinkedIn Ads CTR is slipping — back below your pre-March baseline. Proposed next sprint: re-test the hook that won in April.

GTM dashboard

Live · updated just now

Open
Apply for early access

Working with a small group of committed founders.

The Challenge

You know the growth motion and can handle multiple channels in parallel.

Turning each initiative into a rigorous experiment → validation loop is why you are here.

Playbookmain

Living playbook

The lineage with the experiments stripped away — only what promoted to main.

v1·6 promoted·2 in flight·steady
last promotion · C6 · 2 cycles ago
functionC1C2C3C4C5C6nowstanding approachwon by
salesMetric-led openersales/outbound+4.1% replyMulti-thread enterprisesales/first-enterprise2 enterprise
beat story-led (−1.4%)Leading with the quantified buyer pain beat the narrative opener on reply across two cycles; story-led was cut with the number that killed it.
beat single-thread (stalled)Reaching champion and economic buyer together cleared the late-stage stalls single-threading kept hitting — landing the first two enterprise logos.
marketingICP-led landing pagesmarketing/seo+1.9k organic/mo
derived from sales/outbound · /blog variantPages built on the ICP sales had already proven, not guessed keywords. The /blog variant earned its keep and is the next promote candidate.
communityFirst-3-postscommunity/social→ candidate
in flight — not yet promotedNot on the trunk yet — three posts live, reply data still landing. It needs a reply-rate read to clear the commit gate.
productPLG funnel conversionproduct/plg→ pending
in flight — not yet promotedA signup → activation funnel experiment Polipo just opened — instrumenting where self-serve users stall before first value. No conversion read yet, so it stays off the trunk until the numbers land.
cumulative outcome
6.2→10.3%
reply rate
2
enterprise customers
+1.9k/mo
organic visits

6 plays promoted over 8 cycles · 1 cut and kept out. The trunk is the proof, not the prose.

Why Polipo

Many platforms promise you a spike. Polipo tells you if it holds.

Most growth tooling reports good news: the number went up, the experiment “worked,” on to the next. Polipo measures for lasting impact. Every win gets a baseline and a target, then gets tracked — funnel and pipeline. Three weeks on: did the gain hold, or decay the moment your attention moved?

Health scoreboardtracked weekly · vs committed baseline

Prospect → meeting conversion

baseline 5% · target 10%

9.4%
HELD · 4 WKS

Speed-to-close (mid-market)

down from 28d · target ≤21d

21d
IMPROVED

LinkedIn Ads CTR

prev 2.1%

1.1%

And it doesn't break when you specialize.

One project, many functions

Grow into real functions without fragmenting what you've learned.

Sales, marketing, community, product — each becomes a function branch with its own approach. A marketing play can still derive from what sales already proved, and every win merges back into the one trunk they share.

Lineage· namespaced
mainthe shared playbook · one trunk every lane merges into
community1 lane
community/social running

Newest function. First posts live; standing approach still forming.

sales2 lanes
sales/outbound merged

The origin function. Metric-led opener became the standing approach, merged to the trunk.

sales/first-enterprise merged

Two enterprise customers signed → folded into the playbook.

marketing2 lanes
marketing/seo/blog merged

Derives from sales/outbound — reused the ICP sales proved. The /blog variant earned its own keep.

derives from sales/outbound

promote → marketing/blog

marketing/content pruned

Thin pages, no organic lift → cut, with the reason kept.

product1 lane
product/plg running

Newest function — a signup → activation funnel experiment is live but not conclusive yet; no conversion read, so nothing has merged to the trunk.

function/lane/variant
◇ HEAD✓ merged✕ pruned⤷ derives↑ promote
4 functions · 6 lanes · 3 merged · 1 pruned · 1 trunk

Your stack

Plugged into where go-to-market already happens.

Your CRM, your call recordings, your analytics, your socials — Polipo isn't a replacement but the orchestration layer on top of them, with the rigor your ambition demands. One click to authorize, no vertical lock-in — use the best tool for each job. Composable, not a closed loop: it slots into the stack you've already built.

One click to authorizeOAuth-secured · managed authNo API keys, no glue code
HubSpot
Salesforce
Google Analytics
Gmail
LinkedIn
Stripe
GitHub
Slack
Notion
Calendly
Google Calendar
Intercom
Mailchimp
Zoom
100+ more

…and 100+ more via managed connections.

Early access

Request early access

We onboard the people who own the growth motion in small batches during private beta: founders still running founder-led sales, and the first growth hires brought in to scale it.

If it's a fit, we'll reach out as we open the next batch.