How long should building your small-business website actually take?

The weekend promise versus the month reality

Say a contractor in Putney calls a web designer on a Tuesday. He needs a website and has been meaning to do this for three years. Now he finally has a weekend free. Can they turn it around by Monday?

For a fully custom build, the short answer is no. The longer answer is that anyone who says yes without asking a single real question about your business is selling you a template with your logo swapped in, and you will spend the next two years wondering why the phone never rings from web traffic while your competitor three towns over, whose site actually says what they do and where, books out through June.

Fully custom websites, designed and coded from scratch, take four to eight weeks to build correctly. Not because the work is slow, but because the work is specific. It covers discovery, architecture, copywriting that actually converts and custom design that loads fast. It also covers testing on real devices over real Windham County cell coverage, plus the technical SEO foundation that makes Google pay attention. Every one of those steps requires input, revision, and time to think.

This is not a flaw in the process. It is the process working. The real question is not how fast a site goes up; it is whether you get a site that looks done or a site that works.

What the template builders promise and deliver

Wix, Squarespace, GoDaddy, and a dozen other drag-and-drop platforms all sell the same dream: a professional website in an afternoon, no code required, $12 a month. The marketing shows clean templates, stock photography, and a timeline measured in hours. For a certain kind of business owner, especially one who just needs to check the box that says "I have a website," this sounds perfect.

Here is what you actually get in that weekend build:

A template that looks like a template. The layout is identical to a thousand other sites built on the same theme. Google sees it. Visitors see it. Everyone quietly understands that nobody spent time here, which makes them wonder what other corners you cut.

Placeholder copy you probably never replaced. "Welcome to our site. We are passionate about quality and committed to excellence." Every template ships with this language, and half the people who launch in a weekend leave it there or write something equally generic because they do not know what else to say. The result is a site that could describe any business in any category.

Slow load times. Page builders are slow by design, because they load a massive pile of generic code to handle every possible layout configuration, and your site inherits all of it whether you use it or not. Run a few Wix and Squarespace sites through Google PageSpeed Insights and the mobile scores are often in the 30s or 40s. Google's threshold for "good" is 90. The difference is rankings, conversions, and whether someone on a weak cell connection between Bellows Falls and Westminster waits for your site or backs out.

No local SEO foundation. The platform does not guide you to create separate pages for each town you serve or each service you offer, because it does not understand how local search works. So you end up with one generic "services" page and zero rankings for "plumber Putney" or "electrician Westminster," even though you serve both towns and people search those terms every week.

No support after launch. You are alone with a page builder and a knowledge base. When you want to add a feature or fix something Google Search Console is flagging, you are either learning code or paying someone hourly to wrestle with the platform's limitations.

The weekend site is done fast because nothing in it is custom. It is assembly, not building. And it shows.

What the eight-week custom build actually involves

When a designer tells a prospect that a real custom build takes four to eight weeks, the first reaction is often sticker shock: not at the price, but at the time. Why does it take two months to build a ten-page website?

Because those ten pages are not templates. They are built from scratch, for your business, with every decision optimized for the searches your customers actually run and the conversions you actually need. Here is what happens in those weeks, and why each step matters.

Week one: discovery and strategy (5-8 hours)

A good builder starts by learning your business in detail. Who are your customers? What do they search for when they need you? Which towns do you serve, and which services make you the most margin? What does your competitor's site do well, and where do they leave opportunity on the table? What does success look like in six months: more calls, more bookings, less time explaining the same things?

This is not a formality. The answers shape everything: which pages get built, what those pages say, how navigation is structured, what the site is optimized for. A Brattleboro HVAC contractor who makes most of his margin on heat-pump installs needs a completely different site than one who lives on service calls, even though both are "HVAC contractors." This is also the time to review your current web presence if you have one: what you rank for now, how fast your site loads, what your Google Business Profile says, where the technical gaps are.

The discovery phase is also where you and the builder align on timeline, content responsibility, and what you will need to provide (photos, service details, pricing guidance). A project that starts with a clear shared picture finishes on time. One that starts with assumptions finishes late or wrong.

Weeks two and three: architecture and copywriting (10-15 hours)

