Loading your visibility
Loading your visibility
The other screens help you send a referral. This one is about receiving them: who saw your profile in Denver, CO, who opened it, who acted — and what each stage says about the one before it.
Nobody has searched for you, because this prototype has no other agents using it and logs nothing. The figures are generated from a fixed seed, so they are the same on every reload — they are here to show what the screen would tell you, not to report what happened. Each panel says what its own numbers are derived from.
Last 30 days, the default. Widen it and the later stages have more to say.
Appearances over the last 30 days, against the other 4 Denver–Aurora–Lakewood agents in the roster.
Their profiles opened 6 times on average over the same window.
Both sides of this comparison are sample data. The average is computed from the same generated funnels for the 4 agents the seed roster places in Denver–Aurora–Lakewood — so it is derived from the roster rather than invented, but it is still an average of figures nobody earned. In a real market it would be drawn from hundreds of agents, not 4.
Two settings decide whether anything above can happen at all.
Your profile says you are accepting, so you are eligible for every search — including the ones filtered to agents who are open.
Your stated terms: 25% referral fee, first reply under an hour.
Pausing when you are at capacity is a normal thing to do — it hands the demand to someone who has room, and your profile stays intact.
Neither state is sample data — the listing switch is real state in this browser, and “open to referrals” is read from the sample profile every screen shows for you. What this prototype cannot do is act on either one, because search only queries the 232 fictional agents and you are not among them. Referral terms are edited in the profile wizard, which works on a copy of your profile, so this row keeps reporting the published one.
Each stage explains the one above it. Every stage this window can read sits inside the band the model calls healthy.
Result sets your profile was part of
38 appearances in the last 30 days, against a metro average of 34.
If this stage is low: Few appearances means the market is thin, or the filters searchers use exclude you.
31 dropped off here
Someone clicked through from a card or a pin
18% of the searchers who saw your card opened it — 31 cards were scrolled past.
If this stage is low: Plenty of appearances and few opens points at the card itself — the headline, the rating and the four numbers on it.
4 dropped off here
Marked Yes or Maybe after opening the profile
3 shortlists from 7 opens. Too few opens to read a rate from yet.
If this stage is low: Opens without shortlists means the profile or the pitch is not carrying the decision.
3 dropped off here
Someone actually sent a client
0 referrals from 3 shortlists. Too few shortlists to read a rate from yet.
If this stage is low: Shortlists that never become referrals points at your terms — the fee, the response time, whether you are open.
These four counts are generated from a fixed seed — your profile id and the window — so they never change between reloads, and they are shaped by what your profile actually contains and by how many Denver–Aurora–Lakewood agents are in the sample roster. Nothing here was measured, because nothing is logged yet. The “in band” and “weak stage” verdicts come from thresholds the same model sets for itself; there is no industry benchmark behind them, and a stage says so rather than guessing when its numbers are too small to read.
Ordered by what your profile is missing, and what each gap is worth.
Nothing on your profile is missing
All 24 of the 24 fields the strength meter scores are filled in, and both of your availability switches are on. There is no gap left to close here — what happens next is other agents' judgment, so the useful habit is keeping the pitch current and answering fast.
Six events, and none of them is being logged today. This is the whole reason the figures above are generated rather than counted.
profile_appeared_in_resultsprofile_openedverdict_recordedreferral_sentreferral_acceptedresponse_time_observedBehavioural history cannot be recovered after the fact, so the shape is fixed now rather than after a backend exists — and it is one stream, shared with the ranking design, instead of two that would disagree. None of it includes anything about the client being referred.