Building a website takes anywhere from an afternoon to several months. An agency project usually runs weeks to months, a template builder takes days of your own time and an AI builder can produce a live first version in one chat session. In every route, content, decisions and review take longer than the build itself.
- The route sets the range: weeks to months with an agency or freelancer, days of your own time with a template builder, a first live version in one session with an AI builder.
- Writing content, making decisions and reviewing drafts take longer than building in every route.
- Third parties keep their own clocks: payment account checks, email DNS records and domain verification all add calendar time.
- Google says crawling a new page can take from a few days to a few weeks, so plan launch announcements accordingly.
- Speed becomes risky when nobody tests forms, payments and the mobile layout before launch.
The short answer, by route
Three routes cover almost every small business and founder project:
- Agency or freelancer
- Weeks for a small brochure site, months for anything with bookings, payments or logins. You spend little time building and a lot of time briefing, reviewing and waiting between phases.
- Template builder
- Days of your own evenings for a small site. Fast to start, slower to finish, because you fit your content into someone else's layout.
- AI builder
- A live first version in one chat session, then rounds of changes in the same chat. The build is short; your review and setup decide the launch date.
Can you really build a website in one day? Yes, for a one-page or small site, if four things are true before you start: the text is written, the photos are chosen, one person approves, and the site doesn't take payments, or your payment account is already verified. A live link the same day is realistic. Your own domain and Google visibility follow on their own schedules, covered below.
What takes the time: content, decisions, reviews, integrations
Ask anyone who has shipped a few sites where the weeks went, and the build itself is rarely the answer. Four things eat the calendar:
- Content. Page copy, product details, team bios, photos. It's the most common reason a finished design sits empty. Nobody else can write your prices, hours and promises for you.
- Decisions. Every extra person with a veto adds a review round. Two partners who disagree about the homepage can add more time than the whole build.
- Reviews. Each round of feedback costs scheduling time with an agency, and a fresh build with an AI builder. A single consolidated feedback list per round beats a stream of messages.
- Integrations. Payment accounts need business verification, email needs DNS records, domains need verification. These run on other companies' clocks.
Replacing an existing site adds one more job: moving old content and keeping old page addresses working. Every URL that already ranks or sits in someone's bookmarks should redirect to its new home, so list your current pages before the new site goes live.
Why do agency websites take so long? Mostly handoffs. A project moves from brief to copy to design to development to review, and each handoff waits for someone: a client approval, a designer's free slot, an invoice. The agency is also running several clients at once. None of this is bad faith; it's how a phased service works.
Agency or freelancer timelines, phase by phase
A typical agency project runs through these phases, roughly in order:
- Discovery and brief: goals, audience, page list, scope and budget.
- Content plan: who writes what, and by when. Often the first deadline to slip.
- Design: mockups for the key pages, usually with a fixed number of revision rounds.
- Development: building templates, forms, integrations and the content management setup.
- Content entry: loading final copy and images, which exposes every page where the copy doesn't fit the design.
- Review and testing: rounds of fixes across browsers and phones.
- Launch: domain and DNS changes, analytics, redirects from any old site.
Custom web apps add a heavier front end. Research alone is planned in weeks: the UK government's Service Manual says of the discovery phase that "there's no set time period for a discovery, but around 4 to 8 weeks is typical" (GOV.UK Service Manual). That guidance is for public services, but the pattern holds for any bespoke build: understanding the problem comes before writing code.
To shorten an agency timeline, deliver final content before design starts, name one approver, and put the launch date and the number of revision rounds in the contract. For what those weeks cost, see the cost to build a web app.
Template-builder timelines
A template builder gets you to a good-looking page quickly. The time goes elsewhere:
- Choosing a template, which can take longer than it should because every demo looks finished.
- Replacing demo content and discovering that your text is longer, your photos are a different shape and your services don't fit three neat columns.
- Adding functions such as bookings, payments or member areas through add-ons, each with its own settings and limits. If an add-on doesn't match your rules, the project stalls.
- Mobile and SEO settings page by page.
Expect days of your own time for a small site, spread over evenings. The risk isn't the first week; it's the half-finished site that sits for a month because one feature won't work the way you need.
AI-builder timelines: what happens during a WisyLink build
With WisyLink, the sequence is short and visible:
- You describe the site in one chat message, on the web or in the iOS or Android app, and can attach reference files such as your logo, photos, a menu PDF or a product spreadsheet.
- Wisy, the chat assistant, either asks one short question or starts the build. It decides the details it sensibly can itself.
- The build runs while a live task list shows what's being made, with a Stop button if you change your mind. On a first build, the address shows a "building" page until it's done, and the mobile app notifies you when it finishes.
- The site goes live at its own
https://<id>.wisylink.comaddress, with a final note naming anything you still need to set up, such as Stripe or email settings under Integrations. - You change it by chatting. Each change is a new build; a failed build leaves the previous version live. New records such as products or posts appear within about a minute, with no rebuild.
How long a build takes depends on scope, and a one-page site and a client portal are different jobs; we don't publish a fixed number. Your plan sets the pace between builds. The free Community plan gives one build per 5-hour window and keeps each build to a lean first version. Paid plans, from $7 a month, add fuller builds, shorter waits between builds and several apps building at once.
A worked example shows where the hours go. A bakery owner on the Starter plan, with copy, prices and photos ready, describes a five-page site with a menu and a contact form in the morning, reviews the live link on her phone at lunch, and sends one message listing every change. The second build applies them all. In the afternoon she connects her domain and starts verification. The next morning she submits the sitemap in Google Search Console and posts the link. The builds were the short part; reading, deciding and setting up took the day.
The calendar after the build is the same as in any route: your review, test orders, payment verification and your domain. Connecting a domain works on any plan; once you start verification, WisyLink keeps retrying automatically for up to six hours and issues the HTTPS certificate itself as soon as the domain verifies. The full walkthrough is in how to connect a custom domain, and the end-to-end process in how to build a website with AI.
Typical timelines by site type
| Site type | Agency or freelancer | Template builder | AI builder |
|---|---|---|---|
| One-page site | Days to a couple of weeks | An afternoon to a weekend | Same day |
| Small business site | Several weeks | Several days of your own time | First version same day; launch-ready in days |
| Booking site | Several weeks to a few months | Days, if a booking add-on fits your rules | First version same day; days to test rules, emails and payments |
| Small store | Several weeks to a few months | Days to weeks, mostly product data | First version same day; product data, Stripe setup and test orders take days |
| Client portal or web app | Months, often starting with weeks of discovery | Rarely possible without add-ons or custom code | First version same day; weeks of iteration with real users |
Read these as planning bands derived from the phases above, not as measured averages; we know of no neutral study that compares website timelines across routes. Two patterns hold across every row: the AI route compresses the build, not your decisions, and the more a site handles money or logins, the more of its timeline is testing. If your site is really a product test, our MVP playbook explains how to scope it into a short test loop.
Ten things to prepare so you launch faster
- A one-sentence goal and the one action you want visitors to take: call, book, buy or sign up.
- A page list for launch day only. Extra pages can come next month.
- Final copy for every page, including prices, hours, service areas and guarantees.
- Logo and photos at web size, with the right to use them.
- Business facts in one place: legal name, address, phone, email, social links.
- One decision-maker, with authority to approve the final version.
- Two or three reference sites you like, with a note on what you like about each.
- Third-party accounts ready: a verified Stripe account if you sell, an email provider for sending, and the login for wherever your domain is registered.
- Legal pages drafted: privacy policy at minimum, plus terms and a returns policy if you sell.
- A test script: every form, booking and payment path, to click through on a phone and a laptop before launch.
When "fast" becomes risky
A same-day site is fine. A same-day site that nobody tested is not. The risks worth slowing down for:
- Untested money paths. Run payments with test keys, then one real purchase and refund, before you announce anything.
- Unchecked facts. AI can produce inaccurate content, and WisyLink's terms make you responsible for reviewing it. Check every price, hour and claim.
- Email that stops on launch day. Delegating a domain's nameservers to WisyLink replaces all its DNS records, including the MX records that deliver your email. Recreate them in WisyLink's DNS manager first, or connect the domain with a single record instead, which leaves email untouched.
- A free link on printed material. Free WisyLink links stay live for 30 days, then spend a week marked for deletion before they are deleted. Don't print a free address on flyers.
- Keys in the wrong place. Payment and email credentials go under Integrations, never into the chat.
- No copy of your data. Ask for a CSV export of bookings, orders or sign-ups, and download it regularly.
How long until Google shows the site? Google's documentation on asking Google to recrawl says crawling can take anywhere from a few days to a few weeks. Every WisyLink site serves its own sitemap; submit it in Google Search Console once your domain is connected. More in SEO for AI-built websites.
Get a live first version today
Work through the ten-item list, then describe your site in one message and review the live result the same day. Compare plans when you want the site to stay live on your own domain, and see the capabilities to check what your site can include.
Describe it in one message and get a live link: start free on Community, no card required.
F.A.Q.