This is where the builder decides what pages exist and how they connect. It is also where each page's message gets settled. For a service business covering multiple towns, that typically means:

• A homepage that states, in ten seconds, what you do and where
• A dedicated page for each service you offer (not one generic "services" page, but separate pages for the things people actually search: "heat pump installation," "furnace repair," "ductless mini-splits")
• A dedicated page for each town or region in your service area
• An about page that builds trust with real details, not marketing fluff
• A contact page with one job: make it easy to call or email you right now

Every page is then written, from scratch, in plain language that answers the questions your customers ask. Not SEO word salad. Not corporate vagueposting. Sentences like "We install and service heat pumps in Brattleboro, Putney, and Westminster" instead of "Your trusted partner in home comfort solutions."

This is the step most template sites skip entirely, and it is the step that makes the biggest difference in both search rankings and conversions. Google ranks pages that match searches. A contractor with a dedicated "heat pump installation Brattleboro" page will outrank the one with a generic services page every single time, because Google shows the specific page to the specific search. The copywriting phase is also where the metadata, schema markup, and alt text get written, which help search engines and AI assistants understand what each page is about.

You get drafts at the end of week two. You read them, correct anything that is wrong, and say what is missing. The builder revises. This usually takes two rounds, because the first draft teaches both of you what questions should have been asked in discovery.

Weeks three and four: design and development (12-18 hours)

Once the site's words are settled, the builder designs how it looks and builds it. In a fully custom build that may mean hand-written HTML and CSS rather than a page builder, which is one way to get a site that loads in under two seconds on mobile.

Design starts with a mockup of the homepage: layout, typography, color, how the navigation works, where the phone number lives, how photography is handled. You review it, the designer adjusts, and once the homepage is approved that design system is applied to the rest of the site. The goal is not design awards; it is a site that is fast, accessible, readable on every device, and structured so that the most important thing on every page (call now, book here, see the menu) is unmissable.

Development happens in parallel. In a hand-built site there is no theme overhead and no plugin stack slowing things down. The builder sets up the contact form (two or three fields maximum, because long forms kill conversions), adds schema markup so Google knows what your business is, where you operate, and when you are open, and sets up clean URLs, fast image loading, and a logical internal linking structure that helps both humans and crawlers navigate.

By the end of week four, the site is functionally complete. It does not live on your domain yet, but it exists on a staging server where you can click through it, test it on your phone, and see what your customers will see.

Week five: revision and content finalization (4-6 hours)

You walk the staging site and send everything that needs to change: a heading that is unclear, a service described wrong, a town page that should mention a landmark, a photo that should be swapped. The builder makes the changes and you review again. You repeat that until you are confident the site represents your business accurately.

This is also when you finalize any remaining content the builder is waiting on: final menu pricing, staff bios, testimonials you wanted to add, the last batch of project photos. Some owners provide all of this in week one; others need the staging site to see what is missing. Either way works, but it is why the timeline stretches when content arrives late.

Weeks six through eight: testing, launch, and SEO setup (6-10 hours)

The site gets tested in every browser and device size that can be simulated: Chrome, Safari, Firefox, mobile, tablet, laptop, giant monitor. It goes through accessibility checkers to make sure it works for screen readers. PageSpeed gets tested on real mobile connections to make sure it actually loads fast, not just fast on office fiber. Anything that breaks or lags gets fixed.

Then the domain is configured, the site moves to the live server, and the technical SEO infrastructure most site builders never touch gets set up:

• Google Search Console, so you can see what you rank for and what errors Google finds
• A sitemap that tells search engines which pages exist and how often they change
• Redirects from your old site's URLs if you had one, so you do not lose any search equity
• Canonical tags, Open Graph metadata, and Twitter card markup so your site looks correct when someone shares it
• Google Business Profile integration, review schema, and local business markup

A good builder also sets up analytics so you can see where your traffic comes from, which pages people visit, and which paths lead to contact, and shows you how to update common things yourself (hours, a new photo, a blog post if you are publishing one), so you are not dependent on anyone for every small change.

