30-min call with RobBook a proof-of-concept call
Job 04 · Accounts from acquired integrators

// Security integrators · The fourth job

An acquired integrator's accounts checked against your terms, with every gap listed before they move.

Accounts from acquired integrators, tested as a free AI proof of concept on files from a company you already bought and onboarded. Each draft sets the seller's monitoring and service contracts, central station account list and panel and zone lists against your own contract terms and your central station's takeover requirements, and your reviewer compares the gap list with what your onboarding team actually found.

Book a proof-of-concept call30 minutes with Rob
Accounts from one past deal
20 to 30
Customers contacted by AI
None
Passcodes in the copies
None

// The one job

A seller's account files in. Every account that isn't ready to move, listed.

When you buy an integrator, its accounts arrive as a pile: signed monitoring, service and inspection agreements of every vintage, the seller's billing, the central station's account list, panel and zone records, and site notes. Before an account moves onto your forms, your billing codes and your central station, someone has to confirm a signed contract stands behind it, that the contract lets it be assigned, when it renews, and that the site on the paper is the site being monitored.

In the proof of concept, AI does that matching from copies: it reads each contract, lines it up with the seller's account list and site records, compares its terms with yours, and lists every account missing a signed contract, an assignment clause, a renewal date or matching site data, each with the page it came from. No account is transferred, canceled or re-signed, and no notice goes out.

Seller's account fileAcquired company
Monitoring agreement
Service agreement
Account list
Zone list
AccountSiteContract
Illustration, not a real account file
Matched, compared
and listed
Onboarding gap listDraft
Signed contract
Assignment clause
Renewal date
Site match
AccountGapSource page
Illustration, not your accounts

// Where it gets hard

What an acquired account file has to show

Deal papers already hold a buyer's checklist. An alarm monitoring company filed a 2005 asset purchase agreement with the SEC whose Exhibit A says when a monitoring contract counted. For a retail contract: the system installed at the subscriber's premises, fully operational and download-capable; no termination or express notice of one, oral or written; the original delivered with legible signatures of both sides; the recurring charge clearly shown; nothing restricting transfer of the contract or its central station monitoring, or requiring the subscriber's consent; a first term of at least a year, renewing at least yearly and unexpired; and a clause allowing central station monitoring. Accounts were tested against those terms again 45 days after closing. The draft scores each contract on the criteria your team writes down.

Recurring revenue has a narrow definition, and consent has a fallback. The same agreement kept time and materials, installation, reimbursed phone line charges, government taxes and fees, and false alarm assessments out of recurring monthly revenue. Where a transfer needed someone's consent, it didn't happen at closing: the seller kept seeking consent and, until it came, cooperated in an arrangement giving the buyer the benefit. A 2004 credit agreement the company filed counted none of these as Eligible RMR: wholesale monitoring accounts, stand-alone service agreements, and contracts neither written nor freely assignable. The draft sorts each recurring line into your billing codes and quotes every consent clause it finds.

A state may want a notice. Under Texas Occupations Code section 1702.288 and its rule, 37 Texas Administrative Code 35.6, an alarm systems company that contracts with another company or monitor for regulated services must tell the client within seven days the name, address, phone number and contact person of the company that bought the contract, by mail, with stickers showing the new number, unless the contact details stay the same. California's section 7599.54 wants every alarm agreement, monitoring and service agreements included, in writing, amendments too, with the operator's license number and the services after installation. A missing signed agreement or amendment goes on the list.

Cities register sites, and certificates name an issuer. West Linn, Oregon gives each alarm site with its own address or business name a separate registration, allows 30 days after a takeover to register, and bars moving a registration to another user or site. An ordinance published by the Indian River County, Florida sheriff's office has the alarm company file registration within 15 calendar days after a takeover, naming who took the system over and who monitors it. UL Solutions says only a UL Listed alarm company can issue a UL certificate for a security alarm system, never a monitoring station alone, and insurers and code officials often require one. The draft lists each account's city and any certificate in its file; whether a rule applies is your counsel's call.

What your reviewer will watch: a central station account with no signed contract behind it, a contract with no account, assignment clauses that need consent, renewal dates that don't match the billing, sites whose address or business name differs between contract, account list and zone list, stand-alone service customers mixed in with monitored ones, and certificated accounts. Customer names, addresses, passcodes, call lists and code words are removed or swapped for look-alikes before any copy moves, and the draft never needs the real ones.

// What you send

What the test needs from one finished acquisition

One closed deal
Passcodes removed
01

The seller's account files

Copies of 20 to 30 accounts from a company you bought and have already onboarded: monitoring, service and inspection agreements with their amendments, and the seller's billing for each one.

02

What the central station held

