Loading...
Loading...
Product launch microsite
Give the launch one place for the story, outside proof, waitlist and press assets. Agree what happens to the pages afterwards.
Three routes
The smallest change that meets your date is the right one. I mark the standalone route because it fits a fixed date and a blocked main site. The inventory can still send you to the smaller route. I tell you which one after step 2.
Your main site can carry the story. I add the launch pages, the form and the tags inside the site you already have. This is the smallest of the 3 routes.
Scoped in writing after the inventory.
Your main site cannot carry the campaign cleanly. A separate site gives the launch one address and an agreed post-launch destination.
Scoped in writing after the inventory.
You run several campaigns. The approved block system can be reused, while each campaign receives its own inventory and scope.
Scoped in writing after the inventory.
Who does the work
Scope
The process
After the inventory, the written scope names the approved assets, dependencies, approval points and expected effort.
I list every asset the launch needs: copy, proof, images, video, press files, forms and tags. We agree the pages in scope, the review window, the content cutoff and who signs off.
Output: A written scope, the named approver, the content cutoff, the missing items and my route recommendation.
I build the pages from reusable blocks, with the form, the consent banner and the analytics. I load the copy, proof, images and press files your approver signed off. I then check accessibility, links, downloads, forms and every date on the page.
Output: A complete preview site with a visible change log, a test lead inside your own tools, and the acceptance fixes.
I publish after the named approver releases the pages, check the forms and analytics, and hand over editor access.
Output: A live launch site, an editor guide, and the agreed end-of-campaign plan.
Safeguards
A launch puts 3 things at risk: the date, the press files, and who owns the site after the campaign.
Questions
Tell me the date first. I inventory what you have, then I say in writing what fits before that date. If there is not enough time for the content, the review and the checks, I turn it down. To add the launch to your current site takes less time than a standalone site.
A landing page carries one ask. A launch has a teaser phase, a launch day and months of follow-up traffic. If your main site can carry all 3, add the launch to your current site.
A folder uses your main site's existing domain. A separate address starts without that history. Your search owner approves the final route.
One address with 3 phases takes a date change without a rebuild. Three separate pages do not. We agree the launch-day swap at step 1. A new date is then a content change.
You decide before launch, not months later. Fold the pages into your main site, redirect them, or archive them with a visible end notice. The decision goes in the written scope.
Yes. Your team edits the copy, images, dates, proof and FAQ in the CMS. A new block type or a layout change still needs a developer.
The form writes into the tool your team already uses. It captures consent and gives an unsubscribe path. We send a test lead and check the events before launch day, not on it.
Your advisor supplies the privacy, cookie, company and accessibility requirements. I build those approved requirements and record them in the acceptance checklist.
Send the approved message, outside proof, destination form and launch constraint. I return the route, missing assets and risks in writing.
Send me the launch date