Finally, someone should watch the first week after launch to catch anything that only shows up under real traffic: a form that does not send on one email provider, a page that looks broken on one specific Android browser, an image that loads slowly under real-world conditions. Most launches are smooth. The ones that are not get fixed quickly when someone is watching.

What you cannot compress without losing something real

The eight-week build is not eight weeks of nonstop work. It is eight weeks of calendar time with built-in space for your feedback, revisions, and the rounds of iteration that turn a good site into a working site. A custom build can be compressed when someone's current site dies or a seasonal deadline demands it, but compression costs something.

If you compress discovery, the builder misses the details that make your business different from the competitor two towns over, and the site ends up generic. If you compress copywriting, the pages say the right general things but miss the specific searches people run. If you compress design, the site works but does not feel like you. If you compress testing, you launch with bugs that cost you conversions until you catch them.

The timeline is not padding. It is the minimum time to do the work right and still leave room for you to stay focused on running your business instead of answering web questions eight hours a day.

Why the timeline is a feature, not a bug

The eight-week build has a hidden advantage the weekend template does not: by the time you launch, the site has been thought through, tested, revised, and refined by two people (you and your builder) over two months. Every page has been read multiple times. Every button has been clicked. Every search term has been considered. The result is not just a site that works on day one, but a site that keeps working, because the foundation is solid.

The template site launches fast and breaks slowly. Six months in, you realize it does not rank for anything. A year in, you notice the contact form was never sending email correctly. Two years in, you accept that the phone never rings from the web and maybe that is just how it is now.

The custom site launches slower and compounds faster. Over the following months, it can start ranking for a few key searches, then for your town name plus your category. Eventually the site becomes your best salesperson, and you forget what it was like to explain the same things on every call because the site did it first. Time and search authority compound.

The question to ask before you choose speed

When someone promises you a site in a weekend, ask this: will it rank for the searches my customers actually run, or will it just exist?

A site that exists is not expensive: $12 a month, a weekend of your time, done. A site that ranks costs more up front and pays back monthly forever, because the searches do not stop. Someone in Westminster is searching for an electrician this week. Someone in Newfane is searching for a weekend inn next month. Someone in Putney is searching for a plow contract in October. The business that owns those searches is the business whose site was built to rank for them, which means separate town pages, separate service pages, fast load times, schema markup, and all the invisible infrastructure the weekend template does not include.

You can launch in a weekend and spend two years invisible, or you can spend eight weeks building it right and spend the next two years answering the phone. The math is not subtle.

What to do if you actually need it fast

Sometimes the timeline is not negotiable. Your old site died, or a competitor just launched and you are losing ground, or you have a seasonal deadline and eight weeks puts you past peak. In those cases, here is the honest path:

Option one: Launch a simple holding page now (one page: your name, what you do, where, phone number, email, hours) and build the real site in parallel. The holding page keeps you visible while the real build happens correctly. It is not a strategy for the long term, but it is better than a template you will regret in six months.

Option two: Compress the build to four weeks by frontloading all your content and feedback. If you can provide final copy, photos, and service details in week one, and commit to reviewing drafts within 24 hours, most builders can tighten the schedule significantly. This requires focus and availability, but it works.

Option three: If you are genuinely in "I need something live tomorrow" territory, use a template for now and budget to rebuild it right in the next slow season. Just go in knowing that the template is a placeholder, not a solution. Plan the replacement before you get comfortable with it. Plenty of businesses launch on Wix or Squarespace and realize it is costing them leads. Then they decide to do it correctly the second time. That path costs more than doing it right the first time, but it is better than staying on the template for five years.

How to tell whether a timeline is honest or padded

Not every web designer or agency needs eight weeks. Some can ship a quality custom site in five or six. Some need ten or twelve because their process includes more rounds of revision or they are juggling many projects. The timeline itself is not the signal; the explanation is.

If someone says "four to eight weeks" and can walk you through what happens in each phase and why it takes that long, that is honest. If someone says "twelve weeks" and cannot explain what happens in weeks seven through twelve, that is padding. If someone says "we will have it done in three days," that is a template with your name on it.

Ask this: "What happens in week three?" A builder who knows will tell you exactly what they are working on and what they need from you. A builder who does not know will give you vague assurances.

