A landing page should continue the conversation started by the ad.
For Corpus, a Pilates and physiotherapy studio, I designed campaign-specific entry points. Pilates, physiotherapy and RPG each needed a relevant starting point, while sharing one visual system.
The page keeps the brand’s warm, editorial character through typography, photography and movement. Clear service information and WhatsApp calls to action give that visual experience a practical next step.
My role covered art direction, responsive web design, interaction and AI-assisted front-end development.
This clip shows the general version. The responsive layouts follow the same visual language across desktop and mobile.
When designing campaign landing pages, do you start with one master page or with the individual ad journeys?
The WhatsApp handoff could preserve the service context too. A prefilled message naming Pilates, physiotherapy or RPG would help the studio understand why someone arrived, without making them explain the ad they clicked. I’d measure that click separately from a confirmed booking.
I designed and built this hero as a concept for Nation, an AI store builder for first-time sellers. You write one sentence, and Nation builds the store, runs the ads and ships the orders while you approve each step
The brief asked for “a nation, not a SaaS.” A nation is somewhere you travel to, so the hero is a boarding pass for one trip: JOB → OWN, from your 9-to-5 to your own store. The ticket’s only highlight is “First sale,” which promises money without promising a number
Before the ticket I tried a flag, a passport, a main street of shops and a shipping box. The box didn’t make it, but its airmail stripes ended up on the stub
On the live page the two torn halves of the ticket snap together, the page builds around it, and hovering flips it to the back. Below that, one real seller’s story explains the product with the interface set into the sentence
Nice breakdown. Mine for small business sites: WordPress with Elementor for builds, WooCommerce for stores, Search Console plus Lighthouse for before and after speed reports, and LiteSpeed Cache on the hosting side. The one habit I'd never drop is a full backup and a staging...