Requests, ranked
What callers asked for, grouped and counted, so a rising service shows up as a trend and not a hunch.
Platform/Demand intelligence
What people actually called about
Hear what every caller wanted — including the things you don't sell yet.
Planned
Every call carries a request. Aggregated across hundreds of them, those requests are the clearest demand signal a business has, and most of it evaporates the moment the call ends.
To be plain about it: this part is not built. It is described here in the future tense because that is what it is. If it is the reason you would sign up, wait for the dated line in the changelog.
14 days on Scale, no card. Full export on every tier.
In detail
How it is meant to work
Unmet demand
Services people asked for that you do not offer, or do not offer in that area — the expansion list your calls are already writing.
Shifts over time
Week-on-week movement in what callers want, so seasonality and new competitors surface early.
Down to the call
Every number opens the calls behind it, with the sentence that produced the label.
Every card above describes intent, not a shipped surface. Read them as a design brief we have published early so you can tell us it is wrong.
Limits
What this does not do
The fastest way to lose someone is to let them find the edge on their own. So here it is up front.
- This is not built yet. Calls are read one at a time today; the aggregated demand view, the trend lines and the unmet-demand list are not written, and we are not promising a date.
- It will report what callers said, not what a market wants. People who never picked up the phone are invisible to it, so it is demand your phone already captured — not market research.
- Small numbers will stay small. Four callers asking for the same thing is an anecdote, and we would rather show you the count than dress it up as a trend.
- It will not tell you whether to add a service. It reports what was asked for and how often. Whether that is worth doing is a business judgement we have no view of.
- Any demand example you see on this site is illustrative. We have no customers yet, so none of it is a result.
More of the platform
The other four parts
Every call, not a sample
Call analysis In build
Every call gets a verdict.
ReadCoach from evidence, not memory
Team performance Planned
Find the questions your team couldn't answer.
ReadOne place for all of it
Tracking & revenue In build
Keep track of everything, in one place you can audit.
ReadFor when you don't want a dashboard
API & MCP Planned
Ask your calls what happened.
Read