The reason small business websites take six months or more to go live is rarely that the technical work is genuinely complex; it is that the work has never been broken down into named, sequenced tasks with clear completion criteria. Without that structure, the project becomes an open-ended pursuit of “the website” — a thing that grows in scope as new ideas occur, that hits decision paralysis whenever choices need making, and that drifts indefinitely because no individual day has a clear definition of done. The owner doing the work blames themselves for procrastination; the actual cause is structural. A website with the same scope and quality, broken into thirty named days, can be built and launched in a month by an owner working two to three hours a day, around their existing operations. The compression is not from working harder; it is from working with a plan.

This guide is the plan. It assumes you are starting roughly from zero — no website, or an old one being replaced — and that you are doing the work yourself with the help of an AI website builder for small business owners, a freelancer, or both. The plan is structured around four weeks: the first for foundation and content, the second for build, the third for refinement, and the fourth for launch and promotion. Each day has a defined task with a clear completion criterion, and the cumulative effect is that the website goes live at the end of the month with the basics correct rather than perfect, ready to improve through real customer feedback rather than through endless internal debate. The goal is not perfection; it is launch.

§ 01Week One — Foundation and Content

The first week is content and decisions, deliberately ahead of any building, because content drives design rather than the other way around. Day one is the customer-and-positioning brief: write down, in plain language, who your customer is, what they’re trying to achieve, what they’re afraid of, and how your business helps. This is not market research; it’s articulating what you already know in a way that the website can reference for every subsequent decision. Half a page is enough; the discipline is forcing yourself to write it down concretely rather than holding it loosely in your head where it stays vague and shifting.

Day two is the services audit: list every service or product you offer, with realistic pricing or pricing ranges, the kinds of customers who buy each, and a rough sense of which are higher-margin or strategically important. This list will become the structure of the services area of the site. Day three is the testimonials gather: pull together every piece of social proof you have — emails from happy customers, Google reviews, screenshots of compliments, video testimonials — and organise them in a single document by service. Day four is the imagery audit: identify what you have for photography (real photos of work, real photos of you and your team, real photos of your space), what you’ll need to capture or commission, and what stock photography you might need to fill gaps you can’t fill yourself.

Days five, six, and seven are the writing days. Day five is the homepage and the about page, written as drafts rather than finals — get the words on the page, with the structure from the earlier chapters of this series, and accept that they’ll be refined later. Day six is the service pages, one per service, using the writing structure for service pages that converts. Day seven is the process page and the contact-page structure, plus the FAQ if you’re including one. By the end of week one, you have a content document that contains everything the website will eventually display, written in your voice, ready to be poured into the chosen platform. The temptation to start building before the writing is finished is strong and consistently produces worse outcomes; resist it.

§ 02Week Two — Build

Day eight is the platform decision and account setup. If you’re using an AI website builder, this is where you describe your business to the platform and let it generate the initial site structure. If you’re using WordPress directly with a freelancer, this is where you brief the freelancer with the content document and the structure decisions. If you’re using a drag-and-drop builder, this is where you choose a template that fits the structure rather than fighting one that doesn’t. The objective at the end of day eight is a working site with the seven-page structure scaffolded — every page exists with placeholder content, the navigation works, the basic design is applied — ready to fill in over the next few days.

Days nine and ten are pouring the content into the site, page by page, using the writing from week one. The discipline at this stage is not to start editing the writing as you place it; the writing was approved at the end of week one and changes now will cascade across multiple pages and slow the build. Get the content into place exactly as written; the refinement pass comes later. Day eleven is imagery placement: real photos where you have them, sensible stock photos where you don’t, with sizing and alt-text done properly the first time rather than retrofitted. By the end of day eleven, every page of the site looks roughly like the final version, with real content and real imagery, even if the polish is still to come.

