A landing page is a sales page with manners
Build a single page that states the offer, who it is for, how it works, proof stubs, price or waitlist, and a clear button. Use Framer, Webflow, or Durable — pick one and finish. Switching builders is a hobby, not a strategy.
Structure: headline from Part 2, three benefit blocks from the NotebookLM phrases, a simple process (Discover → Build → Deliver), FAQ, and footer with contact. Link out to your AI Arsenal only if it helps the reader. Do not turn the page into a tool directory.
Measure the only metric that matters now
Install the simplest analytics your host offers. Watch waitlist signups or checkout starts. Ignore vanity. If nobody clicks, rewrite the headline before you rewrite the product.
Connect the domain. Use HTTPS. Test on a phone. If the button is hard to tap, you are not ready to advertise anything — including your own ego.
Publish while scared
Ship the page this week. A private draft cannot teach you. Share it with five people from the niche and ask what confused them. Fix the top confusion. Then stop polishing.
Running tip: keep a changelog on the page ("Updated this week"). Motion signals life. Dead pages do not convert.
Field notes
Field note: your first site is a hypothesis board, not a museum. Put the publish date in the footer. Update a sentence weekly. Motion tells visitors a human is home.
If you need more than one page to explain the offer, the offer is still fuzzy. Extra pages can arrive after the first ten conversations.
Operator checklist
Operator checklist: publish a one-page site with headline, three benefits, process, FAQ, and a single CTA to waitlist or checkout. No blog yet. No about essay. No tool zoo.
Click every link on a phone over cellular. Fix tap targets and form errors before you tell Twitter. Broken launches create permanent first impressions.
Collect five pieces of confusion feedback, fix the top two, and freeze the page for seven days. Observation needs a still target.
How to run it this week
Write FAQ answers that kill the top five fears: time, money, skill, privacy, and "will you disappear." Fear is the silent bounce reason.
Add a single primary CTA. Secondary links are how pages lose elections. One button. One job.
Set a launch date and tell someone. Public deadlines create gravity. Private projects float forever.
What good looks like
What good looks like: a live URL with one CTA and five pieces of real confusion feedback already fixed. Draft sites do not collect truth.
Common failure mode: building a sitemap for a company that does not exist yet. One page. One job.
Series bridge
Series bridge: this chapter sits between designing the flag and building the product. If you skipped here, go back one part and finish the checklist first. The playbook only compounds when each layer is real — research under offer, offer under site, site under product, product under distribution.
Keep a single Notion page titled Kingdom OS and paste the outcome of this part at the bottom before you leave. Date it. Future you will skim twenty dated notes faster than twenty open browser tabs. That page becomes the operating system the last chapter asks you to run daily.