// Security integrators · The second job
Recurring billing and renewal dates, read from the signed agreement and checked against what's running.
RMR contracts, tested as a free AI proof of concept on 20 to 30 commercial agreements your team already set up. Each draft lists the recurring lines, the renewal and notice dates and the price changes the agreement allows, and your reviewer compares it with the billing your team built and the notices that went out.
- Past agreements
- 20 to 30
- Notices sent by AI
- None
- System access
- None
// The one job
A signed agreement in. Recurring lines and a renewal calendar out.
A commercial agreement for monitoring, inspection, service or a cloud subscription names the services, the sites, the monthly or annual charge, the term, how it renews and what notice either side owes. Someone in billing reads it, sets up the recurring lines, enters the renewal and rate increase dates, and months or years later has to remember the renewal notice.
In the proof of concept, AI does the reading from copies: it turns each service into a draft recurring line, sets out the term, renewal, notice and price change dates, and compares them with the monitoring center's account list and the license reports you export. Nothing is billed, sent or changed.
and dated
// Where it gets hard
What an RMR file has to get right
Renewal clauses carry their own notice rules. If an agreement falls under New York's General Obligations Law section 5-903, which covers contracts for service, maintenance or repair to real or personal property, its automatic renewal can't be enforced unless the provider sends written notice, in person or by certified mail, 15 to 30 days before the customer's deadline to cancel; renewal periods of a month or less are exempt. Wisconsin's section 134.49 reaches business service contracts. One that renews automatically for more than a month needs the renewal terms disclosed at signing, on a separate signed form or initialed in the contract, and where both the first term and the renewal run past a year, a reminder 15 to 60 days before the deadline, which may go on the first page of a monthly invoice in bold type of at least 12 points. Under both, a missed notice leaves the renewal clause unenforceable. The draft lists each agreement's state, clause and window; whether a law applies is your counsel's call.
Billing lives on the site and the system. In SedonaOffice, for example, cycle invoicing bills the active recurring lines on each customer's Site or System records, and the cycle report is checked before posting, because a wrong line means deleting the cycle, fixing the line and running it again. The Company Rate Change program's Recurring Renewal Dates method picks lines by their Renewal date, Rate Increase date and an optional Override percentage, then moves both dates forward, and an RMR Escalation code can attach a schedule of increases by renewal number. The draft fills those values from the agreement for your billing lead to check against what was keyed.
One customer, many buildings. SedonaOffice's Master Accounts group subaccounts, each with its own sites and systems, and each recurring line is flagged to bill the master or the subaccount; the help pages use a property management company and its tenants as the example. Invoice Groups hold lines billed on another schedule, such as in arrears. Canceling a customer stops all of its lines on the effective date, but one who drops monitoring and keeps service is handled line by line. The draft names the account, group and site for each service, in the agreement's own words.
Cloud terms don't follow the contract. Verkada licenses co-term to one expiration date for the whole organization, a weighted average of the licenses claimed, with each product weighted by its license MSRP, so adding cameras mid-term moves the date for every device. Genetec requires Genetec Advantage, its software maintenance agreement, on new Security Center systems, with coverage of one to five years. Where your agreement promises a cloud or software term, the draft compares it with the license report you export and flags the gap.
What your reviewer will watch: a service billed that the agreement doesn't list, an account at the monitoring center with no billing line, a line still billing after a cancellation, increases the agreement doesn't allow, renewal dates that drift from the signed term, and notice dates for states with renewal rules. Call lists, passcodes and zone details come out of the copies before they move, and the draft never needs them.
// What you send
What the test needs from your billing team
20 to 30 signed agreements
Commercial monitoring, inspection, service and cloud agreements your team already set up, with amendments, renewals and cancellation letters. Include a few that renewed and one whose price changed.
What billing did with them
An export or screenshots of the recurring lines with their renewal and rate increase dates, and copies of the renewal notices that went out.
What is actually running
The account list from your monitoring center and the license reports from your cloud and software vendors, as exports, with call lists and passcodes taken out.
An NDA first, and redaction
Monitoring files describe how a customer's building is protected, so the NDA comes first and your reviewer approves every copy. If agreements can't leave your office, we build look-alikes with you.
// Before it starts
Agreed before any agreement moves
Three things are fixed first: who checks the drafts, what fails one, and which details stay behind.
- Reviewer
- Named by the owner. Usually the billing lead or whoever manages RMR.
- Success criteria
- Written first, including which missed dates or lines fail a draft
- Price
- A range for the live job, given up front
- Agreements
- Chosen by your reviewer, across monitoring, service and cloud
- Kept out
- Call lists, passcodes, zone lists and credentials
- NDA
- Signed before any agreement moves
// How it's judged
Agreements, compared line by line
| Same 20 to 30 agreements | What your team set up | The proof of concept |
|---|---|---|
| Each listed service on a recurring line | Filled in on your agreements | Filled in on your agreements |
| Charge, cycle and billing account | Filled in on your agreements | Filled in on your agreements |
| Term, renewal and notice dates | Filled in on your agreements | Filled in on your agreements |
| Rate increases the agreement allows | Filled in on your agreements | Filled in on your agreements |
| Monitoring accounts and licenses with no billing | Filled in on your agreements | Filled in on your agreements |
| Notices due under state renewal rules | Filled in on your agreements | Filled in on your agreements |
// After a yes
About 30 days on new agreements
After your reviewer's yes, the same job runs for about 30 days on agreements as they are signed, renewed or amended.
Your billing lead approves every recurring line and every notice before anything is keyed or sent, and nothing is canceled or changed without a person.
The live job's fixed price is settled before you sign. Whatever follows gets a price of its own, and monthly support begins when that job goes live.
// Later, one at a time
What could come next
- 01Next
Accounts from acquired integrators
A bought company's agreements, sites and recurring lines mapped onto your forms and billing setup before the accounts move over.
- 02Then
Software support renewal quotes
Renewal quotes for video and access control software support drafted from each site's license report, for your account manager to price.
- 03After that
Low voltage estimating
Bills of material and proposals drafted from bid sets and surveys, if estimating wasn't your first test.
// Across industries
The same job in other industries
// One hard limit
It never touches a live system or a credential.
Nothing in the proof of concept designs a system or chooses where devices go or what they cover, and nothing in it touches a live security system or a credential, or handles a client's site security details beyond the copies your reviewer approves. It logs in to no monitoring center, panel or cloud portal, sends no notice and changes no agreement's terms. How a building is protected stays with a license holder and the client.
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 agreements you bill, how many sites and systems they cover, and whether the monitoring is your own or a third party's.
// Questions
RMR contract questions
We resell monitoring from a third-party central station. Does that change the test?
Will it send renewal notices or apply rate increases?
Can recurring inspection and test agreements be part of the set?
Do you need our call lists or passcodes?
Does it decide whether New York's or Wisconsin's renewal rule applies?

Rob Eason, founder
// Book a proof-of-concept call
Bring a stack of signed agreements.
30 minutes with Rob. You'll be asked your company and role, the job you want tested, and roughly how many commercial agreements you bill each month. Keep agreements and account lists back until the NDA is signed.
- 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.
