
Ecommerce build
13Product · Case study
Product launch lander — date, specs, notify CTA. We delivered the landing page as a live conversion surface for launch notify list.
01The delivered site
The layout we shipped for this project — desktop first, with a phone view where we have one.

02The brief
What we were hired to fix
Meridian Mark III needed a landing page that did one commercial job: launch notify list. Product launch lander — date, specs, notify CTA.
The constraint was not “more pages”. It was a product audience who would leave if the next step was vague. We treated that as the brief, not a later optimisation.
We shipped a finished landing page — copy, layout and conversion path — so the team could run launch notify list from a URL they own.
03What we delivered
We built Meridian Mark III as delivered work, not a concept. Structure, proof and the launch notify list path were designed together, then implemented as a maintainable front end.
Every block on the page has a job: explain the offer, show evidence, and move a real person to launch notify list. If it did not do that, it did not ship.
We wrote the page around one job — date, prize, wait-list or download — and cut everything that did not serve it.
Stats, rules, specs or social proof sit next to the ask so the visitor does not have to hunt.
Name, contact, the one qualifier that matters, and a button that says the action in plain English.
We shipped the live URL, checked the mailbox, and confirmed the page holds on a phone before any spend.
04Outcomes
Visitors can complete launch notify list without a sitemap. The action sits where the offer is.
Meridian Mark III reads as a product landing page — not a reused template with the logo swapped.
The same structure takes a new offer, SKU or workflow without starting again.
Next step
A short call with the person who would run it — not a sales script.