Every door on the street. Not just the ones on your list.
Your list knows about eleven houses on a street of forty. ProspectBase starts with all forty, tells you which of them you actually know something about, and records what your team does at each one, door by door.
Four things that go wrong quietly, and what we do about each
Two agents plan a drop on the same 1,452 doors.
Nobody could see it until the flyers were printed. ProspectBase intersects the audiences of the campaigns on screen and names the shared door count before you commit.
A street of forty houses, eleven of them in your data.
The other twenty-nine are doors too. They appear on the round marked as address only, so the walk is complete and the tool is honest about which is which.
You wash a number, then pay to wash it again next week.
A wash belongs to the number, not to the batch it arrived in. Ours holds for thirty days across your whole account, and the quote names the saving before you spend.
"Who owned it in 2019?" "The file says the current owner."
Ownership is recorded as the moments it was observed, each with its own source. We never draw a span between two points as though we knew what happened in between.
Figures are product mechanics, not customer averages. We do not publish uplift percentages we cannot show you the working for.
A list is a snapshot. The door is the record that survives the next one.
Every prospecting tool an agency already owns is organised around a record that somebody bought or typed. The CRM holds the ones you have spoken to. The data file holds who owned the place on the day it was extracted. The map app holds pins you dropped yourself.
None of them hold the street.
ProspectBase turns it around. The address is the durable thing. Owners, files, contact numbers and campaigns are observations attached to it, each one carrying the date it arrived and where it came from. Refresh your data, change your CRM, lose a staff member: the door and its history stay.
Four jobs, one map, one set of numbers
Coverage, worked counts and campaign reach are computed once on the server. The map, the sidebar and the principal's dashboard read the same figure, so two screens can never disagree about how much of a territory has been worked.
Build the territory before you have the data
Seed a suburb and every address in it becomes a door on your map. Draw a zone freehand and every door inside is captured. Knock a house nobody had and add it from the search card in one step.
Every value can answer for itself
Column mappings, owner attribution and Do Not Call state each run on an evidence ladder, and every value records which rung answered it. A number nobody has washed is never shown as clean.
From a shape on the map to a walked street
Campaign the zone you just drew, set the drop date or say it already happened, then hand a named link to whoever is walking it. The office watches the tint fill in as the street is confirmed.
One number, everywhere it appears
Doors, owners, worked percentage and last activity per territory. Recent work shades the map in plain categories rather than a fading colour pretending to encode a date.
Your file covered six of these twenty-two houses
The other sixteen are not missing data. They are doors, and they belong on the round. ProspectBase shows them as address only, so a walker works the whole street and a principal can see exactly how much of the territory is genuinely known.
Filled doors carry an owner. Outlined doors are addresses we hold and you have not met yet. Both are walkable, both record activity, both keep their history.
We are not replacing your CRM. We are holding the ground it never covered.
| Your CRM | A purchased list | Map app + spreadsheet | ProspectBase | |
|---|---|---|---|---|
| Holds every address on the street | no | no | no | yes |
| Tells you where a value came from | partly | no | no | yes |
| History survives a data refresh | partly | no | no | yes |
| Records a letterbox drop door by door | no | no | no | yes |
| Treats Do Not Call as a channel, not a delete | partly | no | no | yes |
| Holds the relationship and the deal | yes | no | no | not its job |
Comparison is about product shape, not vendor quality. Your CRM is a system of record for people you already know. ProspectBase is a system of record for the ground you are working, and it exports to whatever you use.
Hand a casual a link. Do not hand them your database.
Mint a named link for one campaign. No login, no app store, no account. The walker gets the streets in walking order, ticks a whole street off in one tap, gives a reason for the odd skip, and can report what they saw at a door.
The field routes are built as an isolated part of the system that is structurally incapable of reading owner data, and an automated check proves it on every build. Links are stored as digests only. Regenerate one and every live session on the old link dies at that instant, while the walker keeps their name and everything they already confirmed.
What the walker saw comes back with them
Renovation underway, tenants moving out, a for sale board on the neighbour, a dog that means knock next door first. The walker files an observation at the door and it lands on that property's timeline under their name, through the same write path everything else uses.
It is not a separate notebook that somebody has to type up on Monday. By the time they finish the street, the office already has it.
A skip is a reason, not a blank
No access, no junk mail, dog, looks vacant, mailbox full. Chips, not typing. The reasons feed the campaign's skip split and the missed-doors view, so an unwalked house is a known quantity rather than a gap.
Works with no signal
A street commits as one unit and is held on the phone until it can sync. The chip says which state it is in, in plain words, and finishing a street is never blocked by being offline.
Live, and the same number
A walker's confirmations write through the same activity path as everything else, so the progress bar in the field and the tint on the office map are one figure, not two counts that drift.
You know who walked it
Every confirmation carries the walker's name. Lose a phone, revoke the link, and the record of the work stays intact.
A drop is not a conversation
A flyered home still shows as never contacted, because it is. The tool will not inflate your contact rate on your behalf.
The phone side, wired to the doors
Door work is half the platform. The other half is a call session that starts from the same doors, writes back to the same record, and leaves your CRM smarter than it found it.
Call lists from any set of doors
Turn a suburb, a zone or a hand-picked selection into a call list. Every number shows its Do Not Call state before you dial, and a wash stays valid for 30 days per number.
Observations become the record
What you hear at the door or on the phone is captured against the property with its source and date, and the full history stays visible. Observed points, never invented spans.
Checked against Rex, pushed to Rex
See at a glance which owners already exist in Rex, check one person or a hundred doors, and push a contact with its property and relationship in one action. One push per person, never per record.
Roadmap, in active development
Designed, argued about, and in build now. When one of these ships it moves up the page as something we do, with the date it landed.
Is this a CRM?
Where do the addresses come from?
Is this rep tracking?
Do you sell or reuse our data?
Someone is on the Do Not Call Register. Do I lose the door?
Can I get everything back out?
See it on your own suburb
Bring one file and name one suburb. In the session we will seed the area, match your file against it, and show you the two numbers that matter: how many doors are in your suburb, and how many of them you actually know something about.
- Your file matched live, with the rows that did not match named and explained
- A drawn zone, a planned drop and a walk sheet, end to end
- A straight answer on what we do not do yet, and when we might