Hardik Dewra

3 min read

How long does a landing page take to design

One to three weeks for a custom page, four to eight with research and copy. Where the time goes, and the three things that decide it.

A custom landing page takes one to three weeks to design, from signed brief to live URL. This is the timeline when the copy is already written and one person approves the work. Add customer research, original copy and a testing plan and it runs four to eight weeks. WebFX publishes six to eight weeks for its fully custom landing page and two weeks for a template build. This is a fair picture of the wider market.

Where the time goes

Design is the small part. On a typical single page the split is roughly one part strategy, one part copy, two parts design and build, and two parts waiting on feedback, assets and approvals. Nobody plans for that last part, which is why estimates slip. The work itself takes about four days. Those four days get spread across three weeks of calendar.

What decides how long a landing page takes to design

Three things decide it: whether the copy is written and signed off, how many people have to approve, and whether the offer itself is settled. A page with finished copy and one decision maker goes live in a week. The same page with copy coming soon and three stakeholders who each want a call takes six weeks. The design work is just as hard in both cases. The whole difference sits on the client side.

The copy sets the timeline

Most delays come back to words. A designer who lays out placeholder text has to rebuild the page when the real copy lands. This rebuild is a second design phase nobody budgeted for. If the copy is not written, give copywriting its own phase with its own dates. Do not assume it will happen in parallel. It never happens in parallel. Turning up with approved copy is the single biggest thing that shortens a project.

What you control

Name one decision maker who can approve without calling a committee. Put analytics access, brand files, product photography, testimonials and platform logins in one folder before kickoff, not during. Agree a feedback window and stick to it, ideally twenty four hours. Every asset you chase mid-project costs about a day. Days spent chasing are days you already paid for.

What a rushed timeline really costs

Speed is a real product and it gets priced. A designer who clears a week for you turns other work away for that week. So a compressed schedule carries a premium, and a rush fee on short notice is a normal ask. What money cannot buy is decision speed on your side. If you need a page live in five days, you have to answer feedback inside a day, every day. A team that cannot do that should skip the rush fee, because it will burn the money waiting on itself.

Ours, as one data point

We run a single landing page as a five working day sprint. Strategy on Monday, copy on Tuesday, direction on Wednesday, design on Thursday, build and launch on Friday. It works because scope is locked on day one and feedback comes back inside twenty four hours. When either of those slips, the sprint turns into two weeks. We say so at the start instead of pretending the date still holds.

How to set a date you will actually hit

Work backwards from the campaign, not from the design. Take the launch date and subtract a week for tracking setup, QA and ad platform review. This is the live date for the page. Then ask the designer for a schedule with your deadlines on it, not only theirs: when copy is due from you, when each feedback window opens and closes, and when scope locks and stops changing. A timeline with client deadlines written into it is a timeline someone has actually run before.