AIMay 9, 202611 min

Landing in a day using Claude Code: step-by-step analysis from technical specifications to deployment

One of the last landing pages was done like this: brief in Notion (15 min) → Claude Code scaffolding (40 min) → copy in voice (60 min) → finishing through v0 (30 min) → Vercel + DNS (15 min). The contractor's starting rate is 180K ₽ for 4 weeks. I did it in 3 hours.

In April 2026, I made a landing page for one of the client projects using the following formula: brief in Notion (15 minutes) → Claude Code scaffolding (40 minutes) → copy in my voice (60 minutes) → design fine-tuning via v0 (30 minutes) → deployment Vercel + DNS (15 minutes). Total - 2 hours 40 minutes. The contractor's starting bid for the same technical specification is 180,000 ₽ and a 4-week deadline.

This is not a “AI is replacing developers” post. This is about a specific model of a marketer’s work in 2026, in which the landing page for the campaign is done by him - because owning the landing page is part of owning the funnel. And the article below is a step-by-step analysis of that workflow, step by step, without “secret prompts”.

Landing in a day is not “typing speed.” It's the difference between "I'm thinking about conversion" and "I'm explaining conversion to a contractor who's thinking about breakpoints."

What is Claude Code and why does a marketer need it?

Claude Code is a CLI tool from Anthropic for terminal development with an AI agent. He can read the repository, write code, run tests, make git commits, and follow the documentation. This is not v0 (which generates the component) and not Cursor (which autocompletes). This is an autonomous agent to whom you can tell “make a landing page with a hero section, a contact form and three cases” - and he will do it, asking for clarification only on architectural decisions.

Why do marketers need three reasons:

Speed of A/B tests: editing copy / structure / CTA on a landing page - 5 minutes instead of two days through a contractor
Control over the context: the marketer understands the funnel, the developer does not. A landing page under the brand “X” with an explanatory UX is created only by those who live in this funnel
Cost: $20 per month Claude Code Max subscription + $0 per developer = ~70K ₽ savings on one landing page

The stack that I have on this landing page

Next.js 16 — framework (the same one on which the site is made) dpustovalov.com)
Tailwind CSS v4 — styling through utility classes, without separate CSS files
shadcn/ui — ready-made components for typical UI blocks (forms, cards, tabs)
Vercel — deployment via CLI, autodomain, free tier is enough for 95% of tasks
Reg.ru / Cloudflare - for DNS

This stack is not the gold standard. This is a set where I stop worrying about technical issues and can focus on conversion. Alternatives (Astro, Remix, Svelte) also work, but require more configuration.

Step 1. Brief in Notion (15 minutes)

The brief is half the battle. Before opening Claude Code, I fill out a template in Notion with the following fields:

The purpose of the landing page. One sentence: “register for a free trial lesson” or “request a 30-minute call”
ICP. Who will see this landing page? Age, context, level of product awareness
3 main benefits. From the buyer's point of view, not the seller's
3 main objections. What's stopping you from saying yes?
Section structure. Hero → Social proof → Benefits → How it works → Testimonials → CTA → FAQ
CTA button. The exact wording of the action

I give this brief to Claude as the first prompt - in its entirety, without editing. The time to fill out is 15 minutes, if the ICP is already clear from previous discovery calls.

Step 2. Scaffolding via Claude Code (40 minutes)

I open a terminal in an empty folder and write:

claude

> Make a new Next.js 16 project with Tailwind v4 and shadcn/ui. The page structure is a landing page for [product]. Brief below:
[I paste the entire brief from Notion]

Use:
- Next.js App Router (not Pages)
- Tailwind v4 with @theme config, not tailwind.config.js
- shadcn/ui for forms and buttons
- Inter font via next/font
- TypeScript strict
- Mobile-first responsive

Structure: one file app/page.tsx, sections through components in components/. No backend-routes yet.

Claude Code writes code within 30–40 minutes, installs dependencies, launches npm run dev, checks what's going on. At this time I am opening a preview on localhost:3000 and watch the landing page grow.

