Funnels
Step-by-step conversion with the definition of every step visible on the chart, and a one-click breakdown by any property you send.
Recomputed within 90 seconds of a definition change
Product analytics software
Product numbers your whole team can read without a data analyst in the room
Product analytics a designer, a founder and an engineer can all open on Monday morning and agree on by lunchtime.
Not signed in — ask about anything public, or sign in from the chat to see your own conversations.
The product
What Quillon measures, and how
Five capabilities, each with what it actually does, which plan it is on and how fast it lands. The assistant answers from this list rather than from marketing copy.
Retention
Cohort retention on any event pair, with the unusual option of counting a week as seven days from signup rather than the calendar week.
Daily cohorts overnight; weekly available from the first full week
Session replay
Replay of a session that produced a number you distrust, opened straight from the chart point, with inputs masked by default.
Available about 3 minutes after the session ends; kept 30 days
Warehouse export
A nightly or hourly export of raw events to your own warehouse, with the same schema the product reads so the numbers reconcile.
Hourly export lands within 15 minutes of the hour
Metric definitions
One shared dictionary of what each metric means, in plain words, versioned — so a changed definition shows on every chart that used it.
Immediate; every chart records which version it was drawn with
See it answer
Three things worth asking
Each one opens the assistant with the question already sent — you only wait for the reply.
What counts as a tracked event, and would 6 million a month put us on Team or Scale?
Answered from the published plans and the event definition through list_plans — the same numbers on this page.
Our funnel is dropping sessions between two steps and I don't think the drop is real — can someone look?
Opens the message form as a card in the chat, topic and detail already filled in from the conversation.
Any news on QM-5521?
Asks which email it belongs to, then reads the thread back. Signed in, it goes straight to your own.
The desk
In the inbox right now
Open conversations with their id, state and the next thing that happens. Anyone can look one up with its id and the email it belongs to; signed in, you just see your own.
QM-5521in progress
Funnel loses 40% of sessions between step two and step three and the drop looks wrong
Reproduced: step three is defined on a property the mobile client stops sending after an app upgrade, so the sessions are real but uncounted.
QM-5498resolved
Hourly export arriving about 40 minutes late three days running
A backfill job was holding the export queue; it now runs after the export rather than before.
QM-5534open
Whether a server-side event counts once or twice when it is also sent from the client
Waiting for a person; the short answer is once, if both carry the same event id.
Signed in as the demo customer, the assistant reads these back through my_conversations. Signed out, it asks for a conversation id and the email it belongs to.
Plans
Priced on monthly tracked events, not seats — everyone on your team gets an account on every plan.
Solo
Free to 50,000 events a month
One product, early, before the numbers matter to anyone but you.
- Funnels and metric definitions
- Unlimited team accounts
- 90 days of history
- Community support
Team
$89 a month to 2 million events
A product team that has to agree on a number in a meeting.
- Everything in Solo
- Retention and session replay
- 24 months of history
- Two-hour first reply in working hours
Scale
From $540 a month
Several products, a warehouse, and someone whose job is the data.
- Everything in Team
- Warehouse export, hourly
- Unlimited history
- A named support contact
- Single sign-on
Start a conversation
Write what you need. It lands in the same queue a person watches all day. The assistant can open this same form for you — that is what open_desk_form does.
What is real here, and what is not
Quillon Metrics is a business invented for this page. Read this before you believe anything else on it.
Genuinely running
- The assistant on this page is a live Busymate AI assistant, grounded in this site's own published pages.
- The capability list, the plans and the conversations come from this demo's own MCP server — real tool calls, not pasted text.
- The page registers its own actions over WebMCP, so an agent can highlight a capability or open the message form.
- Signing in as the demo customer is a real identity hand-off: the assistant receives a name and an email address it never asked for.
Seeded, not connected
- There is no Intercom workspace behind this page. Nothing started here becomes an Intercom conversation, or a conversation in any other inbox.
- Quillon Metrics is an invented product. The capabilities, prices, limits, people and threads are fixtures written for this demo.
- Conversations started here live in memory until this demo restarts. Nobody is notified and nothing is assigned.
The Intercom connection is on the roadmap, not in production — this page shows the assistant half of it working against seeded conversations so you can judge the experience before the connector exists.
Put this on your own site
The same first reply, on your own site and your own inbox
The same assistant, the same page actions, the same identified sign-in — on your Intercom setup instead of this one.
- Point the assistant at your documentation so your own words become the first reply, as published content rather than a re-written summary.
- Expose your conversation book as a small MCP server: a lookup by id and email, and a read that only ever answers for the signed-in person.
- Give the message tool an action card so a new thread is captured as a structured record rather than reconstructed from prose.
- Wire the identity hand-off so a signed-in customer is recognised and their own threads answer without them typing an address.
- Register the page's actions over WebMCP so the assistant can act on the documentation the visitor is looking at.
Frequently asked
The assistant answers from these same words — ask it any of them and compare.
What exactly counts as a tracked event?
One call that records something a person did, after deduplication. An event sent from both your client and your server with the same event id counts once. Page views count. Identify calls, property updates and anything Quillon sends itself do not count and never appear on your bill.
Why do two charts of the same thing disagree?
Almost always because they were drawn with different versions of a metric definition. Every chart records the definition version it used, and opening the definition shows what changed and when — which is the whole reason the dictionary is versioned.
Can I get my raw events out?
On Scale, yes: a nightly or hourly export to your own warehouse using the same schema the product reads, so your SQL and the charts reconcile. On Solo and Team you can export a query result as CSV, but not the raw event stream.
How long is data kept?
Ninety days on Solo, twenty-four months on Team, and for as long as you are a customer on Scale. Session replays are kept thirty days on every plan regardless, because they are heavy and because keeping them longer is rarely what anyone actually wants.