A Builder That Does the Sums
Drag a step into place and the conversion rate beneath it redraws before you let go. Funnels are assembled from real events across product, billing and marketing, not from last month’s exports.
See exactly where customers drop off and why. Funnelry joins product, billing and marketing data into one live map of the journey, marks the step where the most people leave, and sends the same numbers to everyone who has to act on them.
Reads from Stripe, HubSpot, Postgres and SegmentGrowth teams use Funnelry to settle the first argument of the week: which step is actually leaking.
Each of these is a different view of the same live data. Scroll sideways, or use the arrows, and read them in order.
Drag a step into place and the conversion rate beneath it redraws before you let go. Funnels are assembled from real events across product, billing and marketing, not from last month’s exports.
Funnelry finds the step where the largest share of people leave and writes down what it sees: who stalled, where, and what they did next. The chart says where. The note says why it deserves your Tuesday.
Set newsletter readers against paid search at the step you care about, or this month’s signups against last month’s. Choose a segment once and it follows you into every funnel you build.
Pick a day, a time and a destination. A digest of the funnel lands in Slack, in an inbox or as a PDF, so the whole team starts the week from one set of numbers.
Stripe, HubSpot, Postgres and Segment authorize with read-only access and share a single customer ID once connected. A sync line on every source tells you when it last spoke.
The route from credentials to a Monday report runs through three milestones, each small enough to finish in one sitting.
Authorize Stripe, HubSpot, Postgres and Segment with read-only keys. Each connector maps its events to a shared customer ID, so a click, a charge and a CRM stage land on one timeline.
Drag steps into sequence on the builder. Conversion rates compute as you place each one, and Funnelry marks the step where the most people leave and says why in a sentence.
Choose a day, a time and a destination. The report goes to Slack, email or PDF on schedule, and the whole team reads the same figures before the week begins.
Past the four one-click connectors, Funnelry hands findings to the tools your team already keeps open all day.
One payment per plan, with no monthly meter running. Begin with Sketch to map a first funnel; move to Atlas when several teams need to read the same numbers.
Plan 01
For one team mapping its first funnels.
$99one-time
Plan 02
For teams comparing segments and sending reports.
$259one-time
Plan 03
For organizations where many people read the same numbers.
$409one-time
All prices in USD. The figure on this page is the figure on your invoice.
| Capability | Sketch | Insight | Atlas |
|---|---|---|---|
| Price, paid once | $99 | $259 | $409 |
| Funnels | 3 | Unlimited | Unlimited |
| Data history | 30 days | 12 months | Unlimited |
| Drop-off charts | Basic | Full | Full |
| Cohort comparisons | — | Included | Included |
| Scheduled reports | Weekly email | Slack and email | Slack, email and PDF |
| Custom dashboards | — | — | Included |
| SSO and role-based access | — | — | Included |
| Warehouse sync and a dedicated analyst | — | — | Included |
We used to debate whose spreadsheet was right. Now the Monday digest lands in Slack and the conversation starts from one page.
The note on our connect step said in a sentence what we had spent months guessing at: people were stalling on the host and port field. We fixed the form that week and the next report showed the step recovering.
Putting newsletter readers beside paid search at the purchase step took a couple of clicks. I stopped exporting to CSV.
Each plan is a single payment. Pick the one that fits the funnels and readers you have today, connect your data, and let Monday’s digest name the first leak.
See plans