MARKETING SITES AND LANDING PAGES
Pages built to be read, found, and acted on.
A marketing site has one job: get a stranger from a search result to a reply. Most sites lose that visitor somewhere in between — a hero that says nothing, three scroll-jacked sections, a 4-second load on 4G. I build the opposite. Static-rendered Next.js pages, one clear argument per page, a form that works without JavaScript enabled.
Scope here is roughly five to forty pages — home, services, work, about, contact, plus campaign landing pages that each target one offer. Every page gets its own title, description, H1 and schema block instead of a template with the nouns swapped. Copy is part of the build, not a field you fill in afterwards. I draft it with you and it ships with the page.
Honest version of the scale: I am one person in Mumbai, there are no Wish Master clients paying for this yet, and the proof is this network of sites plus the sites I shipped while employed. What that buys you is a short line — the person who designs the page is the person who deploys it and the person who fixes it at 11 p.m.
WHAT I DO
- Page-level copy — headline, subhead, body and call to action written per page, not placeholder text swapped out at the end
- Static-rendered Next.js build — marketing pages pre-rendered at build time, with no client-side data fetch for anything above the fold
- A form that submits somewhere real — validated, spam-filtered, with the enquiry landing in an inbox and in a CRM record
- Per-page metadata and Open Graph cards, so a link pasted into WhatsApp or LinkedIn does not render as a blank rectangle
- Campaign landing pages — one offer, one call to action, a separate URL per channel so attribution survives the click
- Responsive down to 360px, checked on a real phone rather than a browser window dragged narrow
- Handover notes: where each piece of content lives, how to change it, how to redeploy
HOW I WORK
- 01
ARGUE
I write the one sentence each page has to win, and any page that cannot earn one gets cut from the sitemap before design starts.
- 02
DESIGN
Layouts drawn against the real copy at three widths, so nothing is approved as a pretty mockup that breaks when the text arrives.
- 03
BUILD
Next.js build with metadata, schema, image sizing and form handling done per page as it is built, not retrofitted.
- 04
SHIP
Deploy to Vercel, domain and SSL pointed, analytics and Search Console verified, then a page-by-page check on a phone on mobile data.
BEST FOR
- Service businesses whose pitch is better than their current site, which is a slow template nobody enjoys sending
- A launch that needs five to ten pages live in weeks rather than a six-month redesign committee
- Founders running paid traffic who need a landing page per campaign instead of pointing every ad at the home page
NOT THIS
- Not the platform build. Logins, dashboards, user accounts and anything with records being written belong on the Next.js platforms and portals page.
- Not an ongoing SEO engagement. This includes clean per-page markup, but cluster research at depth, entity graphs and programmatic templates are the SEO architecture page.
- Not a component library. If what you actually need is tokens, variants and documented components your own developers build against, that is the design systems page.
THE PROOF
Published case studies from digital experience work. Each one names the client and shows what was delivered.
STRAIGHT ANSWERS
REST OF DIGITAL EXPERIENCE
MAKE A
WISH.
Tell me what you're building. I'll tell you how loud it can get.
- /01
YOU WRITE
Tell me what you're building and what's in the way. Two lines is enough.
- /02
WE TALK
A 30-minute call, booked within 7 days. Real questions, no pitch theatre.
- /03
YOU GET A PLAN
Scope, timeline and an honest number, usually within a week.