Speed & experience
Weekly Growth review · ISO week undefined · undefined undefined · undefined · Generated undefined
The third clearing dimension: not just whether a requirement sells, but how fast it gathers buyers toward the North Star of three. Speed is the customer experience — one quote after a fortnight, and they'd have been quicker calling the networks themselves.
Speed to three quotes — the customer's clearing experience
This week. The North Star is three purchases per requirement — three providers competing, a genuine comparison — arriving fast. We are nowhere near it. Half of requirements never get a single purchase; of those that do, almost all stop at one — a one-provider 'comparison' is a poor experience — and only ~3% ever reach three, after eleven days. So what: a customer who gets one quote slowly, or two in two weeks, would have been quicker calling the networks directly — the platform has to beat that or it has no reason to exist. The histogram shows most first purchases landing fast — within two days — while second and third purchases are rare and skew to the slower windows; and ~half of requirements never reach even the first. The trend line shows all three getting slowly faster — first purchase 3.2 → 2.1 days, third ~13 → 11 — but that's speed, not reach: the second and third stay far above the first, so we're serving the few who get there a little quicker, not getting materially more requirements to three. Three, fast, for everyone is the whole game. · AI stub
Catalog Error: Table with name market_clearing_milestone_speed does not exist!
Did you mean "information_schema.referential_constraints"?
LINE 3: from demo.market_clearing_milestone_speed order by speed_order...
^Catalog Error: Table with name market_clearing_speed_trend does not exist!
Did you mean "information_schema.referential_constraints"?
LINE 3: from demo.market_clearing_speed_trend order by week_start, miles...
^Catalog Error: Table with name market_clearing_quote_milestones does not exist!
Did you mean "information_schema.referential_constraints"?
LINE 3: from demo.market_clearing_quote_milestones order by milestone_or...
^