Folloze-Top-Of-Funnel-Campaign-Landing-Page

Folloze Top-Of-Funnel Campaign Landing Page

Use this skill to turn a broad campaign idea into a buyer-facing Folloze landing page that can support paid media, social, web, events, partner marketing, or nurture entry points.

Fit

Use this skill when the page is one-to-many and should avoid named-account assumptions. If the request is for a named account, use Folloze-One-To-One-Microsite-Builder. If it is for a vertical or segment page, use Folloze-Industry-Campaign-Page-Builder.

Required Foundations

• Keep the brief one-to-many unless named-account evidence changes the motion. If an upstream route handoff is supplied, inherit it without rerunning routing.
• Run $abm-strategist only if the request becomes named-account or one-to-few. Do not invent a target account for a broad campaign.
• For a Folloze-owned experience, use $folloze-brand-kit. For an external brand, run $brand-harvester and require a zero CLI exit plus brand.json.validation.status: ok before visual design.
• Use $folloze-board-quality-core for source discipline, experience-shape selection, responsive and interaction QA, analytics, and MCP preflight.

Minimum Inputs

Gather only what is missing:

• Campaign goal and primary CTA.
• Audience segment or persona.
• Offer, event, product story, or resource.
• Source brand page, brand guide, screenshot, or approved design direction.
• Required content links, forms, calendar links, videos, or resources.

If the user only provides a URL and goal, infer the first draft from the source page and clearly label assumptions.

When required campaign assets are missing, load and apply Missing Campaign Asset Fallbacks before building, saving, or publishing.

Workflow

1. Build a short campaign brief: goal, audience, offer, promise, CTA, source inputs, and constraints.
2. If the motion changes to named-account or one-to-few, stop and run $abm-strategist before continuing with the matching customer builder.
3. Complete the brand gate before visual design: $folloze-brand-kit for Folloze-owned work or a saved, reviewed, validated $brand-harvester bundle for an external brand.
4. Choose a simple landing-page shape: hero, why now, value proof, how it works, resource/offer module, CTA.
5. Create a single self-contained HTML file in the active repo.
6. Keep buyer-facing copy public-safe. Do not expose internal notes, sales scoring, intent data, private meeting notes, or tool mechanics.
7. Add real buttons, anchors, resource links, forms, video embeds, and analytics hooks where supported.
8. If any required URL, form, event detail, asset, theme, or consent text is missing, apply the fallback reference and maintain a visible fallback inventory.
9. QA desktop and mobile before Folloze save or handoff.
10. Complete a buyer-facing QA pass across copy, links, interactions, desktop/mobile layout, placeholders, and dead controls before save, publish, or delivery.

Copy Standards

• Make the first viewport explain the offer in under 10 seconds.
• Use plain campaign language: what the visitor gets, why it matters now, and what to do next.
• Avoid visible words like demo, template, wireframe, test, internal, generated, or placeholder on final/approved pages; provisional pages must visibly flag missing assets per the fallback reference.
• Do not make Folloze the visible brand unless the campaign is Folloze-owned.
• Use proof only when sourced from public pages, approved materials, or user-provided facts.

Recommended Page Shapes

• Offer landing page: hero, problem, offer, proof, resource preview, CTA.
• Event awareness page: hero, audience promise, agenda/outcomes, speakers or proof, registration CTA.
• Product launch page: hero, shift in market, capability story, use cases, proof, request CTA.
• Partner campaign page: co-branded hero, joint value, workflow, resources, shared CTA.

QA Gates

Before final response or publishing:

• The page has one clear CTA path and no dead controls.
• The selected brand path is complete: $folloze-brand-kit for Folloze-owned work, or a durable validated $brand-harvester bundle for external-brand work.
• $folloze-board-quality-core passed for source/proof discipline, selected experience shape, desktop/mobile render, controls, analytics, accessibility, and save readiness.
• Rendered desktop and mobile views were compared with the harvested source screenshots or approved equivalent brand evidence.
• Desktop and mobile layouts are readable with no horizontal overflow.
• External links and embedded media load or have a deliberate fallback.
• Copy is public-safe and not account-specific unless approved.
• Styling follows the source design context instead of generic AI gradients or decorative filler.
• Any fallback content, interim route, bracketed value, placeholder asset area, or unconfirmed legal language is summarized in one user-facing list and explicitly confirmed before saving to a live board.
• Buyer-facing copy, links, interactions, desktop/mobile layout, placeholders, and dead controls have been checked and any blocking issues have been fixed or explicitly reported.
• If publishing through Folloze MCP, use the available Folloze MCP publishing tools and current Folloze guide. Report the exact board ID, returned edit URL, and public URL status separately.

Final Response

Return the local file path, campaign-brief mode, brand-harvest path and review status, campaign goal, CTA, rendered QA status, and whether the page is local-only, ready for Folloze publish, or already saved/published.