I Killed My Webflow Service. Here's What Happened in 30 Days.

AI can build a website now. So I stopped selling websites and started selling the AI work itself. Four clients signed in three weeks.

I'm an AI automation engineer for home-services and aesthetics marketing agencies now. For years before that, I hunted Webflow leads. Cold outreach, freelance marketplaces, network asks, the full grind. The work kept thinning as AI moved the floor on what buyers would pay for a site. A month ago a Hormozi clip on focus hit at the right moment. The gut feel on AI/automation lined up with what was already showing in the market, and I flipped my positioning that week. This post walks through the call, the cut, the rebuild, and what showed up on the other side.

TL;DR: I'd been hunting Webflow leads for years. The pattern kept thinning as AI moved the floor on what buyers would pay for a site. A month ago a Hormozi clip on focus hit at the right moment, I trusted the gut feel on AI automation, switched my positioning that week, and four signed in three weeks. Three still active. The line that pushed the call: "if we were to define focus as the quality and quantity of things that we say no to."

Why hunting Webflow leads stopped paying

The market moved before I did. The AI website builder space hit $3.24 billion in 2026 and is projected to reach $17.43 billion by 2035 (Precedence Research, 2026). The headline number isn't the point. The point is what that growth means at the buyer level: a small business that used to pay a freelancer for a basic site can now ship something functional from a self-serve AI platform for the price of a streaming subscription.

I felt the shift inside my own pipeline before I read the numbers. Years of Webflow lead hunt. Stretches of three or four calls a month in the good months, then a quiet stretch, then a thinner one. The trend line was down, and most of the inbound wanted a designer up front, not a developer.

I wasn't competing with other developers anymore. Most leads wanted a designer-and-developer in one person, and I'm a developer, not a designer. The slice that did fit a developer's shape kept getting cheaper-looking options from AI site builders and self-serve tools before they ever reached me. That's not a fight you out-craft. It's a fight you stop showing up to.

Pre-pivot pattern across the last few years: three to four discovery calls in the good stretches, mostly price-shoppers. Win rate trending the wrong way every quarter.

What was the Hormozi line that pushed the call?

I was at my desk in the office, working on my Webflow site, hunting Webflow leads that weren't landing. Years of skill behind me. Many sites built. None of it was helping. The clip dropped into the middle of that quiet rethink. Alex Hormozi on Lewis Howes' show, talking about focus as a subtraction problem, not an addition one:

"if we were to define focus as the quality and quantity of things that we say no to. Right? Because the most focused person would do nothing but one thing." (Alex Hormozi on The School of Greatness podcast, 2025)

The reframe that landed for me: focus is not what you do, it's what you refuse to do. My positioning at that point was Webflow developer first, automation second. Two doors everywhere. The site, the freelance profiles, the cold outreach, the discovery calls. Each one splitting the inbound. The years of hunting through the Webflow door had been getting harder, not easier.

I didn't tell anyone before I switched. The same afternoon I started planning the new positioning and the new site. Kill the Webflow lead everywhere it lived. Lead as an AI automation engineer. Trust the gut feel that AI work was where the heat was about to land.

What I cut

The cuts were boring on purpose. Webflow had to go everywhere it was living, not just the site. Site, profiles, outreach scripts, conversation defaults, pricing.

Site first. Webflow positioning got stripped from the new build entirely. No Webflow service page, no Webflow case studies, no Webflow mention in the hero, the about, or the contact form options.

Outbound got the same treatment. I stopped pitching Webflow rebuilds in cold outreach and freelance marketplaces. Mid-week-three I deleted the Webflow-specific saved searches and templates so I couldn't slip back into the habit on a slow morning.

Discovery calls narrowed. Site-only inquiries got declined politely. The hardest pass mid-pivot was a Senior Webflow Developer role someone reached out about. Full-time, good money, the safe play. I'm not looking for a job. I'm looking for client work. Saying no to that one stung in a different way than the rest.

Pricing collapsed to fixed-scope AI and automation tiers. No website line item anywhere. The discipline isn't dramatic, it's repetitive. Every Webflow conversation that tries to start gets routed away. The cut only counts when it sticks with revenue on the other side of the door.