Days twelve, thirteen, and fourteen are operational integrations. Day twelve is the contact form and CRM connection — using the structured-form approach from the follow-up sequence chapter, with auto-acknowledgement configured. Day thirteen is the booking integration if your business takes appointments, or the e-commerce setup if you’re selling products, or the payment processor connection for service businesses that take deposits. Day fourteen is the email-marketing integration with the welcome sequence drafted (full content can be refined in week three) and the signup forms placed across the site. By the end of week two, the website is functionally complete — every page exists, every integration works, every workflow can be tested end-to-end. It is not yet ready to launch, but it is ready to be made ready.

§ 03Week Three — Refinement

The third week is where most launches that drag into six months actually fail, because the refinement work is open-ended without structure and tends to expand to fill any time available. The discipline that prevents this is to enumerate the refinement tasks at the start of the week and stop when they’re done rather than continuing to find more. Day fifteen is the content refinement pass: read every page on the live site, mark the sections that don’t read right, and rewrite only those sections. Resist the urge to rewrite from scratch; targeted improvements produce better outcomes than wholesale replacements at this stage. Day sixteen is the design refinement: go through every page and adjust the specific things that look wrong rather than reconsidering the overall design.

Day seventeen is the mobile pass: open every page on a real mobile phone (not just the desktop browser’s mobile preview, which lies) and fix the things that don’t work properly. This day reliably surfaces issues that are invisible on desktop — text that’s too small, buttons too close together, images that don’t scale, navigation that breaks. Day eighteen is the speed pass: run every key page through Google PageSpeed Insights, address the specific issues it flags (oversized images, render-blocking scripts, missing caching headers), and confirm the metrics are at least in the green for mobile. These three days handle the technical-quality issues that determine whether the site converts; they’re worth the time even when they feel finicky.

Days nineteen, twenty, and twenty-one are SEO foundation, accessibility, and analytics. Day nineteen is the SEO basics: page titles for each page following the structure that local SEO actually rewards, meta descriptions that are written rather than auto-generated, structured data (LocalBusiness schema for service businesses, Product schema for retail), the XML sitemap submitted to Google Search Console, and the Google Business Profile cross-referenced with the website. Day twenty is the accessibility pass: alt text on every image, proper heading hierarchy, sufficient colour contrast, keyboard navigation working, ARIA labels on interactive elements. Day twenty-one is analytics: Google Analytics 4 installed and configured, Microsoft Clarity (or similar) for behaviour analytics, conversion goals set up for the actions that matter (contact form submissions, booking starts, email signups). At the end of week three, the website is ready to launch.

§ 04Week Four — Launch and Promotion

The fourth week is where the website becomes a real business asset rather than a private project, and the work shifts from building to telling. Day twenty-two is the friends-and-trusted-contacts review: send the URL to five to ten people you trust, ask them to use the site as a real customer would, and collect their feedback. The objective is not consensus design changes; it’s catching specific issues — broken links, confusing language, friction in the contact flow — that you can no longer see because you’ve been staring at the site for three weeks. Day twenty-three is fixing the issues that came back, with the discipline of fixing only what’s broken rather than restarting design conversations.

Day twenty-four is the formal launch: domain pointed at the new site, SSL confirmed, redirects from the old site (if any) configured properly, a final round of testing on multiple devices and browsers, and the announcement scheduled for the next day. Day twenty-five is the announcement itself: an email to your existing customer database introducing the new site, a post across your social media channels, an update to your Google Business Profile and other directory listings, and a mention to any partners or referral sources who should know. The objective is not to drive a flood of traffic; it’s to put the existence of the site in front of the people who already know your business so they can use it from now on.

Days twenty-six through thirty are the soft promotion week, with one specific activity per day. Day twenty-six: outreach to three local partners or complementary businesses about cross-promotion. Day twenty-seven: ask three of your best customers for Google reviews using the systematic approach from the reviews chapter. Day twenty-eight: write the first proper blog post or content piece on the new site, demonstrating that the site is a living thing rather than a static brochure. Day twenty-nine: review the analytics from the first week of live traffic, identify the top three issues or opportunities surfaced, and plan the first month of post-launch improvements. Day thirty is rest and reflection: the website is launched, the foundations are sound, and the work shifts from launch to operation. The compounding from this point forward — improving the site week by week, adding content month by month, accumulating reviews and testimonials — is what makes the website increasingly valuable. The launch was the start.