Where Claude usually gets stuck at this stage: package versions (selects old ones), and sometimes wants to create unnecessary API routes. Solution: in the brief I explicitly say “no backend” and “use only the latest versions.”

Step 3. Copy to your voice (60 minutes)

This is the step where “okay landing” differs from “landing that converts.” Claude writes boringly by default - in general terms, with the stamps “innovative solutions” and “effective approach”. To get copy in the brand voice, I load the entire folder into context /content/voice/, where 11 files are stored with voice coordinates, rhetorical pillars and a list of AI-tells.

Second round prompt:

Context: [loading all /content/voice/]

Now rewrite all the texts on the landing page according to this voice. Prohibitions:
- No “is”, “is”, “has”
- No “in the modern world”, “it’s no secret that”, “worth noting”
- No “effective”, “comprehensive”, “innovative”
- No “AI changes the rules of the game”

Required:
- At least one antithesis in hero (“not X, but Y”)
- Minimum 2 numbers per 100 words
- At least one scare-quote per industry stamp
- At least one equation or time/cost contrast
- Insider terms - no translation

Each section needs to be rewritten. Show the changes with diff.

One pass is usually not enough - Claude still pulls through 2-3 tells. I make a second pass with specific instructions: “here “is” - replace it with a dash.” At this stage, I often completely rewrite the hero by hand, because the hero is the face of the landing page, there is no “normal” on it.

Step 4. Design fine-tuning via v0 or Figma AI (30 minutes)

Claude Code is good at building structure, but bad at feeling the “vibe.” If the standard shadcn/ui style is not enough, I open v0.dev, ask to rebuild one or two sections in a more avant-garde design, and copy the generated code back into the project.

What I usually ask v0 to do is:

Hero with more complex animation (parallax, gradient mesh, animated text)
Pricing cards with premium effect
Testimonials with asymmetrical grid instead of the usual 3-column

v0, when copied into a project, sometimes breaks the layout because it uses its Tailwind conventions. Claude Code fixes it in a minute: “fix conflicts in this file, keeping the v0 design and integrating it into the overall style of the rest of the sections.”

Step 5. Deploy to Vercel + DNS (15 minutes)

The final step is the fastest if the stack is already standard.

# In the terminal:
npx vercel
# (I answer questions once - link to project, framework, etc)

npx vercel --prod
# (I get the production URL in 60 seconds)

# In Reg.ru / Cloudflare:
# Adding a CNAME record to cname.vercel-dns.com
# In the Vercel dashboard - Settings → Domains → Add custom domain

5–10 minutes after CNAME setup, the landing page is available on its own domain with automatic HTTPS. No separate servers, separate contractors, separate hosting bills.

What I stopped doing after switching to this model

Order a landing page from the studio. 90% of tasks are overkill. A studio is needed when a complex back-end integration or CRM connection is required, and not for a one-pager for a campaign.
Use Tilda and analogues. Tilda is good for a quick MVP, but the crutches with custom code + more expensive hosting + less control over SEO.
Coordinate each edit with the developer. Now editing the hero copy on production takes 10 minutes. Previously, through a contractor - at least 2 days.
Be afraid of technical details. SEO, schema.org, sitemap, IndexNow - Claude Code sorts it out. A marketer should know that these things exist, but should not manually write them themselves.

What you need to know as a marketer to make it work

The minimum technical set, without which Claude Code turns into a black box:

Basic HTML/CSS. Understand what div, class, padding, flex, grid are. Without this, you will not be able to edit the generated code.
React concepts. What is a component, props, state. You don't need to write them, you need to recognize them.
Git basics. Commit, push, branch. So as not to lose your job and be able to roll back.
Terminal. Basic commands: cd, ls, npm, vercel.

This is a volume that any marketer can master in 2 weeks of evenings. Does not require “JavaScript for Beginners” courses, requires one book on Tailwind and one weekend with a tutorial on Next.js.