Sharper Explanations
Drop-off notes that compare the stalled group with the group that passed, so the sentence names a behaviour as well as a step.
01 / About Funnelry
A Funnel Is a Story.Most Teams Read Three Different Ones.
Funnelry exists to give product, billing and marketing one account of the customer journey: a single live map, the step where people leave marked in plain sight, and the same figures delivered to everyone who has to act on them.
02 / The problem
Three Dashboards, Three Answers
Every growing product ends up with the same quiet disagreement. The product team counts signups from events. Finance counts customers from invoices. Marketing counts leads from the CRM. Each tool is accurate on its own terms, and each produces a different number for the same Monday question: how many people made it through?
The disagreement is rarely dramatic. It simply eats the first half hour of every review, and it hides the thing that matters, which is the single step where the largest share of people stop. A funnel with a leak in it looks like a healthy funnel from three different angles.
One journey, one ID, one number everyone can quote.
Funnelry was built to end that half hour. It joins product, billing and marketing data on a shared customer ID, draws the journey as an ordered set of steps, and marks the step with the steepest drop. Then it writes the finding down in a sentence and delivers it on a schedule, so the argument about whose figure is right never starts.
03 / Principles
Four Convictions Written Into the Product
They are less a mission statement than a list of things we refuse to trade away when a feature gets harder to build.
- 01
Name the Step
A funnel report that lists six steps and shrugs has done half a job. Funnelry always marks the largest drop-off and says who stalled, where, and what they did next.
- 02
One Journey, One ID
Clicks, charges and CRM stages are folded onto a single customer timeline. A number that cannot be traced to a person on that timeline does not appear on a chart.
- 03
Read, Never Write
Every connector asks for read-only access. Funnelry observes your systems; it has no way to change a record in them.
- 04
Reports Over Dashboards
A dashboard waits to be opened. A digest arrives on Monday at 08:00, in the channel where the team already works, with the same figures for everyone.
04 / How it is built and supported
Plain Machinery, Kept Honest
Funnelry reads from Stripe, HubSpot, Postgres and Segment, resolves them to one customer ID, and recomputes step conversion as the data arrives. A sync line on every source states when it last spoke, so a stale number is visible rather than silent.
- Read-only keys on every connector, revocable from the source at any time.
- Documentation for each connector and report, written alongside the feature it describes.
- Support is a single inbox, team@funnelryofficial.com, answered by people who use the product themselves. Atlas customers also get a dedicated analyst.
05 / Where it is going
The Next Four Chapters
Direction rather than promises: the work we are leaning toward, in the order we expect to reach it.
More Hand-Offs
Findings sent straight into the task and documentation tools teams already use, with the funnel step attached.
Longer Memory
Side-by-side views of this quarter’s funnel against the same funnel a year earlier, kept honest about what changed in between.
More Sources
Further read-only connectors for the systems that hold the middle of the journey, added one at a time and documented as they ship.
06 / Begin
Give Your Team One Version of the Truth
Each plan is a single payment. Choose the one that fits the funnels and readers you have today, connect your sources, and let Monday’s digest name the first leak.
See plans