Landing pages built around one action, and measured against it

What landing page development actually means

A landing page is a single page built for a single action, usually the destination of an advertisement, an email or a specific search. Everything on it either moves the reader toward that action or is costing you, and that constraint is what makes it a different discipline from building a website.

The most common failure is not design and not speed. It is message match: the ad promised one thing, the page opens with something adjacent, and the reader spends their first two seconds working out whether they are in the right place. Fixing that costs nothing and outperforms every visual change anyone will suggest.

Who this is for

• Businesses running paid campaigns that currently point at a home page
• Companies launching one product, offer or event who need a page for it now
• Services with a single high-value conversion — a consultation, a quote, a booking
• Anyone who wants to test an offer before committing to building a full site
• Businesses whose main site cannot be changed quickly enough to keep up with campaigns

Who it is not for

Saying this out loud costs me some enquiries and saves both of us the ones that would have gone wrong. If you are on this list, I will tell you in the first reply rather than after a deposit.

• Businesses that need a full website and are hoping one page will substitute. It will not, and it will look like what it is
• Complex products requiring genuine research and comparison before purchase
• Anyone without a defined offer. The page cannot be built until the offer exists
• Campaigns with no tracking and no budget to measure, since the page then cannot be judged

The problems it solves

Paid traffic landing on a home page

A dedicated page matching the ad promise, so the reader is not asked to navigate to what they were sold.

Three competing calls to action

One action, chosen deliberately. Competing actions reliably convert worse than any one of them alone.

A hero image pushing the offer below the fold

The offer and the action are visible on a phone without scrolling.

Slow pages burning ad budget

Static HTML with no framework runtime, because you have already paid for the click before the page loads.

No idea what the conversion rate is

Tracking configured before launch, so the first campaign produces data rather than an anecdote.

Objections never addressed

The structure handles the objections that actually stop people, in the order readers raise them.

What you get

• One page, one conversion action, agreed in writing before the design starts
• Above-the-fold offer and call to action visible on a phone without scrolling
• Conversion-focused structure: problem, proof, objection handling, action
• Form or booking flow with server-side validation and spam protection that is not a CAPTCHA wall
• Sub-second render on 4G — no framework runtime, no render-blocking third-party scripts
• Conversion tracking wired up, so the page can be judged rather than admired
• Thank-you page and confirmation email, because the flow does not end at submit
• A/B-ready structure if you intend to test variants later

What is included in the starting price

Everything below is in the $40 figure. Nothing here is quoted as an extra once the build is underway, which is the point of publishing it.

• One page with one defined conversion action, agreed before design begins
• Offer and call to action above the fold on a 360px screen
• Conversion-focused structure: promise, proof, objections, action
• Form or booking flow with server-side validation and spam protection
• Sub-second render on 4G — no framework runtime, no render-blocking third-party script
• Conversion tracking configured and tested before launch
• Thank-you page and confirmation email
• Mobile-first responsive build tested on a real handset
• 30 days of snag fixes after go-live

What costs extra, and why

A quote that omits these is not cheaper — it is less honest. Each one is real work that someone has to do, and pretending otherwise is how a fixed price becomes a negotiation in week two.

Copywriting

Structure and editing are included. Writing the offer from nothing is separate, and it is the highest-leverage work on the page.

Additional variants for A/B testing

Quoted per variant. Worth doing once you have enough traffic to reach significance and not before.

Campaign management

I build the page. Running and optimising the advertising is a different specialism.

Custom illustration or video

Commissioned separately where the offer genuinely needs it.

Integration with a CRM or email platform

Straightforward where the API is documented, and quoted per platform.

How the work runs