What I rebuilt

The site was the visible piece. The rebuild was bigger than the site. New positioning copy across every freelance profile, new outreach scripts, new pricing tiers, new qualification questions for discovery calls. The site got the heaviest cut and the heaviest rebuild because it's the surface every lead hits sooner or later, so it's where I'll spend the rest of this section.

Stack: Next.js on the App Router for control over routing and rendering, Sanity for content so the blog, projects, and testimonials live in a CMS I edit without a deploy, Vercel for the deploy edge, Tailwind for the visual system, and framer-motion for the touches that matter (custom cursor, scroll-driven sections, an animated workflow demo on the home page that swipes through builds on mobile).

The docs did more work than the stack. DESIGN.md locks the visual system, color, typography, spacing, animation, component patterns. STRATEGY.md locks positioning, pricing, and the offer ladder. VOICE.md holds the copy rules. AGENTS.md and CLAUDE.md set the working rules for any AI agent that touches this repo. The docs are the thing that lets the site evolve without drifting.

The touches were where the personality lives. A custom cursor with per-element labels so hover states feel intentional. The mobile workflow demo on the home page. A contact form that runs every brief through an AI analyzer and writes a structured summary into my inbox before I ever read the raw message.

The docs system is the unlock. Every visual decision, every pricing decision, every copy decision has a paper trail. Future me, and future Claude, can pick up the build without re-litigating old choices.

What happened in the 30 days after?

The numbers shifted fast. Before: years of Webflow hunt, mostly price-shoppers, trending down every quarter. After: four paying clients signed in three weeks. They came in through the channels I already had open. Same surfaces, new positioning. The conversations changed, the closes followed.

Closed: four paying clients in three weeks. One turned out to be a scammer. He paid me $50 for a small trial task, which built the trust. I delivered the work. Then he ghosted on the invoice. I Googled him on a gut feeling once the silence got long. First result was a Reddit thread. Same alias, same trial-then-ghost pattern, different freelancer who got the same move pulled on him a while back.

The lesson was cheap relative to the tuition: 50% up front on every new engagement, contract signed, no exceptions. Half upfront isn't a wall against the buyer. It's a floor under both of you. They protect their downside, you protect yours, and the work happens in between.

Currently active: three paying clients across three different verticals.

• An AI consulting practice in Australia running a Fractional CAIO operation, building internal AI workflows for the consultant's own delivery
• A credit-repair operation in the United States, building GoHighLevel workflows and n8n integrations across their internal ops and sales pipeline
• A 3D and XR studio in Australia, automating the manual ops around their virtual-tour fulfillment

The pattern is the thing. Three different industries. Same shape of work. Manual repetition that needed to be turned into a workflow, with AI doing the parts that need judgment. That shape didn't exist on my offer when I led with Webflow.

Most pivot stories treat AI as the threat. The move that worked here was treating AI as the offer. The thing killing the old service became the new service.

How should you think about your own narrowing?

One honest caveat up front, because it changes everything below. Plenty of Webflow developers are doing fine right now. They've been in the game long enough that the referrals and the network keep the calendar full. Easy mode if you're already inside. I wasn't. I was still knocking on doors when the AI shift hit, which made the door harder to open every month. The pivot worked for me partly because the service category itself was hot and the field was still wide open. I wasn't a beginner inside the work. I'd been building GoHighLevel workflows, n8n integrations, and lead-routing systems for years inside other people's projects. What was new was selling that work as the headline offer instead of the side dish. If you're inside an established service that's still feeding you steady, the math runs different. Read the rest of this section through that lens.

Hormozi's frame again: focus is the things you refuse, not the things you list. The most focused person does one thing. The clip didn't tell me what to switch to. It just unlocked permission to act on a gut feel I'd been sitting on for months.

Three things I used when I cut Webflow. Not a study, not a published rule. Just the path I walked.

