Blogs · Operations
Why project sites belong in your field CRM
A project site is not another contact — it is where volume actually moves, and your branch manager needs it beside the dealer.
| Operational intelligence | Field activity turned into structured timelines for HQ |
| Role scope | Each rep sees only their dealers and territory data |
| Offline-first | Orders and visits survive low connectivity on routes |
Building-materials and industrial distributors sell through dealers — and into projects. A high-rise under construction, a villa renovation, a commercial fit-out: each is a place where specifications are discussed, samples are left, and demand is won or lost long before a purchase order hits a dealer's counter. Yet many field CRMs only know "accounts." The site becomes a note on a dealer record, a row in a shared spreadsheet, or a pin in a salesperson's personal map.
That collapse works until project-led selling becomes a real slice of revenue. Then leadership asks which sites are active this quarter, which salesperson last visited the tower on the highway, and why orders from Dealer X spiked — and the answer requires archaeology across chats and memory.
Dealers and project sites solve different problems
A dealer is a trading relationship: credit, outstanding, dispatch rhythm, collections, and repeat counter sales. A project site is a demand location: stage of build, influencers on site, competitive brands specified, and visit cadence driven by construction progress — not by payment terms.
Conflating them creates predictable distortion:
- Visit history mixes contexts. A counter visit and a site walk both log against the dealer, so managers cannot see true project coverage.
- Pipeline lies. A "deal" on the dealer account may actually be one wing of one site among twenty in the territory.
- Reassignment loses site memory. When a salesperson leaves, the new salesperson inherits the dealer but not the site narrative — who met the contractor, what was sampled, what follow-up was promised.
- Orders detach from specification. The order books to the dealer (correct for billing) while the commercial story lived at the site (lost for coaching and forecasting).
Dealers remain essential. Project sites are not a replacement — they are a parallel entity type with its own lifecycle.
A salesperson's Tuesday is not only shops. It is a slab cast on Site A, a meeting with the contractor on Site B, and an evening stock check at Dealer C who supplies both. The CRM should reflect that day — not flatten it into three "dealer visits."
What a first-class project site record looks like
Treating project sites as first-class CRM entities means each site has its own record, status, and timeline — linked to dealers and contacts where relevant, but not swallowed by them. Practically, that includes:
- Identity and location — site name, address or geo, phase (foundation, finishing, etc.), and segment tags your ops team uses.
- Stakeholder map — contractor, architect, influencer roles attached to the site, not only to a generic dealer card.
- Visit workflow — check-in, notes, photos, and follow-ups on the site record, the same discipline as dealer visits.
- Linkage to commercial outcomes — orders and collections may still run through a dealer account, but the site shows which demand they fulfilled.
- Lead path when the site is prospecting — a project site lead can stay in qualification with its own follow-up rhythm before it becomes a tracked active project.
First-class does not mean duplicate data entry on every order. It means the operational story of specification and coverage lives where the work happened — on the site — while finance still books through the dealer network you already trust.
Why desk CRM categories fail here
Pipeline CRMs optimise for company → contact → opportunity. Field distribution optimises for route → visit → outcome. When "opportunity" is forced onto a dealer because that is the only account type, project managers in your HQ lose visibility into site-level conversion: visits per active site, time-to-first order, influencer engagement on location, and sites that went quiet while the dealer relationship still looks healthy on paper.
Spreadsheets patch the gap until they do not. Branch B's project list diverges from Branch A's columns. A site changes contractor mid-build; three salespeople touch it over six months; nobody updates the shared file. Mobile apps that only allow dealer check-in push salespeople to log site work as "other visit" notes — which never roll up to territory analytics.
FieldAXIS ONE includes CRM for dealers and project site leads as distinct record types. A project site lead represents a construction or renovation location where products are specified; it carries its own visit and follow-up workflow while remaining linkable to supplying dealers and contacts. Salespeople on the Android app plan project stops on the Daily route the same way as dealer stops; managers see site activity on the web dashboard without reclassifying every site walk as a shop visit.
A day on the route with sites and dealers separated
Consider a territory where plywood and hardware move through a dealer network but wins are fought on sites. Morning: the salesperson checks in at a project site lead — slab stage, competitor sample on site, photo of pack label attached to the site record. Midday: they visit the dealer who will bill the order, confirm stock and credit, and place the order against the dealer account with the site referenced. Afternoon: another site in the same pin code, first visit — they create or update the site lead, schedule return after the contractor meeting, and leave a note visible to the branch manager.
That evening, the manager reviews coverage: which sites were touched, which dealer accounts moved, and which sites have gone cold despite high potential. None of that requires a separate "project module" bolted on later — it requires the data model to admit that sites are real objects in field operations, not footnotes.
A salesperson covers twelve active sites and forty dealers. One dealer supplies five of those sites. Without site records, visit reports show five dealer touches and zero site touches — leadership underinvests in specification coverage. With site records, the same week shows five site visits and two dealer visits tied to those projects; the branch manager reallocates Friday's plan to cold sites instead of repeating counter calls.
Building materials is the reference industry — not an edge case
Nett area on orders, weight-based lines, and project-led demand are core workflows for many distributors — not exceptions for a custom demo. Software that treats project sites as optional extras signals it was built for desk sales first. Field operations platforms admit that the jobsite is where demand is created; the dealer is where it is fulfilled and collected.
If your team already runs influencer or warranty programmes, site-level truth matters twice: scans and activations tied only to dealers miss the carpenter on the slab. Unified field ops keeps site, dealer, and programme context in one graph — see our piece on visits and loyalty sharing one system when those modules are live for you.
Evaluation questions for your next field CRM
- Can salespeople create and visit project sites without forcing them into a dealer account?
- Does site history survive salesperson reassignment?
- Can orders link to both dealer (billing) and site (demand story)?
- Do managers see site coverage metrics alongside dealer metrics?
- Is the mobile visit flow identical in discipline for sites and dealers?
Weak answers mean your project business will keep living outside the system — and your strategic selling motion will stay invisible until someone exports a spreadsheet.
Project sites are where specification happens. Dealers are where fulfilment and cash happen. Your field CRM should respect both — as equals in the data model, not as notes on a single card.