Folloze-One-To-One-Microsite-Builder

Folloze One-To-One Microsite Builder

Use this skill to build a Folloze-ready page for one named account or customer. The page should feel like the seller or vendor understands the account's public business context, not like an internal account plan was pasted into a page.

Fit

Use this skill for named-account pages, executive follow-up, post-event one-to-one pages, account-specific ABM, renewal/expansion stories, and deal-room-style microsites. If the user wants a broad campaign page, use Folloze-Top-Of-Funnel-Campaign-Landing-Page.

Required Foundations

1. Confirm the named account, visible brand owner, and primary conversion job. If an upstream route handoff is supplied, inherit it without rerunning routing.
2. Run $abm-strategist. Do not start design or HTML until its campaign brief and page structure have been presented and approved.
3. 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.
4. 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:

• Vendor or seller organization.
• Target account name and public website.
• The trigger: meeting, event, campaign, opportunity, renewal, expansion, or outreach.
• CTA: continue the conversation, book a workshop, review resources, register, evaluate a solution, or another clear next step.
• Approved sources: public account research, call notes, CRM, Drive assets, content links, screenshots, or pasted notes.

Source Boundaries

• Private notes, CRM, email, Slack, and meeting summaries are strategy inputs only.
• Buyer-facing claims must come from public account evidence, approved content, or user-approved wording.
• Never expose contact-level intent data, private notes, known-contact counts, internal objections, budget comments, sales stage, pricing, or procurement details unless the user explicitly approves that visible copy.
• For any personalized detail, read references/personalized-not-creepy.md and classify it as Safe, Risky, or Prohibited before it appears on the page. Keep Safe, fix or cut Risky, and never include Prohibited.

Workflow

1. Inherit the approved campaign brief and page structure from $abm-strategist.
2. 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.
3. Use the vendor brand as the primary visual system. Use the target-account brand only as a respectful secondary accent unless the user asks for co-branding.
4. List the personalized elements you plan to show, name each source in one sentence, and apply the personalized-not-creepy rubric before drafting buyer-facing copy.
5. Translate the approved narrative structure into the best page shape without changing its strategic argument.
6. Build one self-contained local HTML file in the active repo.
7. Include real resources, anchors, modals, videos, or CTA links. Do not include decorative dead controls.
8. QA desktop/mobile, buyer-safe copy, personalization provenance, source-brand fidelity, and CTA behavior.
9. Complete a buyer-facing QA pass across copy, links, interactions, desktop/mobile layout, placeholders, and dead controls before save, publish, or delivery.
10. For Folloze save/publish, use the available Folloze MCP publishing tools and current Folloze guide. Keep local source path, board ID, returned edit URL, and public URL status separate.

Page Standards

• First viewport must name the target account or make the account context obvious.
• Use the account's real operating context, public priorities, industry, event trigger, or known initiative to sharpen the story.
• The page should make the next seller action easier: a precise follow-up, a buyer-ready link, or a focused meeting ask.
• Do not over-personalize in a way that feels watched. Recognize the account; do not reveal surveillance.
• The page should feel prepared from professional homework, never like the account is being watched.

QA Gates

Before final response or publish:

• Account identity is correct and not confused with a similarly named entity.
• $abm-strategist brief and page structure were explicitly approved.
• 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.
• Public-facing claims are sourced or user-approved.
• Private context has been translated into public-safe problem language.
• Every visible personalized element has a named source and has passed the Safe/Risky/Prohibited rubric.
• Any Risky personalized element has been generalized, explicitly confirmed by the user, or removed.
• CTA is specific and functional.
• Vendor and account logo treatment is verified.
• Mobile and desktop layouts are readable.
• 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.
• The final response includes the list of personalized elements and sources for explicit confirmation before any live publish.
• If saved through Folloze, report local source path, board ID, returned designer URL, and public URL status separately.

Final Response

Return the local file path, approved brief/structure status, brand-harvest path and review status, account/page angle, CTA, source boundary caveats, rendered QA status, and Folloze save/publish status.