§ 05The Hours-Per-Day Reality

The plan above is achievable in two to three hours per day for an owner doing the work themselves with an AI website builder, somewhat less if working with a freelancer, somewhat more if building from scratch in WordPress without significant prior experience. The hours per day matter because the most common reason 30-day plans fail is that the owner attempts to do them on weekends only, which means the actual elapsed time becomes 90 days minimum and the momentum needed to sustain the discipline never builds. Daily, even modest, beats weekly heroic in this kind of project.

The practical implementation is to block the same two-hour window every day — early morning before operations, late evening after, or whenever your schedule allows — and treat that block as inviolable for the thirty days. Phone notifications off, dedicated working space, the day’s task in front of you. Most owners find that the block becomes habitual after the first week, and the discipline starts running itself. Owners who try to work in stolen ten-minute windows throughout the day rarely finish; the context-switching cost of a complex creative task makes those minutes far less productive than a single dedicated block.

The other reality worth naming is that some days will run over and others under, and the plan absorbs both as long as the daily commitment is genuine. Day twelve might take three hours; day fifteen might take an hour. The cumulative budget is roughly sixty to ninety hours over thirty days, and the named-day structure ensures the work doesn’t sprawl beyond it. If a day is genuinely too short to complete in the allocated time, split it across two days and accept that the launch slides by one. What you should not do is allow accumulated slippage to blur into “we’ll launch when it’s ready” — the structural commitment to a fixed launch date is what produces the launch.

§ 06What’s Deliberately Not in the Plan

Several things people often expect in a launch plan are deliberately omitted from this one because they belong to a different phase of the business’s life. Comprehensive content marketing strategy, with a content calendar mapped out for six months, is not in the plan; one good blog post on day twenty-eight is enough to demonstrate the site is alive, and the broader strategy can develop after launch when you’re seeing real traffic and learning what your audience responds to. Detailed paid advertising campaigns are not in the plan; the foundation that makes paid traffic work — strong landing pages, clear conversion flow, working analytics — is what the plan builds, and the actual ad spend belongs in month two onwards.

Sophisticated email automation beyond the welcome sequence is not in the plan; the sophistication compounds best when applied to a real list of subscribers who came through real signups, which only exists after the site is live for some weeks. Multilingual versions of the site, complex e-commerce taxonomies, custom integrations with industry-specific tools — all of these are valid investments at the right point and are wrong investments to make before the basic site has even launched. The principle that runs through the entire plan is that done-good beats undone-perfect, and the things that make the site genuinely better are mostly things you’ll discover after launch, not things you can predict before it.

The final omission is the most important: the plan does not include the temptation to redesign the site mid-build because something newer or shinier appeared. Templates, design trends, competitor sites, and design articles will all surface during the build phase and tempt you toward partial restarts. The structural answer is to bookmark them for post-launch review and continue with what’s working. Every restart costs a week minimum; three restarts and the 30-day plan has become 90. Hold the line on the original choices through launch, and revisit them deliberately afterwards when you have real data rather than aspirations.

§ 07What to Do When Days Slip

Not every day will go to plan, and the discipline that distinguishes successful launches from drifting ones is how the slippage is handled rather than whether it happens. The first principle is to keep moving even when behind: if day fourteen finishes incomplete, day fifteen still happens on schedule with whatever can be done, and the incomplete pieces of day fourteen carry forward as supplementary tasks. The mistake is letting one slipped day become a day off and then two days off, which becomes a week and then becomes the project drifting into the indefinite future. Daily contact with the work, however small, sustains the momentum that completes the launch.

