a website in 7 days: what can actually be delivered

business · 2026-11-01 · 4 min

seven days is the deadline almost everyone asks for. sometimes it is real, usually it is a hopeful number copied from an ai builder ad. i build websites in parma, and i have delivered small sites in a week. i have also watched a week become two months for reasons that had nothing to do with code.

here is the honest version: what one week can produce, what it cannot, and what has to be true before the clock starts.

what one week is actually enough for

one week is enough for a single page, or a three-page site, when the content is ready, the decision maker is one person, and nothing has to connect to anything else.

• a landing page for one service, with a form and a booking link
• a short professional site: home, services, about, contact
• a rebuild of an existing one-page site with better copy and performance
• a page for a launch or a campaign, measured with analytics

that is not a consolation prize. for a professional with one clear offer, a fast one-page site with a real call to action outperforms six pages nobody reads.

the seven days, honestly

day 1 - a 30-minute call, then a written scope: pages, what the visitor must do, what i need from you. no design yet.

day 2 - structure and copy. you send the text, or we agree that i write it and you review. photos, logo and any existing material arrive today, not on day five.

day 3 - design direction: one page, real content, desktop and mobile. you approve or list changes once.

day 4-5 - build. the same content becomes code, with metadata, form, analytics and a booking link.

day 6 - review and fixes. one consolidated round, not a conversation spread over three days.

day 7 - tests, deploy, credentials, a short training call. done.

notice where the week goes: three of the seven days are content and decisions, not code. that is why the deadline is about you as much as about me.

what breaks the week

content arrives late. a professional photographer takes longer than a site build. placeholder text produces a placeholder site.

feedback arrives from four people. a committee reviews in rounds. one owner, one list, one round.

a hidden integration appears. payments, a crm, a newsletter, a booking system, a multilingual migration. each one is a small project inside the week.

if any of those is true, the honest answer is two to four weeks, not seven days. a week that ignores them is a week that ships something broken.

what it costs

a one-page site in a week is not cheaper because it is fast. speed comes from decisions being made, not from cutting phases. what you save is calendar time, and what you risk is paying for a second round later.

expect a fixed price for the scope, a deposit, and a clear list of what is not included: photography, domain and hosting, advertising, ongoing seo. the same rule as any project, compressed.

when to say no

say no to a week when the site is a shop, when the brand is still undecided, when content has to be written by someone who has not been hired yet, or when the brief is "something modern" and nothing else.

a good builder refuses those seven days, because accepting them means delivering the problem later, at your expense.

is a week enough for an e-commerce site?

no. a shop needs catalogue structure, shipping rules, taxes, payments, returns and a test order that actually completes. two to six weeks is realistic for a small catalogue with ready product data.

can i write the content myself during the week?

yes, if it is ready by day two. writing in parallel with the build is the most common cause of a one-week project becoming a three-week project.

what if i need changes after launch?

they are a separate, quoted piece of work unless the scope included a post-launch window. the handover includes the credentials, so you are never blocked.

if you want to know whether your project fits in seven days, book a 30-minute call. bring the pages you think you need and the date you need them by. i will tell you which of the two is unrealistic. for the wider timeline, see how long it takes to build a website and who can build it.