Also ask what happens if you are slow to provide feedback or content. A builder who has done this before will tell you that delays on your side push the timeline back one-for-one, and the project is only as fast as the slowest input. A builder who promises the timeline is fixed no matter what is either lying or planning to launch without your input.

The honest timeline for a Windham County small business

Here is a reasonable guide to how long a fully custom build takes, broken down by business size and complexity. These are elapsed calendar weeks, not hours of work. They assume normal feedback speed (you review drafts within a few days, not a few weeks).

Small service business (trades, solo consultant, simple retail): Four to six weeks. Ten to fifteen pages, straightforward service structure, a handful of town pages. Example: a Bellows Falls electrician, a Brattleboro bookkeeper, a Putney dog trainer.

Established multi-service or multi-location business: Six to eight weeks. Twenty to thirty pages, more complex service breakdown, more town pages, possibly some custom functionality like a quote estimator or booking calendar. Example: an HVAC company covering five towns, a law office with three practice areas, a property-management company.

Hospitality, retail with inventory, or anything requiring custom tools: Eight to twelve weeks. The site itself might be straightforward, but integrating a booking system, building a menu or inventory display, or connecting to a POS takes testing time. Example: an inn, a farm store with online ordering, a restaurant with reservation integration.

If your needs are simpler than that, the timeline can be much shorter. Our website for local businesses is built for exactly that case: six pages written for you from what you tell us on a form (home, about, services or menu, the areas you cover, common questions, and contact), built to load quickly on phones with your number one tap away. Your timeline is short: we build the site 24 to 48 hours from payment and it goes live as soon as it is built. We email you the link. Anything you want changed after launch, we change for you, so the fast timeline does not lock you in. It does not include a page per town or per service, so if you need the larger structure described above, a custom build is the better fit.

The price is public, too: $499 a year with everything included (your own domain with hello@ your domain forwarded to your email, hosting, a security certificate, backups, and a login to change any text, price, photo, or phone number yourself). No setup fee and no monthly bill. You should know what you are buying before you spend time on a call.

What those weeks buy you that the template does not

Speed is not the outcome. The outcome is a site that ranks, converts, and compounds. Here is what you actually get from the longer build:

Search visibility. Pages that target the specific searches your customers run, with the technical foundation that makes Google pay attention. The template does not rank because it does not know how.

Speed that matters. A site that loads in under two seconds on mobile, even on weak cell coverage, which means people stay instead of bouncing. The template loads slowly forever because the platform is built for flexibility, not performance.

Copy that converts. Words that answer the visitor's question in ten seconds and make it easy to call or book. The template gives you placeholder text and assumes you will replace it, which most people never do.

Design that fits. A layout and style built for your business and your content, not stretched to fit someone else's template. The difference is subtle in a screenshot and obvious in conversion rate.

A foundation that lasts. Clean code, proper structure, and a site that gets easier to update and extend over time, not harder. The template looks the same in year one and year five because you cannot change what is built into the platform.

Support that continues. When something breaks or you want to add a page or Google changes a ranking factor, you have someone to call who knows how your site is built. The template leaves you with a forum and a knowledge base.

The eight-week build is not eight times better than the one-week template. It is categorically different, because it is built to do a different job. The template's job is to exist. The custom site's job is to earn.

How to decide what your timeline should be

If you need a website tomorrow, you are choosing between a placeholder and a template, and the placeholder is more honest. If you have a month, you can get a simple custom site that covers the basics and leaves room to expand. If you have two months, you can build it right the first time. That means full local SEO and dedicated pages for every service and town, on a foundation that compounds instead of sitting still.

The decision comes down to what you are optimizing for: launch speed or long-term results. Most businesses think they are in a hurry and then leave the site untouched for three years, which means the cost of the extra four weeks was four weeks, and the benefit of doing it right was three years of better rankings and more leads.

If you are not sure where you fall, start by searching for your own services and town names and see what comes up. If a plain, accurate site would close most of the gap, you can start one here. If you need dedicated service and town pages, custom tools, or a booking system, plan for the longer custom build.

The weekend site will always be there if you want it. The question is whether you want to spend the next two years explaining why the phone does not ring, or two months building something that makes it ring.