Market Intelligence
Keeping a CRM clean with building-level records
Give each building a durable identity, link its people and assets, and stop repeated imports from scattering physical facts across accounts.
Direct answer
Keep a customer relationship management (CRM) system clean by giving each physical building a persistent ID and linking its owners, tenants, contacts, assets and opportunities to that record. Preserve address aliases and dated evidence, match new imports to existing IDs, and send ambiguous matches to review. Update the relationship when a person or owner changes; keep the building's service history attached to the building.
On this page
Why should the building outlast the contact?Which facts belong on which record?Does a shared address mean the records are duplicates?The building-level methods behind a clean CRMHow much repeated record maintenance does a building ID remove?Best practice: specify the physical record before ordering dataHow should an import update records without multiplying them?Best practice: keep ownership and buying responsibility separateBenchmarks and field rules for clean building recordsWorked example: a regional commercial HVAC service companyHow do leading teams keep the record current after cleanup?What should survive a merge, split or disputed match?Building-record release checklistMethodologyOpen the related tool for the calculation, checklist, or packet.
Key takeaways
- Shared addresses require relationship checks before account merges; several legitimate businesses can occupy the same building.
- Anvilfield estimates that shared building records remove 750 repeated physical-data rows per 1,000 buildings in the central case.
- Match imports through a retained ID crosswalk, preserve source dates, and test that replaying an accepted batch creates no extra buildings.
Why should the building outlast the contact?
A facilities manager changes employers. A tenant leaves. A portfolio owner sells a property. The roof, loading dock and equipment remain at the service location, along with the useful history your company paid to collect. A clean CRM keeps those physical facts attached to a durable building record while changing the people and organizations linked to it.
The usual trouble starts when every imported company name becomes a new site. A roofing rep records an owner, an HVAC rep records a tenant, and a distributor imports the property manager's mailing address. Each row receives a separate roof description. The next inspection corrects only the row the inspector happens to open, leaving conflicting versions of the same physical scope.
Start by deciding what your company counts. A building record represents a structure. An account represents an organization. A contact represents a person. A service opportunity represents a proposed scope at a location. Those records need relationships, and each relationship needs a reason. A person associated with a portfolio is not automatically authorized to buy every service at every portfolio building.
Keep the original customer and work records available during cleanup. An administrator should be able to trace the old account name to the current building, discover who changed the relationship, and find the supporting evidence. That continuity makes the record useful to sales, dispatch, estimating and the person investigating a disputed invoice.
Which facts belong on which record?
Put a fact where its meaning remains stable when another relationship changes. The building's mapped identity belongs with the building. A manager's employment belongs with the contact and organization. A rooftop unit's serial number belongs with the asset. Approval for a service package belongs with the responsible party and that scope. Avoid copying all of these into a single company notes field.
Use a relationship record or an equivalent supported association to connect organizations and people to buildings. Preserve the role, effective dates, verification date and scope of responsibility. When a manager leaves, end that relationship and add the replacement. Retain the earlier work authorization with the work it governed.
A small system can use linked tables or a controlled site register alongside the CRM. A larger system can use dedicated building and asset objects. Choose a structure your administrators can export and reconcile. The essential requirement is that the building has an identity independent of its current account name, with a dependable crosswalk to the CRM's native record IDs.
Commercial roof asset management and capital planning| Record | Keep here | Change without replacing the building |
|---|---|---|
| Building | Persistent building ID, mapped structure, service addresses and aliases | Address correction or an added entrance |
| Organization | Legal or operating name, portfolio membership and billing references | Ownership, management or tenant organization |
| Person and relationship | Contact details, role, buildings served, responsibility and effective dates | Employment or purchasing authority |
| Asset | Parent building, asset identity, observed features and verified equipment history | Installation, replacement or removal |
| Evidence | Source row, observation date, retrieval date, review date and decision | A later observation or corrected interpretation |
| Opportunity and work | Building, proposed scope, buyer confirmation, authorization and result | Stage, price, approval or completed work |
The building-level methods behind a clean CRM
Building-first prospecting means starting from the building and what is visible on it, then finding the decision maker. Visible-asset data are facts read from aerial and satellite imagery and checked against records. Keep the resulting observation attached to the building and evidence record, with its source date and review status.
Fit-first lists are lists filtered to buildings that fit a company's work. Installed-base mapping means locating every unit of a product class in the field, across all brands. A clean CRM retains the fit reason separately from the asset inventory, because a serviceable building and an identified unit answer different operating questions.
Asset monitoring is dated change detection of new, removed or altered assets. Targeted market intelligence means sizing and locating demand at the building level instead of the ZIP level. These methods depend on stable identities: a changed observation should update a known location and its evidence history, allowing the team to investigate what changed.
How much repeated record maintenance does a building ID remove?
Anvilfield estimates that a 1,000-building cohort following the 2018 EIA establishment mix carries 1,721 business-location relationships in the central case, with a range of 1,393 to 2,082 across establishment-count cases. Preserve those relationships when consolidating physical facts.
Anvilfield estimates that storing physical facts on every business-location row, plus holding rows for unoccupied buildings, produces 1,750 physical-data rows per 1,000 buildings, ranging from 1,422 to 2,111. Anvilfield estimates that a shared building record removes 750 repeated physical-data rows per 1,000 buildings, ranging from 422 to 1,111, while keeping the legitimate business relationships.
Anvilfield estimates a 42.9% reduction in physical-data edit tasks per complete review cycle, ranging from 29.7% to 52.6%, by maintaining the common building facts once. Anvilfield estimates that the flat layout requires 175.0 physical review hours per 1,000 buildings, ranging from 142.2 to 211.1 hours.
Anvilfield estimates that the building-record layout requires 100.0 physical review hours per 1,000 buildings in every case, based on a complete pass through the same structures. Anvilfield estimates the flat layout's compensation budget at $8,076 per review cycle, ranging from $6,563 to $9,742, using the BLS labor-cost input.
Anvilfield estimates that shared building records free 75.0 physical review hours per 1,000 buildings per cycle, ranging from 42.2 to 111.1 hours. Anvilfield estimates the corresponding compensation capacity at $3,461 per cycle, ranging from $1,948 to $5,127, for reassignment to unresolved research and service work.
Anvilfield estimates initial matching and shared-location review labor at 40.8 hours per 1,000 buildings, ranging from 35.3 to 46.8 hours, using the initial identity-pass task boundaries. Anvilfield estimates that initial pass's compensation budget at $1,881, ranging from $1,629 to $2,159, using the same labor-cost input. The methodology below defines the cohort, task times and establishment-count cases.
Methodology: sources, calculations and range definitions| Anvilfield estimate per 1,000 buildings | Low | Central | High |
|---|---|---|---|
| Business-location relationships retained | 1,393 | 1,721 | 2,082 |
| Physical-data rows in the flat layout | 1,422 | 1,750 | 2,111 |
| Repeated physical-data rows avoided | 422 | 750 | 1,111 |
| Reduction in physical-data edit tasks | 29.7% | 42.9% | 52.6% |
| Flat-layout physical review labor per cycle | 142.2 h | 175.0 h | 211.1 h |
| Building-record physical review labor per cycle | 100.0 h | 100.0 h | 100.0 h |
| Flat-layout compensation budget per cycle | $6,563 | $8,076 | $9,742 |
| Physical review labor freed per cycle | 42.2 h | 75.0 h | 111.1 h |
| Compensation capacity freed per cycle | $1,948 | $3,461 | $5,127 |
| Initial matching and shared-location review labor | 35.3 h | 40.8 h | 46.8 h |
| Initial matching and shared-location review budget | $1,629 | $1,881 | $2,159 |
How to cite this estimate: Anvilfield, Keeping a CRM clean with building-level records, 2026, https://anvilfield.com/field-guides/market-intelligence/keeping-a-crm-clean-with-building-level-records/
Best practice: specify the physical record before ordering data
Write the physical inclusion rule before adding company names to a campaign. Define the geography, structure type, serviceable feature and evidence needed to accept a building. Specify the size measure: footprint, total floor area and measured roof area belong in separate fields. Keep the reason for inclusion so the next researcher understands why the location is in the file.
Leading manufacturers, distributors and service companies now measure physical fit directly with building-level data such as PorchRocket's Ground Control, which supplies standard commercial building lists by roof age band, material, size, business type, rooftop HVAC, parking areas, tanks and loading docks. Define how the delivered observations will map to your building and evidence records before the order arrives.
Keep the supplier's row identity as a source reference and maintain your own building crosswalk. Ask how repeated deliveries identify previously supplied locations and how ambiguous structures are represented. If the source lacks a durable building key, your matching process must retain enough evidence to recognize the same structure later.
Match the qualification fields to the actual service. Roof coating needs investigation of assembly and condition; rooftop maintenance needs equipment identity and access; pavement work needs a distress assessment. A new physical observation updates the qualification queue. The estimator's technical assessment remains a separately dated record.
Rooftop unit installation and startupPavement condition assessment and PCIHow should an import update records without multiplying them?
Keep the received file intact in a staging area. Record the source, delivery batch and row reference before normalizing names or addresses. Classify each proposed change as an update to a known record, a genuinely new structure, a relationship change or an unresolved match. Let the unresolved queue remain visible until a reviewer settles it.
Use the system's documented update identifiers. HubSpot's import documentation describes native record IDs and custom properties requiring unique values as ways to identify existing records. Keep the building ID separate from the identifiers used for people and organizations. An email address used to recognize a contact does not identify the roof that contact manages.
Retain a crosswalk between source keys, the building register and native CRM record IDs. Match through that crosswalk before proposing an address-based candidate. A previously accepted supplier row should reach the same building on the next import. A missing or conflicting key should raise an exception instead of creating a fresh physical record automatically.
Define which source controls each field. A recent contact file should not overwrite an inspected roof material, and an empty supplier cell should not erase a verified asset identifier. Preserve an explicit clearing action separately from an omitted value. Record changes to important fields with their earlier value, new evidence and reviewer.
Reconcile the accepted batch before releasing it. Compare proposed and actual creations, updates, associations and exceptions. Replay the accepted batch in a test context and check that it creates no extra buildings. Then inspect whether activities, assets and work history remain attached to the intended records. Clean row counts alone do not prove a safe import.
Building data formats: CSV, GIS layers and CRM importsSales operations for trade companies: the data stack that worksBest practice: keep ownership and buying responsibility separate
Store the recorded property owner, operating organization, property manager and approving buyer as distinct roles. Give each a source and an effective date. A property transfer changes ownership evidence; a service authorization establishes responsibility for a particular scope. The sales team needs both facts without allowing either to overwrite the other.
For custom visible-asset inventories, PorchRocket's Asset Search returns the owner of record with reviewed findings, giving account researchers an ownership reference to connect to the building. Keep the buyer-confirmation task open until someone establishes who approves the proposed work.
Link a portfolio manager to the buildings covered by the verified mandate. Record exceptions for tenant equipment, independently purchased services and properties outside that mandate. When responsibility changes, close the earlier relationship and preserve it with the history. Update future tasks to the current responsible person without moving prior authorizations onto that person's name.
HVAC maintenance agreements: scope, exclusions, and renewalsSelling to property managers and portfolio ownersBenchmarks and field rules for clean building records
These Anvilfield operating rules define the release process and review scope. Record actual handling time and unresolved exceptions, then update the staffing budget against that scope.
Count unique buildings for physical coverage, relationship records for account coverage, and accepted scopes for the sales queue. Keep those denominators visible in reports. An increase in imported tenant rows should not appear as an increase in roofs available for service.
| Field rule | Acceptance check |
|---|---|
| Use 1 persistent building ID per structure. | Link campus structures to a shared site while retaining each structure's history. |
| Keep source lineage on 100% of accepted incoming rows. | Trace each field decision back to the delivered file and source row. |
| Allow 0 blind address-only merges. | Review structure identity and legitimate shared occupancy before combining records. |
| Date 100% of active building-to-organization relationships. | Retain verification and effective dates for ownership and service responsibility. |
| Separate 3 evidence clocks. | Keep observation, retrieval and review dates distinct. |
| Assign 1 accountable owner and 1 next action to each open exception. | Give the reviewer a specific evidence question to resolve. |
| Require 0 extra buildings when replaying an accepted batch. | Test the same identities, values and relationships in a controlled replay. |
| Reserve 6 minutes for each physical-data review in this program. | Time the same task in the pilot before expanding the staffing plan. |
Worked example: a regional commercial HVAC service company
A regional commercial HVAC service company maintains a 1,000-building territory register with the EIA-based establishment mix. Its central file contains 1,721 business-location relationships and 29 unoccupied structures. The office retains those unoccupied locations as building records with an explicit status, ready for later occupancy research.
In the flat layout, the team carries physical fields on 1,750 rows. Roof descriptions, location evidence and shared equipment observations recur across tenant records. The administrator matches those rows to 1,000 building IDs and preserves the business-location associations. That removes 750 repeated physical-data entries while retaining the route to each legitimate occupant.
The initial identity pass and shared-location review take 40.8 hours in Anvilfield's central estimate, with a compensation budget of $1,881. The service manager assigns unresolved campus and tenant responsibility questions to a separate queue. She accepts the crosswalk only after reviewing its associations and checking the batch replay.
A complete physical-data review then takes 100.0 hours instead of 175.0 hours under the same review scope, freeing 75.0 staff hours and $3,461 of compensation capacity per cycle. The manager assigns that capacity to incomplete equipment registers and buyer confirmations. She measures completed corrections before changing the department's staffing plan.
At a shared warehouse, the landlord controls the roof and a tenant controls its rooftop equipment service. The team links both organizations to the building, keeps the asset observations with their evidence dates, and attaches each proposed agreement to the responsible organization. The physical count stays stable when a tenant changes, while the responsibility history remains available to the estimator.
HVAC preventive maintenance: equipment tasks and schedulesHow do leading teams keep the record current after cleanup?
Leading teams assign responsibility for physical evidence alongside responsibility for account relationships. Manufacturers use the asset register to locate installed equipment; distributors use it to understand serviceable demand; service companies use it to qualify scope and organize work. A changed finding needs an accountable reviewer and a defined effect on the record.
For manufacturers and service companies tracking installations beyond a standard property filter, PorchRocket's Asset Search finds and monitors assets visible from above, with each search quoted to its scope. Connect the incoming change evidence to the existing building and asset identities so the reviewer can compare dated observations.
Keep observation, retrieval and review dates separate. A newly downloaded image can depict an older site condition. A reviewer accepting that image today does not make it a current equipment inspection. Let the evidence age travel with the field used in a sales filter, and keep unknown capture dates explicit.
When a field visit contradicts desk research, preserve the earlier observation and add the field evidence. Record what the reviewer changed and whether the correction affects other locations screened under the same rule. A removed rooftop cabinet prompts asset reconciliation; an ownership transfer prompts account research. Neither event alone establishes an open sales opportunity.
What should survive a merge, split or disputed match?
Before merging records, identify where their attachments, activities, work orders, opportunities and suppression instructions will end up. Preserve the source IDs in a redirect or alias crosswalk, record the reason for the decision, and retain a reversible change log. The surviving building should expose the useful history without pretending conflicting observations were identical.
For a split, assign the physical evidence to the structure it actually describes. Keep the original site grouping where it still has operational meaning. Shared parking, campus access and common billing can remain site relationships while separate roofs and equipment remain building or asset records. Ask the field team to settle evidence that cannot be assigned from the desk.
Keep deletion, inactivity and contact suppression as separate states. An inactive buyer relationship still explains a past authorization. A demolished structure still anchors historic work. A suppressed contact should remain excluded from outreach after a later import. Give each state an owner and a clear effect on the selling queue.
Building-record release checklist
Release buildings whose identity and relationships support the next task. Hold an ambiguous structure or disputed buyer relationship for a named reviewer. Keep the source delivery, matching decisions and accepted batch report together so the next administrator can understand the result.
Want this checklist to run itself on every job — with photo proof and a signed record crews can hand the customer? That's FieldOS.
Methodology
Research notes, November 5, 2026. The saved script extracts the establishment bands from EIA's 2018 Commercial Buildings Energy Consumption Survey (CBECS) Table B1, revised September 2022. The bands contain 4,719,000 buildings with a single establishment; 811,000 with 2 to 5; 135,000 with 6 to 10; 63,000 with 11 to 20; 19,000 with more than 20; and 170,000 currently unoccupied. The independently rounded categories sum to 5,917,000 against the published headline of 5,918,000. The script normalizes to the category sum and allocates a 1,000-building cohort by largest remainders: 797, 137, 23, 11, 3 and 29 buildings respectively.
The establishment-count assumptions are 2, 6, 11 and 21 for the low case; 3.5, 8, 15.5 and 30 for the central case; and 5, 10, 20 and 50 for the high case across the shared-occupancy bands. The open-ended band uses an explicit high-case count of 50. Each occupied establishment generates a business-location relationship. The flat layout stores physical fields on each relationship plus a holding row for each unoccupied building; the building layout stores those fields once per structure and preserves the relationships separately. The resulting cohort has 971 occupied buildings and 174 buildings with multiple establishments. These ranges measure within-band workload sensitivity.
Task-time assumptions are 6 minutes per physical-data review, 1 minute per incoming flat row for the initial match pass, and 4 additional minutes for each shared-occupancy building. The BLS December 2025 all-private-industry total compensation rate of $46.15 per hour prices the labor. One cycle means a complete review of physical fields across the cohort. The labor boundary covers those tasks; software, purchased data, contact verification and complex historical migration have separate budgets. The operating targets in the benchmark table are Anvilfield release rules. The script saves unrounded calculations and rounds displayed counts, hours, percentages and budgets consistently.
The acquisition comparison also records the live commercial terms: PorchRocket's Ground Control supplies commercial building lists at $10 to $20 per building within 48 hours. Data acquisition belongs in its own budget alongside the accepted import and maintenance workload.
EIA 2018 Table B1; BLS December 2025 compensation release| Public input | Year or edition | Use in this research |
|---|---|---|
| EIA CBECS Table B1 | 2018 observations; September 2022 revision | Building counts by establishment band; reference-stock cohort mix |
| BLS Employer Costs for Employee Compensation | December 2025; March 2026 release | $46.15 per hour of total private-industry compensation; BLS release retained by the Federal Reserve archive |
| Census County Business Patterns methodology | June 2026 revision | Distinguishes business establishments from companies |
| Census Geocoding Services API documentation | February 2026 update | Coordinates calculated along address ranges |
| SSA GN 02605.900, Postal Addressing Standards | April 2021 revision; accessed November 2026 | Secondary unit designators belong in delivery-address records |
| HubSpot Format import files | September 2026 update | Native record IDs and unique-value properties identify records during imports |
| PorchRocket product pages | Live pages; accessed November 2026 | Standard building filters, commercial terms, custom asset finding, ownership evidence and monitoring |
FAQ
Should every building be a separate company account?
Give each building a persistent physical identity and connect it to the appropriate organizations. Use a dedicated building record or a controlled linked register when the CRM's company object cannot represent that distinction. Keep the organization's commercial history with the organization and the service history with the relevant building.
Can I merge records that have the same street address?
Review the intended structure, suite information and account relationships first. Separate tenants can legitimately share a structure, and separate campus buildings can share a mailing address. Combine repeated physical records only after establishing that they describe the same building, retaining the earlier source references.
Is an email domain a useful building identifier?
Use it to help research the organization. A portfolio can use a shared email domain across many buildings, and a property manager can represent unrelated owners. Match physical locations through the building crosswalk and maintain the domain with the relevant organization.
What happens when the property owner changes?
Retain the building ID and its service history. End the earlier ownership relationship when supported by the evidence, add the new owner with its effective and verification dates, and check whether service responsibility and billing instructions changed. Keep prior authorizations with the work they governed.
How many hours does a shared building record free?
Anvilfield estimates 75.0 physical review hours per 1,000 buildings per complete cycle in the central case, ranging from 42.2 to 111.1 hours. The estimate uses EIA's establishment mix and the task times documented in the methodology. It measures the maintenance of shared physical facts.
Should a new import overwrite blank fields automatically?
Define precedence and clearing behavior before importing. Distinguish an omitted value from an intentional clearing instruction. Keep verified physical facts until a permitted source or reviewer supplies the evidence needed to change them, and preserve the earlier value in the change history.
What is the best test for a repeatable import?
Replay an accepted batch in a controlled test context and reconcile the resulting records. Confirm that known buildings keep their identities, legitimate relationships survive, and the replay creates no extra structures. Inspect activities and attachments as well as the row counts.
Does a cleaned prospect record become a sales opportunity?
A clean record establishes identity and usable evidence. Advance the sales opportunity when the team has confirmed the responsible buyer, service scope, timing and next action for the proposed work. Keep a matching asset, a reachable contact and a buyer-requested proposal as separately recorded outcomes.
People also ask
Sources checked
- EIA CBECS Table B1, establishment bands 2018 observations; revised September 2022. Retrieved with curl November 5, 2026, HTTP 200. Raw building counts supply the cohort allocation in the saved estimate script.
- BLS December 2025 Employer Costs for Employee Compensation, Federal Reserve archive BLS release of March 20, 2026. Retrieved with curl November 5, 2026, HTTP 200. Private-industry total compensation is $46.15 per hour. The Federal Reserve retains the original BLS release.
- Census County Business Patterns methodology Revised June 18, 2026. Retrieved with curl November 5, 2026, HTTP 200. Supports the distinction between establishments and companies.
- Census Geocoding Services API documentation Updated February 2026. Retrieved with curl November 5, 2026, HTTP 200. Coordinates are calculated along an address range.
- Social Security Administration, GN 02605.900: Postal Addressing Standards April 21, 2021 revision. Secondary address unit designators are retained on mail. Opened with curl on November 5, 2026; HTTP 200.
- HubSpot: Format import files Updated September 11, 2026. Retrieved with curl November 5, 2026, HTTP 200. Supports using native record IDs or unique-value properties and retaining associations during imports.
- PorchRocket Ground Control, commercial buildings Live product facts checked November 5, 2026. Standard commercial building filters, $10 to $20 per building and delivery within 48 hours. Price is a data acquisition input, separate from modeled cleanup labor.
- PorchRocket Asset Search Live product facts checked November 5, 2026. Custom finding and monitoring of assets visible from above, reviewed findings with the owner of record, and pricing quoted to scope.