Personas built from behavior at the address.
Prometheus Intelligence Technology assembles the audiences everything else runs on.
Not a persona workshop. Observed signal.
Most persona work produces four laminated archetypes with stock photos that nobody uses again. Ours are assembled from what households actually do: search and answer-layer behavior, serviceability checks, which entry point they arrived through, where they exited the buy flow, how long a preregistration has been waiting, competitor exposure on their street, segment, and post-install adoption.
Those personas then do real work rather than sitting in a deck. They decide which buy-flow variant a visitor enters, which offer leads, how a rescue path is worded, what cadence a preregistration receives while it waits, and where the next tranche of media goes.
Underneath sits the piece most operators are missing: one authoritative address ID enforced across GIS, CRM, ordering, billing and reporting. Not the address string, not the lat/long. Without it every reconciliation is manual and the debt compounds weekly.
Whose definition of a passing are we using?
A passing is an address where plant has been constructed past it and lit. Some operators count the moment fiber is in the ground, which produces a bigger number for the same build. A 200-unit MDU is either 1 passing or 200, and the difference is a signed right-of-entry agreement.
Penetration is active subscribers over RFI addresses. Using planned passings as the denominator, counting sold rather than installed, or reporting cumulative sold-ever all distort it in predictable directions — and all of them flatter.
We publish one defensible view and get the organization planning against it. It is unglamorous and it is usually the highest-value thing we do in the first month, because every downstream plan is calibrated to that number.