HVAC
Turn a building list into service accounts: a CRM handoff checklist
Turn a building list into service accounts by resolving the property, buyer and scope, assigning a dated next action, and handing dispatch an authorized agreement it can deliver.
Direct answer
Turn a building list into service accounts by deduplicating the properties, separating the service location from the paying organization, verifying who can approve the work, and assigning each qualified opportunity a responsible person and dated next action. In your customer relationship management system, or CRM, keep the original source, verification dates, equipment uncertainty and contact preferences beside the record. Advance it only when the next stage has evidence: a buyer conversation, an authorized survey, a scoped proposal, an executed agreement and a dispatch handoff. An imported address alone is still a prospect.
On this page
What makes a building a service account?What belongs in the CRM handoff record?How do you verify the owner and buying role?How do you import the list without losing history?Which stages should a property pass before it is an active account?Who owns the next action?Sample account recordWhat must the survey confirm before you quote?Worked batch and account economicsDoes the first year cover acquisition and delivery?What does dispatch need after the agreement is signed?Weak notes and common mistakesCRM handoff checklistContact preferences and outreach limitsFinding the next property listSources and verification limitsRelated Anvilfield guidesMethodologyOpen the related tool for the calculation, checklist, or packet.
FieldOS by AnvilfieldOffline-first FieldOS for job photos, proof packets, property memory, calculations, teams, billing, and owner-ready reports.What makes a building a service account?
A building becomes an active service account in this workflow when an authorized customer has accepted a defined scope and your department has accepted responsibility for delivering it. You can create a prospect account earlier for research. Keep its commercial status visible so nobody mistakes a populated database for contracted work.
Separate the physical site, the customer organization, the contacts and the opportunity. One organization can pay for several buildings. One building can contain tenants with separate maintenance responsibilities. One manager can arrange access at several sites while having spending authority at only some of them. Give each relationship its own place in the record.
Microsoft's Field Service documentation distinguishes the service account receiving work from the billing account receiving invoices. That is a useful model even if your software uses different labels. Map those relationships before the first work order reaches dispatch. [1]
For a small shop, linked spreadsheet tabs can hold the same distinctions while the process is being established. Use permanent identifiers and named owners. The test is whether another employee can open the record and determine where to go, what is approved, who pays and what remains unresolved without calling the original salesperson.
Microsoft: Create and manage customer accountsWhat belongs in the CRM handoff record?
Agree on the fields before buying or importing the next batch. The table is an Anvilfield worksheet, not a required export layout from a particular supplier. Your administrator should map each field to the actual CRM and keep the original file as the source record.
Use explicit states such as observed, reported, verified and unknown. A blank approval field must not become yes when someone imports the spreadsheet. Keep the date the evidence describes separate from the date your employee checked it. A property lookup performed today can still describe an older record.
| Field | Minimum handoff fields |
|---|---|
| Site, street address and source row | Batch ID, original row ID, permanent site ID, service address, building or suite, parcel reference and jurisdiction |
| Owner, site manager and party to be billed | Recorded owner, operating company, property manager and proposed billing customer, with separate organization IDs |
| Contact name, role and right to approve work | Name, business role, verified contact route, authority scope, verifier, verification date and supporting note |
| Source file, proof date and review date | Source URL or file reference, source date, retrieval date, original match reason and unresolved conflicts |
| Asset list and agreed service scope | Observed feature, confirmed inventory, asset tags, requested tasks, exclusions and survey status |
| Route, access and service capacity | Territory, travel allowance, supported equipment, access restrictions and available delivery hours |
| Contact choices and rules for further outreach | Channel preference, permission evidence where required, suppression status and date, plus the reason for any hold |
| Sales stage and terms still to be approved | Stage, dated evidence for that stage, proposal version, approval conditions and agreement reference |
| Next task, due date and staff owner | One accountable employee, specific task, due date, local time zone and escalation owner |
| Work order and release to dispatch and billing | Service window, access contact, approved spend, purchase order requirement, invoice recipient and first work order ID |
How do you verify the owner and buying role?
Start with the local property authority to resolve the address and recorded ownership. Harris Central Appraisal District's Property Downloads page provides text files from its property database. It demonstrates a public research route; use the corresponding authority for your territory and retain the jurisdiction and dataset date. No individual owner has been verified by this article. [2]
Check development records when the scope depends on alterations or equipment work. Austin Development Services provides access to permits, site plans, certificates of occupancy and related records through online searches and records requests. An application or permit belongs in the evidence file with its status. It does not establish that the present operator wants maintenance. [3]
Then resolve four roles directly: who owns the property, who operates the equipment, who approves this scope and who pays the invoice. Ask the manager to confirm the equipment or area covered by their authority. Maintenance, replacement and tenant work may need separate approvals. Record the person's answer and any purchasing document that supports it.
A registered agent, tax-mailing contact or front-desk employee is a research contact until the approval path is established. Ask for the correct role without promoting the first available name to decision-maker. An example question is: Who can approve a maintenance agreement for these units, and what purchasing steps must be completed before our first visit?
If records disagree, keep both references and assign the conflict to one employee. Hold the proposal until the proposed customer confirms the contracting entity and responsibility for the assets. Recheck those relationships when management changes or a renewal brings a different signer.
Harris Central Appraisal District: Property DownloadsAustin Development Services: Records and ResearchHow do you import the list without losing history?
Keep an untouched source file and work on a staging copy. Standardize addresses for comparison while preserving the originals. Match against existing customers, open opportunities, lost opportunities and suppressed contacts before creating records. A repeat property should update the evidence trail or create a new scoped opportunity, as appropriate, rather than trigger another salesperson's first-contact sequence.
Match sites using jurisdiction, parcel and building identity together. One parcel can contain several buildings, and a single street address can cover several suites. Review near matches manually. Match organizations separately from sites and contacts separately from both. A common management-company email domain should not collapse its entire portfolio into one service location.
HubSpot's import documentation requires unique identifiers for updating records and explains how identifiers associate records across rows. It also states that blank cells do not clear existing values and that assigning an owner during import does not notify that owner. Those are product-specific behaviors to check in your system before relying on an upload. [4]
Test a small batch containing a new site, an existing customer, a shared billing organization, an unknown contact and a suppressed contact. Confirm relationships, retained history and the actual employee task queue. Keep outreach automation paused for the test. Accept the import only after the receiving employee can see and acknowledge the assigned work.
Reconcile source rows to new, updated, duplicate and rejected rows. Then count unique sites, organizations and opportunities separately; they need not total the same number. Save the mapping, import date and error report. Correct only the failed records using their identifiers instead of blindly importing the whole file again.
HubSpot: Format import filesWhich stages should a property pass before it is an active account?
Use stages with evidence-based exit conditions. Use the labels below to track the operating process. Record the event date and responsible employee whenever a stage changes. A call attempt, an email open and an imported phone number do not establish buying authority or a requested proposal.
Keep survey authorization separate from agreement authorization. The first may allow a scoping visit only. A proposal can remain conditional on a purchase order, vendor approval or access arrangement; retain those conditions until they are resolved.
| Stage | Evidence needed to advance |
|---|---|
| Imported prospect | Source retained, duplicates reviewed and site identity resolved |
| Fit checked | Territory, likely service class and capacity fit reviewed; uncertainties assigned |
| Buyer verified | Contact confirms responsibility and approval path for this site's proposed scope |
| Survey authorized | Purpose, access, fee if any, visit limits and responsible host agreed |
| Proposal requested | Survey or adequate records establish scope; buyer requests a priced offer |
| Agreement executed | Required parties accept the final scope and commercial terms; conditions tracked |
| Active service account | Dispatch and billing accept the complete packet; first authorized work order scheduled |
| Hold, lost or suppressed | Reason and responsible employee recorded; permitted review date for holds, no automatic outreach to suppressed contacts |
Who owns the next action?
Give every open record one accountable employee, even when research, estimating and dispatch each have tasks. The researcher owns source conflicts. Service sales owns the buyer conversation. The estimator owns the survey findings and proposal. Dispatch owns the accepted service schedule. Name the person receiving the next handoff and require acknowledgment.
For a starter operating rule, review new assignments by the next business day and unresolved handoffs twice a week. These are proposed shop targets. Set the actual deadlines against staffing, buyer requests and promised proposal dates. An overdue task should reach the service manager with a reason, not silently roll forward another week.
Write the next task as an observable result: confirm whether the manager controls all six units by Thursday, or reconcile the purchase order against proposal revision two before scheduling. Follow up is too vague. If the buyer asks to revisit at renewal, record that requested date and remove the account from the immediate proposal queue.
Keep attempted contact, actual conversation and buyer-requested follow-up separate. Give unanswered prospects a defined review point under your contact policy. More attempts do not repair a wrong owner, unsupported scope or a route the department cannot serve.
Sample account record
This typical account record shows a buyer-verified prospect ready for a scoping visit. Production records need the actual source links, service address and contact details behind these placeholders.
Notice that the equipment count is still provisional and the billing organization is still awaiting purchasing confirmation. Those gaps belong in the record that the estimator receives. They should survive the handoff until someone resolves them.
| Field | Typical entry |
|---|---|
| Service site, source row and batch ID | AF40-EXAMPLE; original row 027; SITE-027; example warehouse building A |
| Owner, site manager and party to be billed | OWNER-011: Example Property LLC; MANAGER-004: Example Management; billing entity pending |
| Source file, record date and review date | List row and local property-record reference; retrieved 2026-11-05; image capture date unknown |
| Reason this site was added to the list | Six apparent rooftop cabinets inside the proposed territory; type and condition unverified |
| Buyer name, role and right to approve work | Facilities manager C-014; 2026-11-05 example call: coordinates maintenance; purchasing approves agreements |
| Work the buyer has asked you to review | Review the current maintenance inventory; no replacement recommendation requested |
| Purpose and agreed limits of the site visit | Identification and scoping only; access window and any survey charge still to be agreed |
| How the buyer asked you to reply | Manager requests the survey outline by business email; no broader campaign permission inferred |
| Current stage and staff member who owns the task | Buyer verified; service salesperson Jordan owns the record; no contracted revenue |
| Next action, date, time and time zone | Jordan to confirm purchasing contact and survey terms by 2026-11-06, 3 p.m. Eastern time |
| Missing facts that block release of the site visit | No dispatch until visit authorization and access arrangements are recorded |
What must the survey confirm before you quote?
Translate the list's match reason into a question the field visit can answer. For rooftop equipment, confirm each asset's location, tag, identification and service responsibility. For a roof program, confirm the agreed roof areas and inspection limits. For a parking lot, confirm the surfaces and boundaries included. Do not treat visible features as proof of condition, capacity or buying intent.
The Department of Energy's Advanced RTU Campaign decision tree separates initial equipment inventory, detailed field evaluation and project planning. Its inventory includes manufacturer, model, age, condition and maintenance history. Use that sequence for rooftop units, or RTUs, while treating its historical numerical screening bands as background rather than current service rules. [5]
Agree on the visit's purpose, charge, host and access before sending a technician. Record whether the visit permits identification only or specific testing. Apply the shop's job hazard assessment and equipment procedures to the actual visit. A salesperson's appointment does not authorize opening equipment, performing repairs or expanding the scope.
Build the estimate from verified tasks, intervals, labor, consumables, travel, access and reporting. Identify anything the buyer must provide. Keep repairs and additional testing as separate options when they are outside the proposed maintenance scope. Dispatch should review the hours and appointment restrictions before the proposal promises a delivery schedule.
DOE: Advanced RTU Campaign decision treeWorked batch and account economics
A typical campaign buys 80 property rows, removes eight duplicate rows and rejects twelve other rows outside the territory, leaving 60 unique sites. The case uses 36 verified buyer conversations, twelve completed authorized surveys, eight requested proposals and four signed agreements that dispatch activates. Each agreement covers one site and a separate customer.
Anvilfield research models the typical campaign in US dollars. The case uses $15 per delivered row for research data, including the duplicates, with no refunds or other data charges. Labor rates below include compensation, payroll taxes and employment benefits, but exclude central overhead and vehicles. Survey time includes travel, access and reporting. Vehicle allowances cover fuel and ownership costs without labor.
| Acquisition item | Modeled calculation |
|---|---|
| Property data | 80 rows x $15 = $1,200 |
| Research and import | 20 office hours x $40 = $800 |
| Buyer outreach and follow-up | 18 sales hours x $50 = $900 |
| Survey labor | 12 visits x 2 person-hours x $75 = $1,800 |
| Survey vehicle expense | 12 mobilizations x $30 = $360 |
| Proposal preparation | 8 proposals x 1.5 hours x $50 = $600 |
| Account activation | 4 accounts x 1 office hour x $40 = $160 |
| Total acquisition and activation | $1,200 + $800 + $900 + $1,800 + $360 + $600 + $160 = $5,820 |
Does the first year cover acquisition and delivery?
Each of the four accounts has six verified RTUs and accepts a $4,000 annual maintenance fee for four planned visits. Each visit needs 0.75 person-hour per unit plus 1.5 shared hours for travel, access and reporting. That is six hours per visit and 24 hours annually. One qualified technician can safely perform the agreed tasks without a helper, rented access equipment or paid escort.
At $75 per hour, annual labor is $1,800. Add $70 per unit annually for included materials, or $420; four vehicle allowances at $30, or $120; and two ongoing office hours at $40, or $80. Annual delivery cost is $2,420 per account. The stated tasks fit these modeled allowances; actual equipment instructions and the agreed scope must establish your hours and intervals.
Surveys are free to prospects. There are no commissions, incremental software charges, postage, record-retrieval fees, overtime, tolls, parking, financing costs or subcontractors. Repairs, replacement work and additional testing are excluded from both maintenance scope and projected revenue. All four fees are collected over twelve months, all planned visits are delivered, and there is no bad debt, cancellation, inflation or renewal. Sales tax is excluded from both revenue and costs; income tax and central overhead remain outside the contribution calculation.
Each account contributes $4,000 minus $2,420, or $1,580, before acquisition, central overhead and income tax. Four accounts produce $6,320 on that basis. Subtract the full $5,820 campaign cost, including unsuccessful prospects, and $500 remains. Acquisition and activation cost per account is $1,455; the first-year remainder is $125 per account. That is an operating comparison, not cash available on signing day.
Now only two agreements activate while all earlier campaign work stays the same. Activation falls by $80, so total acquisition cost becomes $5,740. Two accounts contribute $3,160 before acquisition, leaving a $2,580 shortfall before central overhead and income tax. The result depends on completed sales and delivery economics, not the number of rows uploaded.
Keep the denominators attached to reported rates. Four wins from 60 unique in-territory sites is about 6.7%; four wins from eight proposals is 50%. Both describe this campaign batch, but they answer different questions. Track the source batch, unique sites, buyer conversations, proposals, activated agreements and total staff cost together.
What does dispatch need after the agreement is signed?
Hand dispatch the accepted proposal version and agreement, service location, verified asset list, task schedule, access contact and approved hours. Include the billing entity, invoice instructions, required purchase order and any not-to-exceed amount. Record conditions that still block work. A signature on a conditional agreement should not silently release an unconditional service visit.
Have dispatch confirm the first appointment and reserve the remaining planned visits against available capacity. Assign a service manager to accept the packet. Give billing the same account and agreement identifiers so it can match the authorized scope to the invoice without rebuilding the sale from email attachments.
Carry the original prospect ID into the account, agreement and first work order. After the first visit, compare actual access, travel, material and reporting needs with the estimate. Send the differences back to the estimator and campaign owner. If every selected building needs an extra escort hour, the next prospect profile and pricing allowance should change.
Use the completed work order to begin the service history. Findings, work performed, approvals, parts, labor and customer acknowledgment belong against the actual site and assets. Keep collection status separate from technical completion and sales status. An active account still needs delivered visits, accurate invoices and a renewal review.
Weak notes and common mistakes
A weak handoff says: Good building, six units, manager interested, call next week. It leaves the receiver to discover whether six means observed cabinets or verified assets, whether the manager controls the work, and what interested permits the team to do.
A stronger note says: Six cabinets observed; inventory unverified. Facilities manager confirms responsibility for planned maintenance and requests a survey outline. Purchasing approval and roof access are unresolved. Jordan will confirm both by the recorded deadline. No work or agreement fee is authorized. Each sentence changes the next decision.
- Merging sites because their billing names match. Preserve separate service locations and link the paying organization.
- Replacing a technician's verified inventory with a newer list estimate. Preserve both evidence dates and review conflicts.
- Calling a sent proposal a won account. Require the agreed approval and operational release conditions.
- Erasing suppression history during reimport. Keep the contact restriction attached to the matched record.
- Counting only successful surveys in acquisition cost. Charge the batch for the unsuccessful work it also consumed.
CRM handoff checklist
Want this checklist to run itself on every job — with photo proof and a signed record crews can hand the customer? That's FieldOS.
Contact preferences and outreach limits
A verified address or business role does not document permission for every contact channel. Keep the contact source, requested follow-up, preferences and suppression status visible. Configure your process to stop a marketing sequence when the recipient asks it to stop, and preserve enough restriction history to prevent a later import from restarting it.
For US commercial marketing email, 15 USC 7704 requires accurate headers, nondeceptive subject lines, a valid physical postal address, and a working opt-out route. It also requires clear identification as an advertisement or solicitation unless the recipient gave prior affirmative consent. Keep the opt-out route working for at least 30 days after sending and honor covered requests within ten business days. Use immediate suppression as this shop's operating rule. These email provisions do not settle permission for another channel or every jurisdiction's rules. [6]
Limit the handoff to information needed for the business task. Restrict exports and attachments to staff who need them, and use a documented retention process for obsolete research. Keep access credentials out of prospect notes. The account worksheet should help the service team reach the right person and deliver approved work without becoming an uncontrolled file of personal details.
US Government Publishing Office: 15 USC 7704Finding the next property list
After the first batch is reconciled, use its rejected scopes, buyer questions and actual delivery hours to define the next search. PorchRocket's Ground Control commercial page supports building selection by business type and visible property features. Its live page describes property data whose owners have not requested quotes, with CSV and Excel delivery for file import. [7]
Take your target profile and field map to the commercial destination below. Ask which source and verification fields accompany the delivery, then add the buyer confirmation and authorized scope in your own workflow. Test the next batch before releasing assignments. That gives the service team a list it can work through with a clear responsibility for every remaining unknown.
Sources and verification limits
Sources reviewed November 4, 2026. Microsoft and HubSpot document their own products; verify field mappings and automation behavior in your configuration. The local public-record pages describe research routes without verifying any particular property or buyer.
The DOE document supplies an inventory and evaluation sequence, not current replacement thresholds. The federal email citation is the Government Publishing Office's 2024 Code edition; the email requirements stated here were also checked against the FTC's live guidance. Workflow deadlines, stages, sample records, costs and conversion outcomes are explicit Anvilfield planning examples.
PorchRocket: Ground Control commercial property listsMethodology
Counts, prices, work rates, schedules and outcomes in typical cases are inputs to the Anvilfield research model. Calculations use the stated scope, formulas, cost inclusions and exclusions. Cited public records and technical documents support their attributed facts. Named case records, dates and outcomes are scenario inputs; cited public records retain their source attribution. Local market counts, account profitability and conversion rates were modeled, without independent measurement.
FAQ
How do you turn a building list into service accounts?
Resolve the site, verify the buyer's authority, confirm the scope and give one employee a dated next action. Progress through an authorized survey, requested proposal and executed agreement, then have dispatch and billing accept the packet. Keep imported properties separate from active contracted accounts.
What is the minimum CRM record for a commercial property lead?
Record the site identifier and address, source and dates, match reason, organization and contact roles, verification status, stage, responsible employee and next action. Add contact restrictions and unresolved scope questions before outreach. The full delivery and billing packet is required before account activation.
Is the property owner always the person who buys maintenance?
No. Confirm who controls the specific equipment or area, who can approve the agreement and which organization receives the invoice. A manager or tenant may have a different responsibility from the recorded owner. Record the approval path instead of inferring it from a public-record name.
Should each building have its own CRM record?
Yes. Give each service location a distinct identity and link it to the customer and billing organization. Keep tenant or asset-group responsibilities separate when the scope requires it. Multiple buildings can share a paying organization while retaining their own access instructions, equipment, and work history.
When should a prospect become an active service account?
Activate it after the authorized agreement and operational handoff are complete, with blocking conditions resolved and the first work order scheduled. A database account can exist earlier as a prospect. Its label must not imply that the customer has signed or that dispatch may begin work.
How much follow-up should the service team perform?
Use the buyer's requested timing and your documented contact policy, with a named owner and review date. This guide recommends reviewing new assignments by the next business day as a shop target. An unanswered attempt does not count as a buyer conversation, and an opt-out stops the marketing sequence.
How do you calculate acquisition cost per service account?
Divide the entire batch's research, outreach, survey, proposal and activation costs by activated accounts. Include failed prospects. The worked example spends $5,820 to activate four accounts, or $1,455 each. Its modeled delivery costs leave only $125 per account in year one before central overhead and income tax.
Does a purchased building list mean the owner requested a quote?
No. Treat a matched building as a property prospect and verify buying responsibility and interest separately. PorchRocket's commercial page explicitly distinguishes its property data from quote requests. Keep the original match reason in the CRM without converting it into claimed consent or a service order.
People also ask
Sources checked
- [1] Microsoft: Create and manage customer accounts Retrieved with curl 2026-11-04 for the 2026-11-05 edition; HTTP 200. Supports the distinction between service and billing accounts. Product behavior is not presented as a universal CRM schema.
- [2] Harris Central Appraisal District: Property Downloads Retrieved with curl 2026-11-04; HTTP 200. Provides a public property-database download route. No individual owner, parcel, purchasing contact or current ownership relationship was verified.
- [3] Austin Development Services: Records and Research Retrieved with curl 2026-11-04; HTTP 200. Supports online searches and requests for permits, site plans, occupancy records and related documents in this jurisdiction.
- [4] HubSpot: Format import files Retrieved with curl 2026-11-04; HTTP 200. Page updated September 11, 2026. Supports identifier and association requirements, blank-cell behavior and the absence of owner-assignment notifications on import.
- [5] DOE: Advanced RTU Campaign decision tree Retrieved with curl 2026-11-04; HTTP 200, application/pdf; text extracted and read. Supports inventory, field evaluation and planning sequence. Historical age, tonnage, incentive and replacement thresholds are not used as current rules.
- [6] US Government Publishing Office: 15 USC 7704 Retrieved with curl 2026-11-04; HTTP 200. Official 2024 Code edition, subsections (a)(1) through (a)(5). The stated email requirements were cross-checked against live FTC guidance through web retrieval; the FTC HTML URL failed curl and is not used as an article link. No penalty amount or channel-wide permission claim is made.
- [7] PorchRocket: Ground Control commercial property lists Full referral URL retrieved live with curl 2026-11-04; HTTP 200. Supports commercial property and visible-feature selection, CSV and Excel file delivery, and the distinction between property data and quote requests. No product price, automatic synchronization, contact inclusion or conversion guarantee is asserted.