top of page

The $0 Front Door: How I Run a Professional Web Presence on a Free Website

Writer: Brian Lathe
Brian Lathe
Oct 29
4 min read

Every professional-looking web presence you've ever admired is three jobs wearing a trench coat:

  1. A door — an address people can remember and trust.

  2. A handshake — the moment a visitor becomes a contact.

  3. A room — the place with the actual content in it.

Most people pay one company to be all three. That's how you end up renting your own audience back from a platform, one monthly plan at a time. I run a one-person operation with a fleet of machines and a small crew of local AI models, each with one defined job, and I needed the opposite: every layer owned or free, every layer replaceable, and the whole thing wired into the system that runs my business.


So I split the trench coat.


The chain

The door is a real domain, bought at NameCheap. Not through a website builder — builders sell domains as the first link in a chain they control. A registrar is a commodity; the domain is mine, portable, and costs a few dollars a year.


The handshake is a FlexiFunnels page. The domain's DNS points at FlexiFunnels — a CNAME record, two minutes of work — so the page the public sees lives on my real domain, with proper HTTPS. That page has exactly one job: capture the lead. Email and WhatsApp number. Nothing else happens before the capture, because a visitor you can't contact again is just weather.


The room is a free Wix site. After the capture, FlexiFunnels sends the visitor onward to a Wix site on its free subdomain — the long-form content, the proof, the video, the articles. Wix's free tier is genuinely good at being a room. It's terrible at being a door (a free site can't take a custom domain at all) and it isn't allowed to be the handshake (the list has to live in my systems). So it does the one job it's great at, and it costs zero dollars a month — which means I can have as many rooms as I want. One per offer. One per campaign. Unlimited doors' worth of rooms, all free.


People trip over one detail here, so let me be direct: after the handoff, the address bar shows the Wix subdomain. I don't care, and you shouldn't either. The visitor arrived through a professional domain, shook hands on that domain, and is now reading in a clean, fast room. The professional impression is made in the first ten seconds — the door and the handshake — and both of those are mine.


The part nobody sees: the plumbing

A captured lead is not a lead. A captured lead is a rumor of a lead until it lands somewhere that works it.


When someone opts in on the FlexiFunnels page, a webhook fires into n8n — the automation layer of my stack — which does two things instantly: it files the person into ContactFlowCRM, my relationship system, where a lead becomes a person in a graph with a history and a next step; and it subscribes them in systeme.io, which runs the email follow-up. The WhatsApp number matters as much as the email: it's the key that lets the relationship continue on WhatsApp, where people actually answer.


No spreadsheets. No "export the CSV on Friday." The lead is being worked before the visitor finishes reading the article they were sent to.


Analytics, honestly

Google Analytics has a rule in this architecture, and it's a rule with one honest exception.


GA4 sits on the FlexiFunnels pages (their tracking-code settings take the tag natively), on my blog at Substack (one measurement ID field in the settings), and on my own servers. It does not sit on the free Wix site — Wix reserves analytics integrations for paid plans, and paying to remove that one limitation would collapse the entire cost structure for almost no information.


So the Wix leg is measured from the doorway instead: the FlexiFunnels → Wix handoff is a tracked event, and every redirect URL carries UTM parameters — source, medium, and a campaign tag naming the funnel it came from. My chain software treats this as law, not habit: a funnel is not allowed to go live unless its redirect carries the full UTM set. The rule is enforced by a validation script, because rules that live in blog posts get forgotten and rules that live in code don't.


The meta part (you're reading it)

This article lives in one of the free rooms. You probably arrived here through a FlexiFunnels page on a real domain, where you left an email and a WhatsApp number — the exact handshake described above. The system that registered that funnel, validated its analytics tags, and filed your contact into my CRM is the same system this article describes: a coded registry that models every domain, funnel, and site as one chain, and refuses to let a broken chain call itself live.


That's the real difference between a stack of tools and an operating system. Tools wait for you to remember the rules. A system remembers them for you — and checks its own work, hourly, whether you're watching or not.


The front door cost: one domain registration. The rooms: free. The handshake: a funnel tool doing the one job it's best at. The plumbing: mine.


Build the chain once. Then just write.


Read more from Brian Lathe on Substack


This blog is one room in a bigger house. My main writing lives on Substack - longer pieces, new posts first, always free to read: Brian Lathe on Substack.

 
 
 

Recent Posts

See All
Do You Need an Integrator If You're a Team of One?

Do You Need an Integrator If You're a Team of One?If you've read anything about EOS — Gino Wickman's Entrepreneurial Operating System, from Traction — you've met the famous pair. The Visionary is the

 
 
 

Comments


Talk to Brian

on WhatsApp

Appointment booking opens soon.

Questions about this article — or about SuccessBrian OS? Text me here.

Texting is best — please don't call. Calls are by confirmed appointment only.

Talk to Brian

Questions, or want a system like this working for your business? Message me directly.

What is SuccessBrian OS?

One system that runs a solo business while its owner lives his life: a checked second brain, a crew of AI agents, and one calendar that never forgets. The whole system is free and open.

Get new posts by email

I build this in public and post the progress. Follow along on Substack.

bottom of page