Beacon SaaS Landing
One bright promise, one product shot, one path to signup.
A SaaS landing-page playbook built around a strong beacon hero: a bold audience-plus-outcome headline, a product shot that proves it above the fold, and social proof made only of real users, quotes, and numbers.
Install it in 3 steps
No sign-up. No CLI tools. Pick your AI, copy one line, paste it over.
Prefer doing it yourself? Buy the skill ($4.99), download the ZIP from your checkout confirmation, unzip it into the directory shown above, restart your AI session — same result. Already bought it? Your AI assistant can download it for you.
What’s inside
One SKILL.md (the playbook) + one starter template. A preview:
Beacon SaaS Landing
When to use
- You're launching a SaaS product and the homepage currently explains what it is instead of why anyone should care
- Visitors land, scroll, and leave because the headline could belong to any of ten competitors
- You have a product screenshot or demo that shows the value in five seconds — but it's buried below the fold
- You have early users, testimonials, or usage numbers and the page doesn't show any of them
- You're sending ad or launch traffic to the page and need it to convert a cold visitor into a signup or trial
Workflow
- Write the beacon headline (input: product + audience + outcome → output: headline + subhead)
Headline = audience + outcome in ≤10 words ("Invoicing that pays you 3 days faster" beats "Next-gen invoicing platform"). Subhead = how, in one sentence, no jargon. Test: could a competitor paste your headline onto their site? If yes, rewrite it until only you can say it. - Place the product shot (input: headline → output: hero layout)
Hero = headline, subhead, primary CTA, product shot directly under or beside the copy. The shot shows the product's key screen with realistic data, annotated if needed. Never a stock photo of people pointing at a laptop — the product is the proof. - Stack the proof (input: testimonials / numbers → output: proof section)
Order: names or logos of real users (only with permission), 2–3 testimonials tied to specific outcomes, one honest number if you have one ("120 teams" — only if true). No fake logos, no invented counts, no "trusted by thousands" on a product with twelve beta users. - Write the feature sections (input: features → output: 3–4 sections)
Each section: one benefit headline, 2–3 sentences, a supporting visual (screenshot, short clip, or diagram). Features that don't map to an outcome get cut or demoted to a spec list at the bottom. A feature section that only describes how something works, not what it does for the user, is filler. - Close with one ask (input: full draft → output: publish-ready page)
One primary CTA (Start free trial / Get started) repeated at the hero, after the proof, and at the close. Pricing or "how it works" linked, not crammed in. Final check: a cold reader can answer "what is it, who is it for, what do I do next" in 30 seconds from the hero alone.
Output spec
Template preview
Beacon SaaS Landing — Page Brief Template
Fill this in before any copy gets written. One product = one brief.
Product: {product name}
What it is (one sentence): {…} Who it's for: {…} The outcome they get: {…}
Beacon hero
- Headline (≤10 words, audience + outcome): {…}
- Subhead (≤25 words, how, no jargon): {…}
- Primary CTA: {Start free trial / Get started / …}
- Competitor test: could a competitor paste this headline on their site? [ ] No — rewrite until only we can say it.
- Product shot: {file / link} — shows: {key screen} | Data in shot: realistic [ ]