1. Define the action. One action. Call, book, buy or enquire. A page with three equal calls to action converts worse than any one of them alone.
2. Structure the argument. Offer, proof, objections, action — in that order, because that is the order the reader raises them.
3. Build. Static HTML and Tailwind. Landing pages are where page weight costs the most, since half your traffic arrives on paid clicks you have already paid for.
4. Instrument. Conversion tracking before launch, not after the first campaign has already spent its budget unmeasured.
5. Launch and read the numbers. The page reports a conversion rate within a week. That number, not an opinion about the design, decides what changes next.

Day by day

2 days from the day scope is signed off. Published as a schedule rather than a promise of speed — you should be able to tell on day three whether a build is on track.

The technology

Deliberately boring, and that is the feature. A stack another developer can pick up is worth more to you than one that impresses other developers.

Markup

Static HTML. A landing page is where every kilobyte is paid for twice — once in ad spend, once in bounce

Styling

Tailwind CSS, purged, inlined where it measurably helps first render

Forms

PHP with server-side validation and a honeypot, rather than a CAPTCHA that costs conversions

Tracking

Server-side or cookieless where possible, so consent banners do not eat the data

Hosting

Static hosting or your existing server. Nothing here needs a specialist landing page platform

What it integrates with

• Google Ads and Meta conversion tracking
• Email platforms and CRMs with a documented API
• Calendar and booking tools where the conversion is an appointment
• Stripe, where the action is a direct purchase or deposit
• WhatsApp click-to-chat, which converts strongly in several markets
• Privacy-respecting analytics that survive a consent banner

What I need from you

Short list, and the first item matters most. Projects do not usually slip because the code was hard — they slip because a decision waited a week.

• The offer, stated plainly, including the price or the reason there is not one
• The ad or email the page is the destination for, so the message can actually be matched
• Proof: testimonials, results, credentials — whatever a sceptical reader would want
• The three objections you hear most often on the phone
• Access to the ad account for conversion tracking, or someone who has it

Content and photography

The copy is the page. Design decisions on a landing page are mostly about not getting in the way, and the single largest gain available on almost every underperforming page is making the first sentence match the promise the visitor clicked.

Write the objections down before writing anything else. Every reason someone gives on the phone for not proceeding is a section the page needs, and the page that addresses four real objections beats the beautiful one that addresses none. That list comes from you — it is the part of the work I cannot do without your sales experience.

Performance standards

Targets, not aspirations — measured before handover on a throttled mobile connection rather than on a fast laptop.

Accessibility standards

This site is built to the same standard it sells, and the accessibility statement lists what is conformant and what is not — which is the part most statements leave out.

Security practices

The SEO included in every build

Not an upsell. A site that launches unindexed is a shop with the shutters down, and the work below is cheap during a build and expensive afterwards because the fixes are structural.

Ownership and handover

You own everything: the domain registered to you, hosting in your account, code in a repository you control, and the payment provider account in your business name. Credentials are handed over as they are created rather than at the end.

A supplier who resists this is protecting recurring revenue rather than your interests. If you want the reasoning in full, including how to check your current site, there is a guide on it.

Aftercare and what happens after launch

Thirty days of snag fixes are included. A snag is something that does not work as scoped — not a new feature, and the difference is written down before launch rather than argued about after it.

You also get written handover documentation aimed at whoever maintains the site next, which may well not be me. That is deliberate: the test of a good handover is whether another developer could take over without calling me, and on my projects they can.

Ongoing maintenance

Optional, monthly, cancellable. Nothing here is required to keep what you paid for.

Payment terms

How this compares to the alternatives

Including the routes that do not involve me, because a comparison that only flatters the author is not a comparison.

What could go wrong, and how it is handled

The offer is not actually defined

Surfaces on day one. The page cannot be built around an action nobody has chosen.

Copy is not ready

Copy is the bottleneck on nearly every landing page. Flagged at scope, and the date moves rather than the quality.

Not enough traffic to judge the page

A conversion rate on forty visits is noise. You are told what volume is needed before drawing conclusions.

Tracking blocked by consent tooling

Checked before launch. A page you cannot measure is a page you cannot improve.