The seller's central station account list and the panel and zone records for the same accounts, with passcodes, call lists and code words taken out or replaced with look-alikes.

03

Your terms and requirements

Your current contract forms, the account criteria your deal team used, your central station's takeover requirements as you received them, and what your onboarding team found on each account.

04

NDA first, names swapped

Customer names, addresses and passcodes are removed or replaced with look-alikes, and only after the NDA is signed does a copy move. If files can't leave your office even then, we build look-alike accounts with your reviewer.

// Before it starts

Settled before any account file moves

Before the first copy moves, the owner decides who reviews the gap lists, which misses fail one, and which details stay out.

Agreed up frontOwner signs off
Reviewer
Named by the owner. Usually whoever ran onboarding for that acquisition.
Success criteria
In writing first, including which missed gaps fail a draft
Price
A range for the live job, set before the test starts
Deal
One acquisition already onboarded, chosen by your reviewer
Removed
Customer names, addresses, passcodes, call lists and code words
NDA
Signed before any account file moves

// How it's judged

Gap lists, compared account by account

Your onboarding beside ours
on the same accounts
Same 20 to 30 accountsWhat your team foundThe proof of concept
Accounts with no signed contractFilled in on your accountsFilled in on your accounts
Assignment clauses needing consentFilled in on your accountsFilled in on your accounts
Terms and renewal dates against billingFilled in on your accountsFilled in on your accounts
Site data across contract, account list and zonesFilled in on your accountsFilled in on your accounts
Recurring lines sorted to your billing codesFilled in on your accountsFilled in on your accounts
Local registrations and certificates flaggedFilled in on your accountsFilled in on your accounts
No results yet. The cells stay empty until drafts exist for accounts from your own past deal.Each row is scored by your reviewer on the criteria set first.

// After a yes

About 30 days on the next acquisition

Once your reviewer says yes, the same check runs for about 30 days on the next company you buy, or on accounts still waiting from the last one.

Your onboarding lead approves every account before it moves, and every customer notice, central station change and re-signed contract stays with your team.

Before you sign, the live job gets a fixed price. Anything after it is priced on its own, and monthly support starts once that job is running.

// Later, one at a time

What could come next

Possibilities, ranked
Each after its own yes
  1. 01

    RMR contracts

    New and renewed agreements read into recurring billing lines and renewal dates once accounts are on your forms.

    Next
  2. 02

    Low voltage estimating

    Bills of material and proposals drafted from bid sets and surveys, for an estimating team that grew with the acquisition.

    Then
  3. 03

    Addenda checks

    Each addendum compared with the bid already priced, for the combined estimating team.

    After that

// One hard limit

It never transfers, cancels or re-signs an account.

The proof of concept never transfers, cancels or re-signs an account, never contacts a customer, a central station or an agency, never touches a panel or a monitoring system, and works only on copies with customer names, addresses and passcodes removed or replaced. It gives no legal advice on whether a contract can be assigned or a notice is due. A person decides every move and sends every notice.

Priced per job. You get a range before the proof of concept and a fixed price before you sign.

The range depends on how many accounts a typical acquisition brings, how many contract forms the sellers used, and how their account lists are kept.

// Questions

Questions about acquired accounts

Will it move accounts to our central station?
No. It lists which accounts are ready to move and what the others are missing. Takeovers, communicator or line changes and every call to the seller's central station stay with your team, and the test never touches a panel or a monitoring system.
Do you need passcodes, call lists or zone descriptions?
Passcodes, call lists and code words, never: they come out of the copies before anything moves. Zone lists help match sites, and any zone description that shows how a building is protected can be replaced with a look-alike your reviewer approves.
Will it tell us whether a contract can be assigned?
No. It quotes the assignment and consent wording from each contract and lists those that need a customer's consent, so your counsel can decide. It gives no legal advice and never asks a customer for anything.
Can we run it on a company we haven't bought yet?
The proof of concept runs on a deal you've closed and onboarded, because your team's results are the answer key. After a yes, the live job can run on a target's files once the deal's confidentiality terms allow copies, with a person reviewing every account.
Is this for buying residential alarm accounts?
No. These pages cover commercial and industrial security work, such as offices, warehouses, plants, schools and multi-tenant buildings. Residential alarm account sales are outside this offer.
Rob Eason

Rob Eason, founder

// Book a proof-of-concept call

Bring one acquisition you've already onboarded.

30 minutes with Rob. You'll be asked your company and role, the job you want tested, and roughly how many accounts your last acquisition brought. Hold account files back until the NDA is signed, and strip passcodes first.

  • Co-owned a 60-employee financial services firm and sold his share to his partner.
  • Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
  • 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
  • 4.3/5 from 6 Google reviews of Massmarket AI.
  • Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
  • Takes every proof-of-concept call himself.