A field sales CRM built around the door

The address is the record

In SalesPace, the primary object is the home or business at a specific location. Contact details, notes, pipeline stage, sale value, assigned rep and team, appointments and the full visit history all hang off that address. When anyone opens it — the rep who knocked it last week, a different rep working the street today, or a manager in the web CRM — they see the same complete record.

That sounds obvious until you compare it to how field teams usually operate: a purchased list in a spreadsheet, dispositions in a notes app, appointments in a group chat, and a CRM that only learns about a deal after it closes. SalesPace collapses those into one record that is created at the door and stays current for the life of the address.

Because the record is shared, territory handoffs stop being destructive. A rep leaves, a route gets reassigned, a storm changes priorities — the history stays with the address, and the next person to knock it knows exactly what happened there.

Pipeline stages that match how canvassing converts

Field sales pipelines are not enterprise pipelines. Most doors never become opportunities, a large share of the work is returning to a house at a better time, and the appointment is often the real conversion event rather than the sale. SalesPace ships stages that reflect that: New, Contacted, Go Back, Appointment Set, Appointment Completed, Follow Up, Sold and Lost.

Stages move from either side. A rep changes a stage implicitly by recording a disposition at the door or explicitly from the homeowner sheet. A manager drags a card between columns on the opportunities board in the web CRM. Both write to the same record, and every change is appended to a stage history so you can see how a deal actually progressed rather than just where it ended up.

• Eight canvassing-native stages from first knock to sold or lost
• Stage changes from the phone at the door or from the board on the web
• Full stage history on every contact, with the actor and source recorded
• Stage value and counts summarized per column on the pipeline board

Contacts, search and bulk assignment

The contacts screen in the web CRM is a dense table built for volume: search across name, address, phone and email, filter by stage, rep or team, and page through large result sets without loading everything at once. Selecting rows enables bulk reassignment, which is how most real territory changes happen — a manager moves two hundred addresses from one rep to another in one action.

Clicking a row opens a contact overlay in place, so a manager reviewing a queue does not lose their filters and scroll position to check one detail. From there, the full contact workspace is one click away.

The contact workspace

Opening a contact gives managers a three-panel view. On the left is identity: name, phone, email, address, assigned rep and team, current stage and sale value, all editable. In the center is the activity timeline — every visit with its disposition and note, every stage change, every appointment created or moved. On the right are the working modules: schedule or reschedule appointments, log a note, change assignment, change stage.

Notes are append-only. A note recorded at the door in March is still there in September, attributed to the rep who wrote it, rather than being overwritten by whoever edited the record last. For teams that re-knock the same neighborhoods season after season, that history is the most valuable data in the system.

Appointments the whole team can see

Appointments in SalesPace are records attached to contacts, not entries in a separate calendar that has to be reconciled. A rep sets an appointment at the door; it immediately appears in their follow-ups queue, on the manager's appointments screen in the web CRM, and on the contact's timeline.

Managers can review a date range, reschedule, and cancel appointments from the web. Reps can reschedule or complete their own. The result is one appointment book for the field operation rather than one per rep.

Built on real permissions, not hidden buttons

A field sales CRM holds homeowner contact information, so access control has to be enforced where the data lives. SalesPace uses row-level security in the database, scoped by organization, team and role, with four roles: Rep, Manager, Admin and Super Admin. Hiding a screen in the interface is not what protects the data; the database rejecting the query is.

That model extends to administration. Invitations, role changes, team membership and deactivation run through trusted server paths with the permission rules in one place, including protection against removing the last active Super Admin. Bulk export is limited to authorized leadership.

One data layer for phone and web

The iPhone app and the web CRM are two interfaces over the same records. There is no nightly sync between a field tool and a back-office CRM, and no reconciliation step where someone types yesterday's knocks into a spreadsheet. A disposition recorded at 2:14 p.m. on a doorstep is visible in the manager's pipeline at 2:14 p.m.

When you do need data elsewhere, SalesPace connects outward rather than duplicating inward: two-way sync with HubSpot and HighLevel, plus outbound webhooks for custom systems.

Frequently asked questions

Can reps use the CRM without a laptop?

Yes. Everything a rep needs — homeowner records, notes, appointments, follow-ups and performance — is in the iPhone app. The web CRM exists for managers and admins who are running pipeline, territories and the team.

What happens to records when a rep leaves?

Deactivating a user removes their access immediately but keeps the history they created. Their contacts can be bulk reassigned to another rep or team without losing any notes, visits or appointments.

Can we import our existing homeowner lists?

Yes. SalesPace imports address lists by CSV with column mapping, so a purchased list or serviceability export becomes workable territory without manual re-entry.

Does the CRM work offline?

Field actions are captured on the device and synced when connectivity returns, so reps can keep working in areas with poor service.