The second principle is reducing scope rather than extending the timeline. If week three’s refinement tasks are running long, accept a less polished launch rather than a launch deferred. The website can be improved continuously after launch; the commitment to launching cannot be made up after the fact. Choose the simplest acceptable version of each remaining task and ship it. Day twenty’s accessibility pass becomes the basics rather than the comprehensive review; day twenty-one’s analytics setup becomes Google Analytics rather than the full stack. The reduced scope is recoverable post-launch; the missed launch is not.

The third principle is honest assessment of which slippages signal a real plan failure. A day or two over budget is normal; a week behind schedule with no clear path back probably means the plan was wrong for your specific situation, and the honest response is to pause, rewrite the plan with what you’ve learned, and resume rather than pushing through. Most failures are not in the plan; they’re in continuing the wrong plan past the point where it stopped working. Replan rarely, replan honestly, and the launch still happens — just on the schedule the actual work supports.

§ 08The First 90 Days After Launch

Launch is not the end of the project; it’s the start of a different one. The first 90 days after launch are where the website goes from existing to working, and the discipline that produced the launch needs to translate into a different rhythm of continuous improvement. Month one post-launch focuses on iteration based on real behaviour: the analytics show how visitors actually use the site, the contact form data shows what kinds of enquiries are coming in, and the patterns in both surface specific improvements that weren’t visible before launch. Most useful improvements come from this kind of real-world feedback rather than from pre-launch speculation.

Month two adds content and SEO compound. The first proper blog posts, the location pages if you serve multiple areas, the case studies that develop the strongest service pages, and the structural content that targets specific search queries all start producing returns by month two and three. The discipline is committing to a sustainable cadence — one substantive content piece every week or two, not three pieces in a burst followed by silence — because the SEO work compounds with consistency rather than intensity. The same applies to the email list; the welcome sequence runs automatically, but the ongoing newsletter requires the consistent monthly send to build the engagement that converts.

Month three starts producing the first measurable business outcomes attributable to the website: enquiries that came through search, customers who found you via Google Maps, subscribers who joined the email list and converted on a later promotion. These are the metrics that justify the time invested in the launch, and they generally don’t appear in week one or even month one. The patience required for this compounding to start is the most underestimated part of the journey; owners who launched and then lost interest at week three because the site “wasn’t producing results” gave up before the compounding had begun. Stay with the rhythm of consistent improvement and content for ninety days, and the site starts becoming the asset the launch was meant to create.

§ 09How the AI Builder Compresses the Timeline Further

The 30-day plan above is achievable with most modern website-building approaches, but the time-per-day requirement varies sharply based on the tooling. Building a comparable website in raw WordPress without templates or significant prior experience pushes the daily commitment closer to four or five hours, which makes the plan unworkable for owners who already have a business to run. Building with a generic drag-and-drop tool fits the timeline but produces a site with the structural compromises discussed throughout this series — wrong page architecture, weak conversion flow, limited integration depth — that costs more in lost conversion over the years than it saved in launch time.

A purpose-built AI website builder for small business owners compresses the build phase of the plan substantially while preserving the structural quality. Day eight, where the platform takes your business description and generates the initial seven-page structure, replaces what is otherwise the longest section of the timeline. Days nine through eleven, where content and imagery are placed, run faster because the placement structures are already designed for the content rather than the content being shoehorned into a generic template. Days twelve through fourteen, the integrations week, runs faster because the connections to email platforms, booking systems, and payment processors are pre-configured rather than requiring fresh setup work for each.

The economic argument is now familiar from the rest of the series. The 30-day launch plan executed on real WordPress through a custom developer might run £3,000-8,000 for a service business of moderate complexity. The same plan executed through a drag-and-drop builder produces structural compromises that cost more over years than they save up front. The same plan executed through the AI-powered small business website builder at $12.50 a month produces a site on real WordPress, with proper architecture, with integrations in place, on a 30-day timeline that respects the operational reality of running a business while building a website. The plan stays the plan; the tooling makes it executable.