From ~$8K to ~$60K a month
from email.
Burge Pest Control has been in the same family for four generations. It already knew email could generate revenue. What it did not have was a lifecycle system that understood the difference between a new inquiry, an open estimate, a first-time customer, a recurring customer, a failed payment, a cancellation signal, a seasonal add-on opportunity, and someone who had quietly gone dormant.
Decades of service history were already in the database. Nothing was reading it.
Machina rebuilt the channel around those customer states. Instead of asking, “What campaign should we send this week?” the system asked, “What just happened to this customer, what do they need next, and should automation or a person handle it?”
- Client
- Burge Pest Control — residential and commercial pest control across Alameda County, Contra Costa County, and San Francisco
- Industry
- Home services / pest control · Trades marketing
- Engagement
- Lifecycle strategy, email automation, customer-state modeling, retention, reactivation, attribution
The system
The lifecycle revenue engine
Monthly email-attributed revenue
Inputs
Outputs
The outcome
Revenue moved when the channel stopped behaving like a calendar
Before the rebuild, the company attributed roughly $8,000 per month to email. The channel was useful, but it mostly behaved like conventional marketing: lists, broadcasts, occasional follow-up, and manual intervention when someone remembered to do it.
After the lifecycle system matured, the company reported roughly $60,000 per month in email-attributed revenue. That is a 7.5× increase and approximately $52,000 in additional monthly run rate versus the prior baseline.
The point was not to send more email. It was to make email understand the business.
Six-month ramp, email-attributed revenue
ModeledHow to read the numbers
The approximately $8K/month baseline and ~$60K/month endpoint are the reported engagement outcome. Raw exports, exact customer records, and sequence-level ledgers are not published here. Intermediate monthly values, modeled contribution splits, the customer example, selected operating details, and the value indices are normalized or illustrative supporting material, labeled as such wherever they appear. They exist to explain how the system works — not to imply a precision the published figures do not carry.
The challenge
Revenue was leaking between legitimate customer moments
Pest control is not a single-transaction category. A homeowner can begin with an urgent ant, rodent, termite, or mosquito issue; receive an inspection or estimate; book a one-time treatment; move into a recurring prevention program; add another seasonal service; encounter a billing issue; pause or cancel; and return months later when pest pressure changes.
Every one of those transitions is a communication moment. Before the lifecycle rebuild, too many of them depended on a staff member remembering what to do next.
The first step was not copywriting. It was identifying where customer intent was cooling off and where the business was failing to create the next logical action.
Lifecycle journey and leak points
Modeled recovery opportunity, by leak
ModeledThe modeled opportunity map above is deliberately explanatory rather than forensic. The individual leak values are normalized estimates that reconcile to the scale of the reported endpoint; they are not raw accounting entries. What matters is the pattern: several moderate leaks can compound into a very large channel-level gap.
Before and after
The operational change
The larger transformation was operational. Marketing stopped being a layer that sat beside the customer operation and became a response system connected to it.
- Staff manually remembers follow-ups
- Generic campaigns
- Quotes sit untouched
- One-time jobs end with no expansion
- Billing issues surface late
- Marketing and ops disconnected
- Customer states update automatically
- Event-based sequences run with stop rules
- Owner alerts surface high-value / risky moments
- Recurring enrollment built into service flow
- Payment / cancel recovery runs fast
- Marketing and ops share one lifecycle system
Faster response
More consistency
Fewer missed handoffs
More predictable revenue
The intelligence layer
One state, one next best action
One customer. One primary lifecycle state. One next best action.
Every automation had five things defined before the copy was written:
- 01Triggerwhat happened to start the sequence.
- 02Eligibilitywho should receive it and who should not.
- 03Stop conditionwhat event means the sequence should immediately stop.
- 04Primary CTAthe one action that advances the customer.
- 05Human handoffwhen automation should stop trying to be clever and surface the moment to a person.
Customer lifecycle map
States 01–10
Trigger, stop rule, CTA, and timing controls
Eight lifecycle controls
| State | Trigger | Stop condition | Primary CTA | Typical timing |
|---|---|---|---|---|
| New inquiry | Form or inbound lead | Inspection booked | Schedule | Minutes → 7d |
| Quote pending | Estimate delivered | Job booked or decline | Approve quote | 2h → 7d |
| Booked | Service confirmed | Service complete | Prepare | Pre-visit + day 0 |
| First service | Job completed | Plan enrolled | Join program | Day 1 → 21 |
| Active plan | Service due | Visit complete | Confirm or add-on | Event driven |
| At risk | Payment fail or cancel | Account saved or ended | Update or stay | 0h → 7d |
| Former | Service ended | New booking | Return | Seasonal |
| Dormant | 90+ days inactive | Re-engaged or unsubscribe | Rebook | Quarterly |
- Trigger
- Form or inbound lead
- Stop condition
- Inspection booked
- Primary CTA
- Schedule
- Typical timing
- Minutes → 7d
- Trigger
- Estimate delivered
- Stop condition
- Job booked or decline
- Primary CTA
- Approve quote
- Typical timing
- 2h → 7d
- Trigger
- Service confirmed
- Stop condition
- Service complete
- Primary CTA
- Prepare
- Typical timing
- Pre-visit + day 0
- Trigger
- Job completed
- Stop condition
- Plan enrolled
- Primary CTA
- Join program
- Typical timing
- Day 1 → 21
- Trigger
- Service due
- Stop condition
- Visit complete
- Primary CTA
- Confirm or add-on
- Typical timing
- Event driven
- Trigger
- Payment fail or cancel
- Stop condition
- Account saved or ended
- Primary CTA
- Update or stay
- Typical timing
- 0h → 7d
- Trigger
- Service ended
- Stop condition
- New booking
- Primary CTA
- Return
- Typical timing
- Seasonal
- Trigger
- 90+ days inactive
- Stop condition
- Re-engaged or unsubscribe
- Primary CTA
- Rebook
- Typical timing
- Quarterly
- A high-value estimate
- A failed payment
- Cancellation intent
- Repeated engagement that never converts
The decision engine
Personalization was not cosmetic. It came from operational context: pest type, urgency, service history, current lifecycle state, plan status, engagement, seasonality, and risk.
Decision logic
Signals evaluated
Possible outcomes
One fictional customer makes the state model easier to see
The example below is an illustrative composite. The person, profile details, sequence events, and supporting values are fabricated to demonstrate the customer-state logic; they are not a released client record.
Illustrative composite
Inquiry submitted → plan active
- Urgency
- Medium
- Stage
- Inquiry
- Engagement
- New contact
- Plan status
- Not enrolled
- Next action
- Send inspection confirmation
- Urgency
- Medium
- Stage
- Estimate
- Engagement
- Opened estimate
- Plan status
- Not enrolled
- Next action
- Send plan comparison
- Urgency
- Medium
- Stage
- Estimate
- Engagement
- Viewed 2×, no booking
- Plan status
- Not enrolled
- Next action
- Wait 48h, then follow up
- Urgency
- Medium
- Stage
- Estimate
- Engagement
- Opened follow-up
- Plan status
- Not enrolled
- Next action
- Send booking reminder
- Urgency
- Low
- Stage
- Booked
- Engagement
- Confirmed appointment
- Plan status
- Not enrolled
- Next action
- Send prep instructions
- Urgency
- Low
- Stage
- First service
- Engagement
- Service completed
- Plan status
- One-time
- Next action
- Send recurring plan offer
- Urgency
- Low
- Stage
- First service
- Engagement
- Opened offer
- Plan status
- Offer sent
- Next action
- Wait for response
- Urgency
- Low
- Stage
- Plan active
- Engagement
- Enrolled
- Plan status
- Active
- Next action
- Send seasonal service reminder
The architecture
The eight lifecycle sequences
The final architecture covered the highest-value gaps without creating an endless drip campaign. Each sequence had a purpose, a beginning, and a reason to stop.
| Sequence | Trigger | Cadence | Primary action |
|---|---|---|---|
| S1 New inquiry follow-up | Form, call, or audit lead | 0m · 1d · 3d · 7d | Book inspection |
| S2 Quote & booking recovery | Estimate sent, no booking | 2h · 1d · 3d · 7d | Approve or schedule |
| S3 New-customer onboarding | First job booked | Pre · D0 · D2 | Prepare + build trust |
| S4 One-time → service plan | First service completed | D1 · D7 · D21 | Enroll in recurring |
| S5 Service + review loop | Visit due or completed | Pre · Post · D3 | Retain + review |
| S6 Payment / cancel save | Card issue or cancel event | 0h · D2 · D7 | Recover account |
| S7 Dormant reactivation | 90+ days inactive | Seasonal · quarterly | Return or rebook |
| S8 Seasonal cross-sell | Pest + month + history | Event-driven | Add relevant service |
- Trigger
- Form, call, or audit lead
- Cadence
- 0m · 1d · 3d · 7d
- Primary action
- Book inspection
- Trigger
- Estimate sent, no booking
- Cadence
- 2h · 1d · 3d · 7d
- Primary action
- Approve or schedule
- Trigger
- First job booked
- Cadence
- Pre · D0 · D2
- Primary action
- Prepare + build trust
- Trigger
- First service completed
- Cadence
- D1 · D7 · D21
- Primary action
- Enroll in recurring
- Trigger
- Visit due or completed
- Cadence
- Pre · Post · D3
- Primary action
- Retain + review
- Trigger
- Card issue or cancel event
- Cadence
- 0h · D2 · D7
- Primary action
- Recover account
- Trigger
- 90+ days inactive
- Cadence
- Seasonal · quarterly
- Primary action
- Return or rebook
- Trigger
- Pest + month + history
- Cadence
- Event-driven
- Primary action
- Add relevant service
Sequence 01
New inquiry follow-up
- Trigger
- website inquiry, estimate request, call, or other qualified inbound lead
- Goal
- schedule the inspection or service conversation
- Cadence
- immediate, same day, day 1, day 3, day 7
- Stop rules
- booked, manually closed, or unsubscribed
The first job of the sequence was not to “sell pest control.” It was to acknowledge the problem quickly, set expectations, reduce uncertainty, and make the next step obvious. Higher-value or unusually urgent opportunities generated owner alerts instead of simply receiving more automated touches.
Intake & scoring
Nurture cadence
Sequence 02
Estimate and booking recovery
- Trigger
- inspection or quote completed without a booking
- Goal
- turn a completed evaluation into an approved job
- Cadence
- within hours, then days 1, 3, and 7
- Stop rules
- job booked, quote declined, or unsubscribed
The customer has already done the hard part: they asked for help and allowed the company to diagnose the problem. This sequence focused on decision friction — value, safety, disruption, timing, what happens next, and how easy it is to approve the work.
What drives recovery
- Timing matters
- Value reinforcement
- Friction removal
Sequence 03
New-customer onboarding
- Trigger
- first service booked
- Goal
- reduce uncertainty and create a strong first experience
- Cadence
- booking confirmation, pre-visit, day of service, shortly after
- Stop rules
- service completed and recap delivered
Pest control happens in and around someone's home. The onboarding sequence answered practical questions before they became anxiety: who is arriving, how to prepare, what will happen, what was treated, and what to expect after service.
Before the visit
After the visit
Confidence signals carried through every touch
Sequence 04
One-time service to recurring protection
- Trigger
- first service completed for an eligible one-time customer
- Goal
- turn “problem solved today” into preventive service
- Cadence
- day 1, day 7, day 21
- Stop rules
- plan enrolled, or the window closes
The message was not “buy more.” It was “do you want to keep restarting from zero every time pests return?” The sequence compared one-time remediation with the convenience, prevention, and predictability of an ongoing program.
One-time vs. recurring
| Factor | One-time treatment | Recurring program |
|---|---|---|
| Coverage | The single issue found on this visit | The home, across every visit on the plan |
| Prevention | Not included | Built into every scheduled visit |
| Priority | Standard scheduling | Priority scheduling for plan members |
| Long-term value | Pays again for each new issue | Prevention that compounds across the year |
- One-time treatment
- The single issue found on this visit
- Recurring program
- The home, across every visit on the plan
- One-time treatment
- Not included
- Recurring program
- Built into every scheduled visit
- One-time treatment
- Standard scheduling
- Recurring program
- Priority scheduling for plan members
- One-time treatment
- Pays again for each new issue
- Recurring program
- Prevention that compounds across the year
Strategy
Sequence 05
Service, retention, and review loop
- Trigger
- recurring visit due or recently completed
- Goal
- make the ongoing service visible, reduce skipped visits, reinforce value, and capture feedback
- Cadence
- pre-visit, day of service, recap, check-in, review
- Stop rules
- event driven — the loop runs with the service schedule
Recurring charges feel abstract when the customer cannot see what they are buying. Service communication makes the value concrete: here is when we are coming, here is what we treated, here is what to watch for, and here is the next protection milestone.
Timing
Sequence 06
Payment and cancellation recovery
- Trigger
- payment failure, cancellation intent, or account-risk event
- Goal
- remove simple friction automatically and route sensitive situations to a person
- Cadence
- immediate, then selective follow-up
- Stop rules
- account recovered, saved, or closed
A failed card and an unhappy customer are not the same problem. The system separated them. Transactional friction received a fast path to resolution. Cancellation intent triggered reason capture, save logic, and human escalation when context mattered.
Payment failed
Cancellation requested
- Multiple failed payment attempts
- A high lifetime-value customer
- Negative feedback in the cancellation reason
Principles
Sequence 07
Dormant customer reactivation
- Trigger
- no active service or booking after a defined inactivity window
- Goal
- bring a known customer back when there is a relevant reason to return
- Cadence
- seasonal or quarterly
- Stop rules
- re-engaged, rebooked, or unsubscribed
The sequence avoided empty “we miss you” language. It used prior relationship context and current pest pressure: what changed, what usually appears next, and what is the easiest route back to service.
Relevance signals
Sequence 08
Seasonal education and cross-sell
- Trigger
- relevant pest pressure + service history + eligibility
- Goal
- surface an adjacent service only when it makes sense
- Cadence
- event-driven, not fixed
- Stop rules
- add-on booked, or the season passes
A past ant customer does not need every mosquito, rodent, termite, wildlife, and weather message. The system narrowed the offer using service history, timing, and local relevance.
- History matches the trigger
- Timing lines up with the season
- Geography puts the pest in range
The stack
The systems had to agree on customer state
Lifecycle automation fails when marketing knows one thing, payments know another, and operations know something else. The customer should not receive an estimate reminder after booking, a promotional message while a payment problem is unresolved, or a renewal nudge after cancellation.
System capabilities
Automation handles repetition; people handle judgment
The system was intentionally not designed to eliminate human involvement. It was designed to reserve human attention for moments where judgment actually creates value.
Automation handles
People handle
Implementation
Build order: start closest to revenue
We did not treat the project as one giant automation launch. We sequenced the work by revenue proximity: the closer a customer was to a decision, the earlier that automation went live.
Run-rate
ModeledWe documented the prior email revenue baseline, customer fields, consent rules, service-plan logic, reporting gaps, and the events needed to move someone from one lifecycle state to another.
New inquiries and open estimates were the closest leaks to immediate revenue. These sequences also forced the first important discipline: suppression after conversion.
Once front-end follow-up was stable, onboarding and one-time-to-recurring education extended the system into customer value, not just acquisition.
Pre-visit, post-service, reviews, retention, and add-on moments connected marketing to actual service delivery.
Payment recovery, cancellation save logic, dormant reactivation, and seasonal re-entry completed the retention side of the lifecycle.
We evaluated revenue by lifecycle motion, adjusted timing and suppression, removed redundant touches, and increased the share of messages triggered by customer behavior instead of the marketing calendar.
The messaging
Write for the question in the customer's head
The most important messaging decision happened before the subject line.
A pest-control customer does not experience a CRM funnel. They experience a sequence of questions:
- “What is in my house?” — clarity, urgency, and an inspection path.
- “How disruptive will this be?” — preparation, safety, process, and follow-up.
- “Do I really need recurring service?” — recurrence, prevention, coverage, and convenience.
- “Why am I paying again?” — make the ongoing service visible before the charge feels abstract.
- “Can I just cancel?” — distinguish payment friction, dissatisfaction, timing, budget, and true cancellation intent.
- “I used you before. Why should I come back now?” — service history plus a current, relevant reason.
What the system actually sounds like
The examples below are fabricated sample copy, created for this public case study to demonstrate the message strategy. They are representative of the intent, tone, CTA structure, and objection-handling logic — not screenshots of private client messages.
Estimate recovery
“Your pest protection quote is ready”
- Trigger
- Estimate sent, no booking
- Audience
- Homeowners with unbooked estimates
- Objection
- “I need more information before I decide”
- Goal
- Recover lost estimates
One-time to recurring
“Keep the pests out all year”
- Trigger
- One-time service completed
- Audience
- Customers with one completed service
- Objection
- “I don't need regular service right now”
- Goal
- Convert to recurring
Dormant reactivation
“It's been a while — let's get you back on track”
- Trigger
- Defined inactivity window
- Goal
- Rebook
Payment recovery
“We noticed a payment couldn't go through”
- Trigger
- Failed or declined payment
- Goal
- Retain customer
Seasonality becomes context, not a campaign calendar
Pest pressure changes through the year. That does not mean every contact receives a monthly blast. Seasonality is only one input; the contact still has to be eligible based on history, status, geography, and behavior.
Jan
Rodent pressure, reactivation
Feb
Indoor pests, recurring education
Mar
Ants, seasonal awareness
Apr
Termite swarm, inspection reminder
May
Mosquito ramp-up, add-on
Jun
Outdoor peak, add-on
Jul
Peak mosquito and ticks, check-in
Aug
Late-summer pests, add-on
Sep
Wildlife, rodent transition, education
Oct
Pests move indoors, renewal
Nov
Moisture and rodent pressure, reactivation
Dec
Winter home protection, renewal or service reminder
Methodology
Attribution and methodology
A public case study is only useful if the reader can distinguish what is reported, what is calculated, and what is illustrative.
- Identifying details anonymized
- Timing and dates normalized
- Sequence figures aggregated and normalized
Normalized six-month ramp
Modeled contribution split
Reported engagement outcome
- approximately $8K/month in email-attributed revenue before the lifecycle rebuild
- approximately $60K/month at the mature observed endpoint
Derived arithmetic
- 7.5× monthly revenue multiple
- approximately +$52K/month incremental run rate
- approximately +$624K annualized run rate at the endpoint
Normalized or fabricated explanatory detail
- month-by-month ramp
- sequence-level contribution allocations
- leak-level recovery opportunity values
- implementation timing at the sequence level
- fictional composite customer record
- sample email copy
- relative customer-value index
- supporting operating assumptions
These details exist to explain the mechanism and make the economics coherent. They should not be presented as raw client exports.
Outcomes
A portfolio of lifecycle wins, not one magic email
By the mature endpoint, email was contributing roughly $60,000 per month in attributed revenue, compared with roughly $8,000 per month before the rebuild.
The result was distributed across several customer moments instead of depending on one promotional campaign.
From business leak to revenue motion
| Leak | Automation | Modeled monthly contribution |
|---|---|---|
| Cold leads | Lead nurture + owner alert | $6.0K/mo |
| Open estimates | Quote recovery sequence | $10.8K/mo |
| One-time only | Recurring enrollment sequence | $12.0K/mo |
| Seasonal gaps | Add-on / seasonal trigger sequence | $8.5K/mo |
| Payment or cancel risk | Recovery / save flow | $7.2K/mo |
| Dormant customers | Reactivation program | $6.6K/mo |
- Automation
- Lead nurture + owner alert
- Modeled monthly contribution
- $6.0K/mo
- Automation
- Quote recovery sequence
- Modeled monthly contribution
- $10.8K/mo
- Automation
- Recurring enrollment sequence
- Modeled monthly contribution
- $12.0K/mo
- Automation
- Add-on / seasonal trigger sequence
- Modeled monthly contribution
- $8.5K/mo
- Automation
- Recovery / save flow
- Modeled monthly contribution
- $7.2K/mo
- Automation
- Reactivation program
- Modeled monthly contribution
- $6.6K/mo
The leak-by-leak model intentionally lands near, but not exactly on, the reported +$52K/month delta because the row values are rounded explanatory estimates. The channel endpoint is the anchor; the decomposition is the model.
Annualized economics
At the prior run rate, ~$8K/month equates to roughly $96K annualized. At the mature endpoint, ~$60K/month equates to roughly $720K annualized. The difference is approximately $624K in incremental annualized run rate.
Using the normalized six-month ramp in this case study, the program also represents approximately $185K in modeled incremental email-attributed revenue during the ramp itself above a flat $8K-per-month baseline.
The economics
Why the economics compound after the first service
A lifecycle system creates value because the first transaction is not the last legitimate opportunity to help the customer.
The value index below is illustrative. It does not represent released client LTV. It shows the economic logic: prevention, retention, added services, lower reacquisition cost, and longer relationships make later stages more valuable than the initial inquiry alone.
One lead is a lifecycle of conversion opportunities
The strongest strategic takeaway is simple: one lead is not one conversion opportunity.
A customer can create value at the first booking, after an open estimate, after the first service, at recurring enrollment, during a seasonal need, through retention, after a failed payment, before cancellation, after inactivity, and through referral.
- More revenue per lead
- Stronger customer relationships
- More predictable, profitable business
Scope of work
What Machina built
Customer-state architecture, trigger definitions, stop conditions, eligibility logic, escalation paths, and sequence priorities.
Eight core sequences spanning acquisition, quote recovery, onboarding, recurring-plan conversion, retention, payment risk, reactivation, and seasonal cross-sell.
Copy mapped to pest type, urgency, service history, plan status, seasonality, and the customer’s real question at that moment.
Rules that distinguish routine automation from moments that need sales, service, or account judgment.
Reporting designed to connect lifecycle activity to booked or collected revenue rather than treating opens and clicks as the end metric.
Ongoing review of cadence, suppression, conversion paths, deliverability, message fatigue, seasonal relevance, and handoff quality.
Key learning
The best automation mirrors the business, not the marketing calendar
The biggest lesson was not that pest-control companies should send more email.
It was that a recurring home-service business already contains dozens of legitimate communication moments. The value appears when those moments are connected to customer state:
- a new inquiry should not wait for the next newsletter;
- an open estimate should not receive the same message as a recurring customer;
- a completed one-time service should create a preventive-service conversation;
- a payment problem should stop promotional mail and start recovery;
- a cancellation signal should route to the right recovery or human path;
- a dormant customer should hear from the company when there is a relevant reason to return;
- a seasonal offer should only appear when history, timing, and need make it useful.
Once those rules exist, email stops behaving like a media channel and starts behaving like part of the customer operation.
For Burge Pest Control, that shift took a channel from roughly $8K/month to roughly $60K/month in reported email-attributed revenue.
Frequently asked
How can email generate this much revenue for a pest-control company?
Pest control has more lifecycle opportunities than a typical one-time service. New inquiries, open estimates, first treatments, recurring plans, seasonal pest pressure, service reminders, failed payments, cancellations, add-ons, and dormant customers all create legitimate reasons to communicate. Revenue grows when those moments are automated and attributed separately instead of relying on broad promotions.
Did the company simply send more emails?
No. The architecture was designed around eligibility and stop rules. Customers entered a sequence because something happened and exited when the goal was completed. That can increase useful communication while reducing messages that are no longer relevant.
What made the audience different?
The category combines urgency with recurring economics. A homeowner can need immediate relief today while also caring about safety, preparation, professionalism, recurrence, prevention, scheduling, and long-term peace of mind. Those concerns change across the lifecycle.
Why focus on recurring service?
Recurring service changes the economics of the relationship. The first treatment becomes the start of a service lifecycle instead of the end of a transaction. That makes plan conversion, retention, add-ons, risk recovery, and reactivation economically meaningful.
Are the supporting numbers raw client data?
No. The approximately $8K to ~$60K monthly email-attributed revenue result is the headline engagement outcome. Supporting monthly ramps, sequence allocations, leak-level values, the customer example, the email examples, and the value indices are normalized, derived, or fabricated for explanatory purposes and are labeled accordingly. Raw exports and customer records are not published here.
Why include modeled detail at all?
Because an endpoint without mechanics is not useful. The modeled detail shows how a portfolio of plausible lifecycle improvements can reconcile to the scale of the reported result without publishing private customer exports.
What this means for you
Your database already contains the next sale.
Machina builds lifecycle systems that connect what customers do — inquiry, estimate, booking, service, payment, cancellation, inactivity — to the next useful message and next action automatically.
Results Disclosure: Results described in this case study are specific to this client engagement and are not guaranteed. Individual results will vary based on budget, industry, competitive landscape, market conditions, execution, and other factors. Past performance does not guarantee future results. Machina makes no representation that any client will achieve similar outcomes.