Getting your RealGreen customer base onto autopay

Moving your RealGreen base onto autopay is the highest-leverage boring project we know. It has no launch date, no creative, and no one will compliment you on it: and it quietly fixes accounts receivable, office workload, and a slice of your churn at the same time. The good news is that adoption responds to a campaign the same way program sales do. This post is that campaign: the math, the incentives, the enrollment mechanics, and the one policy change that matters more than all the marketing combined.

Why is autopay a retention play, not just an AR play?

Everyone understands the AR argument: card-on-file customers do not age into the 60-day bucket, and the collections ladder we described in the AR automation post mostly exists because mailed invoices give people seven chances a season to forget you. The underrated argument is behavioral. A paper invoice is a monthly re-decision: every statement asks the customer, in effect, do you still want this? Autopay removes the question. The customer stops evaluating the relationship six or seven times a year and starts simply having a lawn service, and the fall-off from pure billing fatigue, the customers who were never unhappy but got tired of writing checks, largely disappears. It also ends the awkward version of churn where a customer quietly stops paying and you keep servicing them into a write-off.

What adoption rate is realistic?

Most established RealGreen books we see sit between 25 and 40% card-on-file, mostly from whoever happened to enroll at signup. A deliberate campaign can push a base past 60% over a couple of seasons, and new-customer defaults (below) will carry it from there. You will not reach 100%, and you should not try: a stubborn tail of customers will mail checks until the heat death of the universe, and they are often long-tenured, profitable, and loyal. Take their checks with gratitude, and offer bank draft beside card everywhere the enrollment link appears: it fails less often than plastic, costs less to process, and the older half of your base often prefers it. Note also that prepay customers have already solved this problem for you by paying the season up front: that motion has its own playbook, and your autopay campaign should exclude anyone in it.

What does the enrollment campaign look like?

Trigger: active customer, no card on file, not prepay, not past-due. Action: a three-touch sequence: an email that explains the why in plain terms, a text with a secure one-tap enrollment link, and a statement insert with a QR code for the paper holdouts, each pointing at the same enrollment page. Math: say you have 1,400 active customers and 420 already on autopay. If the sequence converts 18% of the remaining 980, that is 176 enrollments. At roughly $2.10 per mailed invoice in print, postage, and posting labor across a seven-invoice season, that alone is 176 × 7 × $2.10 ≈ $2,590 a season in admin cost, before you count those accounts dropping from 30-plus AR days to near zero, and before the churn effect. Illustrative: plug in your own base and costs. The enrollment page itself matters more than the copy: card and bank-draft options, no account creation, no login, done in under a minute on a phone.

Which incentives work, and which backfire?

• Works: a one-time credit. $10 or $15 off the next application is cheap against the AR days saved, and it gives the fence-sitters a reason to act this week instead of eventually.
• Works: a small convenience frame. No stamps, no late fees, ever: for a lot of customers the pitch is genuinely about convenience, and saying so plainly outperforms clever copy.
• Backfires: a percentage off forever. A recurring discount for autopay permanently reprices your book to save a stamp. The math never recovers.
• Backfires: punishing paper. Surcharges on mailed invoices read as hostile, show up in reviews, and pick a fight with exactly the loyal older segment you least want to annoy.

Should autopay be the default for new customers?

The campaign fixes the past; the sales script fixes the future. At the point of sale, card-on-file should be the standard path, presented the way every subscription on earth presents it: we will set you up on autopay like most of our customers, and you will get a receipt after each visit. Not a question, not a checkbox buried in onboarding: the default. Customers who genuinely want invoices can still ask, and a few will. Sold this way, new-customer adoption commonly runs near 90%, and your base mix transforms in two seasons without another campaign. This is the single highest-impact change in this post, and it costs a sentence.

What breaks after you win?

Autopay converts a willingness-to-pay problem into a card-validity problem. Cards expire, banks reissue after fraud, and every failed charge is a small leak that needs its own retry-and-recovery machinery: that is the declined-card recovery post. For the customers who refuse a card on file but own a smartphone, a texted one-tap pay link on each invoice is the bridge, covered in the pay-by-text post. And all of it depends on payment status flowing between your billing and your messaging, which is what a nightly RealGreen sync is for: nobody should ever get an enrollment nudge for a card they added yesterday. The sync is also why none of this locks you into one vendor: we can automate pretty much anything, and we can connect RealGreen to pretty much any payments or messaging platform with an API, a Zapier connection, or a native connection.

The takeaway: every mailed invoice is a small invitation to reconsider being your customer. Autopay retires the question. Run the campaign once, change the new-customer default forever, and let the tail of check-writers be.

Start before renewal season

1. Pull the split: active customers with and without a card on file, and the AR aging for each group. The gap funds the project.
2. Stand up a one-tap enrollment page: card or bank draft, no login, under a minute on a phone.
3. Run the three-touch campaign to actives with a one-time credit, excluding prepay and past-due accounts.
4. Change the new-customer script so autopay is the default path, and train whoever sells.
5. Recheck the card-on-file percentage monthly, and hand the failed-payment side to a recovery sequence before the leak starts.