1. The market signal from outside. I'd been using Claude and Claude Code to build Webflow sites faster, learning Webflow and Figma MCPs, even pushing my own old Webflow site to a 100 PageSpeed score on desktop. I was adopting AI into the Webflow work. Website clients didn't care about that. They cared about the site, not the toolchain behind it. That's when the question flipped. If AI is doing the heavy lift on my side anyway, why not sell the AI work itself.
2. The hidden offer you've been doing under another name. I'd been building automations for years inside what I called "website projects." Lead routing, form-to-CRM, payment workflows, scheduling logic. Always under the surface of the deliverable, never on the invoice as its own line. My original plan was to keep selling Webflow first and upsell automation as the second step. The Hormozi reframe killed that plan. Lead with the thing that's already getting traction, not with the wrapper around it.
3. The slow drag on the old offer. For me the drag was specific. I'm a Webflow developer, not a designer. Most of the inbound was looking for a designer. The pool I could honestly compete in had been shrinking for a while, and picking up design from scratch wasn't a months-fast move. The drag isn't always price compression. Sometimes it's a skill mismatch with what the buyer is asking for, and the longer you ignore it, the harder the door gets to push open.

Stack those three. Where is the market heat moving. What have you been doing all along that you haven't named. How is the old offer getting harder for you specifically. The cut tends to make itself when all three line up.

Honest read on the emotional side. I'd been a website developer my whole career. WordPress, then Webflow the last few years. The identity was earned. What I didn't see at the time was that I'd been building automations the whole way through, just under the surface of a "website project." I never called it that out loud.

AI commoditizing site builds is what surfaced it. The path I'd been walking the whole time finally had a name on it. So the cut didn't feel like loss. It felt like I'd been pointing at the wrong half of the work for years.

I never reversed the call once I made it. Closest thing to a "miss Webflow" moment was the urge to build a great site for myself, which I solved by building this one. Different stack, full creative control, no client constraints. Webflow muscle memory ported over fine. Webflow as a service didn't need to.

What I won't do, and what I will

Quick clarifying section because the question keeps coming up. I won't build websites for clients. I won't recommend website builders. I won't take Webflow rescue work. I won't audit a site for design quality.

I will wire AI into existing GoHighLevel sub-accounts and workflows. I'll build n8n integrations between GHL and any tool with an API. I'll ship custom AI agents into agency operations: qualification, summarization, follow-up, internal ops. I'll migrate a working Make scenario to n8n when the cost makes sense, using the n8n vs Make rule I default to.

The line is simple. If the work is about building or designing a site, that's a referral. If the work is about AI inside a workflow, that's mine.

FAQ

How do I know if you're the right fit for a marketing agency on GoHighLevel?

If your team is losing hours to workflow debugging, manual qualification, manual follow-up, or summarization that should already be automated, that's the shape I work on. Custom workflows inside GHL, AI inside the sub-account, n8n integrations between GHL and anything with an API, multi-sub-account rollouts. Home-services agencies (HVAC, roofing, pest control, solar, plumbing) are where the work fits cleanest. What I won't do is resell a snapshot off the shelf and drop it into your account. I build them. I don't flip them.

How did you pick AI and automation specifically?

Gut feel that lined up with what was already showing in the market. Site builds were getting cheaper to ship as AI took over the heavy parts. Automation work was getting more valuable because every agency suddenly needed someone to wire AI into their ops. The two curves crossed. I'd been building automations for years inside what I thought were "website projects." I just hadn't called it that. The pivot wasn't picking a new skill. It was renaming the half of the work I'd been giving away for free.

I came to you for a Webflow build before. Who do I call now?

Reach out via the contact form anyway. I don't have one Webflow shop on retainer, but I've got a network. Tell me what you need and I'll help you find the right fit from it. No fee, no kickback. You'll get a faster yes than if you start from cold.

Where I land

Focus is the quality and quantity of things we say no to. Thirty days, four signed, three active across three verticals. The receipt is small at agency-owner scale, big enough to trust the call. The next service that needs revisiting in twelve months will be one of the three I currently sell. The discipline isn't pivoting, it's pivoting on time.

If you're new to the term, here's what an AI automation engineer does and when an agency owner should hire one.

More shipped builds at /projects.