A Full-Funnel Acquisition System for a Regional Landscape and Pool Contractor

A high-end landscape and pool project is one of the largest discretionary purchases a homeowner ever makes; the journey runs from “my backyard is boring” to a five-figure signed contract across weeks of research, a site visit, and a design they have to fall in love with. A paid click can start that journey, but at home-services costs it cannot carry the whole of it. The business did not need more clicks. It needed a SYSTEM that captured early interest, qualified it honestly, and put only real projects in front of the sales team.

I designed and built that system: the funnel, the automation, the local search footing, and the measurement underneath all of it.

The Challenge

Four things made this a systems problem, not a campaign problem:

• A long, high-ticket, considered purchase. Design leads to build over months. Content and follow-up had to serve every stage, because almost no one converts on the first visit.
• Local demand, bound to a service area. The real market is a drive-time and service radius, not a national keyword. National search volume is a vanity number for a business that can only serve the homes it can reach.
• Many services, one brand. Design, hardscaping and carpentry, pools and spas, and grounds maintenance are different buyers with different intent, all under one roof. The architecture had to separate them without fragmenting the brand.
• No way to tell a browser from a buyer. Leads and projects were not instrumented or scored, so there was no reliable way to know which inquiry deserved a same-day call and which needed a month of nurture.

The Approach

Define the qualified project first

The discipline was subtraction. Before building anything, the program wrote down what a real project looks like: the budget it clears, the decision-maker it involves, the need it solves, and the timeline it runs on. That single definition, a plain BANT screen (Budget, Authority, Need, Timeline), governed keyword selection, ad targeting, lead scoring, and the questions the sales team asked on the first call. It is far easier to build a machine that converts when you have written down exactly whose problem you are solving.

Model the journey and the pipeline as two linked systems

The buildout separated two things that are easy to conflate:

• The customer’s journey, tracked as a lifecycle: a stranger becomes a subscriber, a lead, a marketing-qualified lead, then a sales-qualified lead. This answers “what is this person’s relationship to the business?”
• The internal pipeline, tracked as deal stages: consultation booked, needs analysis and site visit, concept in progress, concept presented, detailed proposal, contract out, closed. This answers “where is this specific project in our design-to-contract process?”

Mapping them separately, then wiring the handoff between them, is what let marketing and sales share one source of truth instead of two contradictory ones.

Automate the CRM around a single record

Every source, a website form, organic and paid social, a referral, or a paid search click, created one contact in a single CRM and marketing-automation platform. From there the system ran itself:

• An automated welcome sequence on entry, then a nurture track for anyone who did not engage.
• Lead scoring that separated a cold browser from a hot inquiry, with re-engagement attempts and a clean archival path for leads that went quiet.
• A BANT qualification gate before any lead was handed to sales, so the sales team spent its time on projects, not tire-kickers.
• Deal stages, proposal steps, objection handling, and onboarding built as automations, so the administrative work of moving a project forward did not depend on someone remembering to do it.

One record per contact, one place the whole funnel lived. Without that, a funnel lies to you.

Put local search and service-area targeting underneath it

Organic content and the local search profile were built around the specific services and the service-area geography, the way homeowners actually search, by service and by place. Competitor positions were benchmarked to size the real opening in the market rather than guess at it. The point was to earn the high-intent, in-radius searches that a local business can actually win, and to stop paying for national head terms it never could.

Instrument everything, measured to the sale

None of the above matters if you cannot see it, so measurement went in before optimization did:

• Web analytics with server-side tagging and consent handling, so form and lead submissions were tracked as first-class key events, not guessed at.
• Call tracking evaluated and specced, because in home services the phone is often the real conversion and an untracked call is an invisible lead.
• Analytics linked to search data and exported to a durable warehouse, so reporting outlived any one dashboard.

The question the system was built to answer was never “how much traffic.” It was “how many qualified projects, from which channel, at what stage,” measured to the booked consultation and the signed contract rather than the click.

Key Takeaways

1. Define the qualified project before you spend. A written BANT definition of who is worth a same-day call, and who is not, is the highest-leverage document in the whole build; it makes every downstream choice easier.
2. Model the journey and the pipeline separately, then link them. Lifecycle stage answers “who is this?”; deal stage answers “where is the project?” Conflating them is how marketing and sales end up arguing over the same lead.
3. One CRM record per contact, or the funnel lies. A single source of truth is the precondition for scoring, routing, and honest reporting.
4. Instrument to the sale, not the session. Wire the calls and forms, warehouse the data, and measure to the booked consultation; traffic is not a result.
5. A high-consideration local service is won on system, not on any single click. The click is the cheapest, most replaceable part; the machine around it is the moat.

The vertical is specific; the discipline is not. Define the qualified buyer, model the journey and the pipeline, instrument to the outcome, and let one system carry the work. That is exactly how I approach organic and AI search visibility now, at a different scale and in a different market, but on the same principles.