Marketing and follow-up for landscaping companies.
Landscaping companies sell two different things. Recurring maintenance is a subscription decision, and design build is a project decision. When both arrive in the same inbox, one of them always gets handled badly.
Two services. Two different conversations.
The stages below split at the first contact, and most of the lost revenue comes from treating them as one track.
Maintenance inquiry
A property owner wants a recurring service and a price. The decision is quick, and availability and route fit decide it.
A slow reply loses a recurring contract to whoever answered first.
Design build inquiry
A project buyer wants to see finished installs and understand process, budget range, and timeline before committing.
Sending a project buyer a maintenance quote ends the conversation.
The request gets captured
Both tracks write to one system with the property, the service type, and the source attached, then split into their own pipeline.
One shared inbox means the fast track and the slow track both wait.
Someone owns the next step
Maintenance gets a quick reply and a route decision. Design build gets a walk-through and a proposal owner.
Without assigned owners, the bigger project is the one that gets forgotten.
Seasonal follow-up runs
Where it is approved, past customers and open proposals are contacted on a plan instead of whenever someone thinks of it.
Off-season silence turns a customer list into a stranger list.
What Cross X Agency can handle.
Separate service paths
Recurring maintenance and design build organized as distinct entry points, so each buyer reaches a page written for their decision.
Local search
Page structure and headings matched to how each service is searched, plus a current Google Business Profile.
Request capture and routing
Forms that capture the property, service type, and timeline, routed into the correct pipeline with the source attached.
Seasonal follow-up
Approved outreach plans for past customers and open proposals, so contact happens on a schedule rather than by memory.
Status and source reporting
One view across both tracks showing what is open, what closed, and where it came from.
Where the installed lead path fits.
Two service types sharing one inbox is a routing problem, not a marketing problem. Capture, routing, follow-up, and reporting can be installed once as one connected path with two tracks inside it.
Cross X OS is the software underneath it: CRM and pipelines, routing, alerts, automated follow-up, tracking, and reporting.
How the work runs.
We audit how both kinds of request arrive and how each is handled today, then write the scope. Pages, capture, routing, and seasonal plans are built, connected, tested, and launched with documentation.
Accounts, data, and content stay in the company's name.
Before you get in touch.
Can maintenance and design build share one system?
Yes, and they should. One system holds the records and the reporting, with separate pipeline tracks so a quick recurring inquiry and a long project inquiry each get the response they need.
Do you handle seasonal outreach to our customer list?
Where it is scoped and approved. The plan, the timing, and the wording are agreed with the business before anything is sent to existing customers.
Do we need a new website?
Only if the current one cannot carry separate maintenance and project paths or a usable request form. That decision is made in the scope, not assumed.
What do we own after launch?
Everything that matters. The domain, hosting, website, analytics, customer records, and any photography or video produced for the business stay in the company's name, and the setup is documented at handoff so your team can run it.
Stop making both buyers wait.
Tell us how maintenance and project requests arrive today. We will scope the two paths, the routing, and the follow-up that fit each one.