Build a Product Launch Kit from Approved Facts
Create a landing page, workflow page, press material and channel copy from one factual launch brief. Check the actual destinations and interactions before using the campaign.
Fastest way
Ask your AI to do it
Paste this into the AI agent you already use:
Use Launch Campaign Kit with my approved product brief. Ask about audience, offer, workflow, brand and the real CTA destination. Write distinct landing, workflow, press and channel copy without inventing results or scarcity. Generate into a fresh folder, check both themes, pricing periods if present, FAQ, keyboard controls and phone layout. Verify CTA destinations separately; static output does not add signup or checkout services.
What does a launch kit actually deliver?
Launch Campaign Kit creates three self-contained static pages, campaign Markdown, an SVG share card, design tokens, a handoff and a file manifest. It helps align the product story across formats. A signup button or pricing card links to your existing service; the kit does not create authentication, checkout or a contact backend.
Build one approved fact sheet
- Name the audience, offer, problem, three supported benefits, actual workflow and real CTA URL. Separate proposed benefits from measured results.
- Supply FAQ, press information and channel-specific copy. Keep unknown metrics, customer counts, testimonials and scarcity claims out of the brief.
- Read references/customization.md. Choose forest, midnight or cobalt and editorial or spotlight; use a permitted local product image only if it accurately represents the offer.
Start with one product page when a campaign is more than you need
Give each page a different job
For an illustrative product launch, the landing page can explain who benefits and what to do next, the workflow page can show the actual steps, and the press page can give reusable factual details. Channel copy should lead back to the same approved offer. Optional prices use integer USD cents; the yearly recurring amount is the total annual charge, not a monthly equivalent.
Build the fictional campaign first
Read the installed SKILL.md and input instructions. From the package folder, Node.js 24+ runs the fictional example without dependency installation or remote assets. For a real campaign, copy the input and replace every fictional fact, image, price and destination before generating into another fresh directory.
Read this release’s setup before running the example
Confirm installation and invocation in your host
node scripts/build-campaign.mjs --input examples/campaign.json --output ./practice-launchFollow the campaign as a visitor would
- Open index.html, workflow.html and press.html in both themes and at phone width. Test tabs and arrow keys, FAQ controls and relative navigation.
- If pricing is present, switch monthly and yearly views; one-time offers should retain their price and label. Check taxes, trial and cancellation terms against the actual linked service.
- Check every CTA destination independently. A working link is not proof of a completed registration or payment. Reconcile the seven exported payload files with delivery-manifest.json.
Make a product demo from approved launch facts — Use the campaign story and permitted screenshots as inputs.
Inspect the current example output → — Compare the visible result with the exported files and checks described in this section.
Adapt the approved campaign to your site
Deliver the static pages and editable input with the reviewed campaign copy. Framework integration is a separate agent task: inspect the target routes, preserve controls and run that project's build. Use a screenshot-based Product Demo Studio film if the launch needs motion; this kit does not export video or automatically deploy a site.
Plan welcome and activation emails from approved launch copy