All work

Case study 05 · Pre-Landing · Page builder for media buyers

A page goes live
the moment it's published.

Pre-Landing is our own builder for pre-landing pages — the pages between an ad and the final offer — used by media buyers and affiliate marketers running many campaigns at once. Users pick a template, fill in a few fields and publish in one click: the page is live at its own address, with ad-tracking pixels built in. Denys took it from zero to a paid product alone.

Product
Builder for pre-landing pages — our own product
Our role
Creator and sole full-stack engineer (Denys): discovery, architecture, UI/UX, frontend, backend and deployment
Period
2025 → 2026, about three months of development alongside contract work
Users
Media buyers, affiliate marketers and agencies
1 month

to the first version

0

deploys or DNS changes to publish a page

Hundreds

of pages published

30 days

a page stays live after one payment, no account needed

The challenge

Media buyers need a simple, credible page for every campaign, fast — without a full website builder or a developer.

Results

  • Live at pre-landing.com with paid plans and hundreds of published pages.
  • First version in one month; about three months of development in total, alongside contract work.

What we did

  1. 01

    Publish in one click

    Mobile-first templates and a handful of fields; every page gets its own address the moment it's published.

  2. 02

    Built for ad campaigns

    Meta, TikTok and Google pixels are built into every page.

  3. 03

    Pay without signing up

    One-time payments and subscriptions; a campaign can run for 30 days after a single payment, without creating an account.

  4. 04

    The whole product, end to end

    Denys designed and built the data model, backend, frontend and deployment alone.

Under the hood

Instant publishing on subdomains

Every page gets its own subdomain without a deploy or a DNS change:

  1. A wildcard domain sends every subdomain to a single Next.js app.
  2. Middleware reads the subdomain and serves the matching page from the database — a rewrite, not a redirect, so the address stays the same.
  3. Only active, unexpired pages are served; everything else goes to not-found.

How we worked

Built solo in an AI-first workflow with Codex and Claude Code, with custom rules for the coding agents, and deployed automatically through GitHub Actions.

Stack

Product
  • Next.js
  • Middleware rewrites
  • NestJS
  • Supabase
  • PostgreSQL
Payments & delivery
  • plata by mono
  • Vercel wildcard domain
  • GitHub Actions

Start a conversation

Need a product live in weeks?

Tell us what you're building, modernising or trying to unblock. One contract via a Lithuanian entity, EU VAT invoicing — we reply within one business day.