The 7-day website build

A small business website takes us about seven days to build, measured from the point the scope is agreed and your photos and copy are in hand. We are Freedom35 Web Design: the build is free, you look at the finished site before paying anything, and keeping it costs $180 to $1,200 a year depending on what it does. This page is the timeline in full — the industry numbers, our seven days, and an honest section on what makes builds run long.

How long does a website normally take?

Longer than most owners expect. These are published figures from agencies describing their own processes, not us guessing at a strawman:

Those agency numbers are not padding, mostly. They cover discovery meetings, mockup rounds, approval cycles, and a queue of other clients. We removed the meetings and the queue rather than the work — more on that below.

The seven days, day by day

No two builds are identical, so treat this as the shape of a typical one rather than a contract. Day zero is the important one.

Why are we fast when agencies take months?

• We never start from a blank page. We maintain our own toolkit — the layout system, the form handling, the booking, payment and account machinery. A new site is assembled from parts that already work, then tailored to you. The agency spending week two rebuilding a contact form has built one before too; they just didn't keep it.
• AI-assisted drafting, human judgement. We use AI tools to draft layouts and code fast, and a human reviews every line and every word before you see any of it. That is the honest description of how the speed happens, so we would rather say it than have you wonder.
• The intake form replaces the meetings. It is deliberately thorough — every question on it is one we would otherwise have to schedule a call to ask. Everything in writing also means no waiting for a slot in anyone's calendar.
• No queue. Your build is the build. Small on purpose has its advantages.

Fast does not mean thin. The seven days include the mobile pass, the speed checks and the proofreading — the sites are live and linkable on our work page, and the most involved of them, a music academy with enrolment, payments and three kinds of dashboard, is described in detail here.

What do you need from me, and when?

Everything on this list, ideally before day zero. It is the same list from how it works:

• A clear description of what you do and who for
• Your logo if you have one — and if you don't, say so, we'll manage
• Photos, if the site should have them. Real ones beat stock every time
• Two or three websites you like the look of, and a word on why
• Someone who can answer a question within a day or two while we build

None of it requires expertise. It requires an afternoon, and doing that afternoon before the build starts is the single biggest thing you can do for your own timeline.

Can it go faster than seven days?

Sometimes. A small site — five pages, good photos, copy that arrived finished — can land in less. We don't promise it, because the days at the end of the table are the ones that protect you: the mobile pass, the testing, the proofreading. A build that skips those to hit an impressive number ships its mistakes to your customers, and "fast but broken" is not a trade we make on your behalf.

The other direction is worth saying too: seven days is the build, not the whole journey. Before it comes the intake form (about ten minutes of your time) and our reply within one business day. After it comes your decision, which takes as long as it takes — the preview link does not expire the moment we send it, and nobody calls you to "check in." Sleep on it properly.

What actually slows builds down?

Honesty section. When a seven-day build takes three weeks, it is almost never the code.

• Waiting on photos and copy. The most common delay by a wide margin, on our builds and every agency's. "I'll get you the photos this weekend" is where timelines go to die.
• Slow answers. A build in motion generates small questions. Each one that waits three days adds three days.
• Decision by committee. One person who can say yes beats four people who can each say maybe.
• Changing the scope mid-build. "While you're in there, could we also…" is fine — we quote it — but it is a new decision, not day five.

Notice what is on that list: things on your side of the table. That is not a complaint, it is the useful information — the half of the timeline you control is the half that varies. Our half is about seven days, reliably, because the process was built to make it so. And since the build is free either way, a slow start costs you nothing but the wait.