Case study · IronHall Pipeline · Commercial landscaping and grounds maintenance
You already know these people. We turn them back into quote requests.
IronHall Pipeline is the system we built for a commercial landscaping company that wins its work from property managers. It finds the managers who should be giving the company work and contacts them every week, and the owner approves every message. Here is what it does, how it works, the guardrails, and what it has produced.
The problem
The relationships were sitting in the inbox.
Quotes sent, jobs won and lost, lunches, managers who went quiet and were never chased. The most valuable thing the company owned was locked where nobody could use it.
What the company had
- Years of relationships with property managers, spread across two email accounts
- A customer list that was a 33-row spreadsheet
- Quotes that went out and never got chased
- No way to see who was still warm, or who to call first on Monday
What it needed
- To know which managers control which properties, and what was quoted to each
- A ranked list of who to contact, with a reason next to every name
- Outreach every week that reads like the owner, without the owner doing the admin
- A hard rule that nothing goes out until the owner has approved it
What it does
It finds the property managers who should be giving you work.
Then it contacts them every week, in the owner’s voice, with every message approved before it sends. It works the relationships the company already has: people who know them and have already asked them for a price.
How is this different from a marketing agency?
Agencies make strangers call you. This gets the company back in front of people who already know it and have already asked it for a price. Different problem, different economics.
Why unanswered quotes matter
A quote with no reply is an open opportunity, not a lost deal. In the landscaping company where this system runs, those unanswered quotes turned out to be some of the best prospects in the business.
How it works
Live outreach in week three. Then every week after.
About two working days of setup on our side. On the company’s side: an hour with us to build the do-not-contact list, then a weekly review of the batch before it goes out.
Mining and mapping
- A read-only connection to the company’s email, on credentials it issues
- Every conversation with every property manager, going back years, read and structured
- The customer record rebuilt: who manages which properties, last contact, what was quoted, what happened
Ranking and the plan
- Every account scored out of 100: relationship strength, quote recency, price competitiveness, signs they’re unhappy with their provider, portfolio size, reachability
- A ranked list in three priority tiers
- A do-not-contact list: competitors, opt-outs, anyone who must never be contacted
- The landscaping playbook applied: what to say, to whom, in what order
First campaign
- Message templates built from the owner’s own past emails, so it reads like him
- First batch drafted and put in front of the owner
- The owner approves, edits or holds each message
- Sending begins, small
Running
- Weekly batches, always approved by a person
- Replies routed straight to the owner
- Follow-ups sent on schedule
- Monthly report: contacted, replied, meetings, quotes requested
- Every quarter: list refresh, message rewrite, a new segment added
Guardrails
Is this spam? No. Here’s why.
Every message goes to someone with an existing relationship or a documented enquiry. The owner approves each one. Anyone who asks to be left alone is blocked at the system level.
Read-only, on the company’s credentials
The system connects to email read-only, using credentials the company issues. It can be switched off at any time.
Nothing sends without the owner
The system drafts. The owner approves, edits or holds each message. It cannot send on its own.
Blocked means blocked
Competitors, their staff and properties, and anyone who asked not to be contacted are removed before scoring. No score can override it.
It writes like the owner
Templates are modelled on the owner’s own past emails. Each invitation names the properties that manager controls and offers real dates.
Checked after sending
Every sent message is checked afterwards against what the owner approved.
The data stays the company’s
It stays in the company’s accounts, on credentials it can revoke. It isn’t sold, shared or used to train anything.
Results
Live, and running every week.
What the system has produced for the commercial landscaping company it was built for.
- Old relationships reopened and turned into booked meetings
- Quote requests coming back in from accounts that had gone silent
- A customer record showing which properties each manager controls, when they were last contacted, what was quoted and what happened
- A weekly outreach campaign that runs without the owner doing any admin
What the system is made of
- Email mining and relationship extractionIn production
- 100-point opportunity scoringBuilt
- Do-not-contact systemBuilt
- Drafting in the owner’s voiceBuilt
- Approval gate and send verificationBuilt
- Customer record rebuilt in the company’s own workbookBuilt
- Landscaping playbookBuilt
- Multi-channel sendingBuilt and tested
Questions
The questions owners ask first.
Your name is on every message, so we built it to act like it.
Is this spam?
No. Every message goes to someone with an existing relationship or a documented enquiry, the owner approves each one before it sends, and anyone who asks to be left alone is blocked at the system level.
What if the owner doesn’t like what it writes?
The owner edits it. Nothing sends without approval. The first campaign usually takes a few rounds of edits, and the system learns from them.
How much of the owner’s time does it take?
About an hour with us in the first fortnight to build the do-not-contact list, then a weekly review of the batch. That review is not optional: the system needs a person at the gate.
What happens to the data?
It stays the company’s, in its own accounts, on credentials it can revoke. It isn’t sold, shared or used to train anything. When the work ends, we remove our access and delete working copies on request, and confirm it in writing.
Who owns the system?
The company’s data, customer record and results are its own. The underlying system stays IronHall’s, and we keep improving it.
Beyond landscaping
Same engine. Other trades.
The engine doesn’t change between trades. What changes is the playbook, where the target list comes from, the message language and the do-not-contact categories. These trades are the closest fit.
- Commercial landscaping & grounds
- Commercial cleaning & janitorial
- Pressure washing
- HVAC service contracts
- Commercial roofing
- Snow & ice management
- Security & fire inspection
Relationships sitting unused in your inbox?
A short call: how you win work today, where your customer history lives, and whether a system like this would pay in your business. If it wouldn’t, we’ll say so.