Home/Blog/How Long Does It Take to Build a Website? Realistic Timelines for 2026

// WEB DESIGN

How Long Does It Take to Build a Website?

A small business site usually takes four to eight weeks. An online store can take up to three and a half months. Here's where that time goes, what makes projects run late, and what you can do on your side to launch sooner.

How Long Does It Take to Build a Website? Realistic Timelines for 2026

When a website project runs late, the code is almost never the reason. The texts for the services page haven't been written. The photos are still on the owner's phone. A feedback round that should have taken three days took three weeks because two managers were on holiday. So when someone asks how long does it take to build a website, the honest answer has two parts: how long the studio needs, and how long the business needs.

Timelines published online swing wildly. Website builder companies talk about hours. Agency guides talk about months. Both are right about their own product, and neither helps much if you run a clinic in Sofia or a shop in Varna and want to know whether the new site will be live before your busy season starts.

This guide gives realistic ranges for each kind of site, shows where the weeks actually go, and lists the things on your side of the table that make a project faster. If budget is the bigger question for you, start with our breakdown of how much a website costs in Bulgaria.

The short answer: timelines by type of site

These ranges assume a professional build with a clear brief and content that arrives roughly on time. They run from the day work starts to the day the site goes live, not from your first enquiry.

  • A one-page site or landing page: one to three weeks. There is little structure to agree, one screen to design and usually one form to connect.
  • A small business site with five to fifteen pages: four to eight weeks. Most service businesses, clinics, restaurants and consultancies land here.
  • An online store: eight to fourteen weeks. Catalogue size, payment and courier integrations, and how many products still need photos and descriptions decide where you fall. Our e-commerce builds start at the short end when the catalogue is already in a spreadsheet.
  • A custom web app or portal with logins and dashboards: three to five months, sometimes more. Planning and testing take a much bigger share of the calendar.
  • A template or website builder site you make yourself: a weekend to a few weeks, depending mostly on how many evenings you can give it.

Our own projects follow the same pattern. On our pricing page we quote four to eight weeks from kickoff to launch for a marketing site, eight to fourteen weeks for an online store and twelve to twenty weeks for a web app with custom dashboards. Those figures hold when the content is ready. When it isn't, the calendar stretches, whoever is doing the build.

Where the weeks actually go

Every serious website build moves through the same stages. Studios name them differently, but the order rarely changes.

Discovery and planning: a few days to two weeks

Someone has to agree what the site is for, who it talks to and what a visitor should do on each page. The output is a sitemap, a feature list and a rough content plan. Skipping this step feels like saving a week. It often costs three later, when half-built pages turn out to be the wrong pages.

Design: one to three weeks

The designer turns the plan into real screens, usually the home page first and then the main inner pages, on desktop and mobile. Most of this time goes on feedback rather than drawing. One round of clear, combined comments moves a project forward. Four rounds of comments from four different people send it in circles.

Content: alongside design, and often late

Texts, photos, prices, team bios, legal pages and, for many Bulgarian businesses, a full English version too. This is the stage owners underestimate most, because writing about your own business is harder than it looks. A developer can build a page in an afternoon. Agreeing what that page should say can take a team a fortnight.

Development: two to six weeks

The approved design becomes a working site. Pages get built, the CMS is set up so your team can edit without calling anyone, and forms, booking tools, payments or a CRM get connected. Each integration adds time, because each one comes with its own account to open, API keys to request and odd cases to test.

Testing and launch: one to two weeks

The site gets checked on real phones and browsers, forms are tested from start to finish, pages are tuned for speed, and redirects from the old site are put in place so existing Google rankings aren't thrown away. Then the domain is pointed at the new site. Launch day is usually quiet. The week before it rarely is.

A realistic six-week plan for a small business site

Here's how a typical ten-page site for a service business fits into six weeks when both sides keep to their dates. Use it as a template for your own planning. It is not a guarantee.

  • Week 1: kickoff meeting. Goals, sitemap and content plan agreed. You start writing texts and book a photographer if you need one.
  • Week 2: home page design presented on desktop and mobile. You send one set of combined comments within two working days.
  • Week 3: inner page designs approved. Final texts for the main pages arrive. Development starts on everything that's signed off.
  • Week 4: the site takes shape on a private preview link. Forms, maps, booking or CRM connections go in. You review pages as they're finished instead of all at once at the end.
  • Week 5: remaining content goes in, plus the English version if you have one. Speed and mobile testing. Redirects from the old site mapped out.
  • Week 6: final review and fixes. The domain switches over and the sitemap goes to Google Search Console. Your team gets a short walkthrough of how to edit the site.

Count how many of those weeks have a task in your column. If the texts miss week three, weeks four and five move with them. Nobody is being difficult when that happens. Development simply can't finish pages that have nothing to say yet.

What slows most website projects down

Late projects rarely have one big disaster behind them. They have a string of small waits. These are the ones we run into most often:

  • Missing content. The design is approved and development is ready to start, but the service descriptions don't exist yet. In our experience this one gap adds more weeks than everything else on this list put together.
  • Slow or scattered feedback. A designer can act on comments the same day. If it takes a week to collect comments from three managers, every design round costs a week.
  • Late sign-off from the top. The marketing lead approves the design, then the owner sees it for the first time at the end and wants something different. The project goes back to the start.
  • Scope creep. "While we're at it, could we add a blog, a client portal and online booking?" Each idea is reasonable. Together they turn a five-week project into a three-month one.
  • A second language added late. Many Bulgarian businesses decide halfway through that the site needs English as well. Translation itself is quick. Checking every page, menu, form message and legal text in both languages is not, and it lands just when everyone expected to be testing.
  • Outside parties. Payment providers need to verify the business, couriers want a signed contract before they issue API access, and whoever controls the old domain has to hand it over. None of this moves fast, and none of it is in the studio's hands.
  • Legal pages. The privacy policy, cookie consent and terms get left until the last week, then someone realises a lawyer should read them first.

Online stores have one more item to plan for. Since June 2025, e-commerce services in the EU fall under the European Accessibility Act, with an exemption for microenterprises. If your shop is in scope, building accessible forms, colour contrast and keyboard navigation in from the first design is much quicker than retrofitting them after launch.

Builder, template or custom: how the route changes the clock

The tool you pick sets how fast you can launch. It also sets how far the site can grow before you have to start again.

  • Website builders such as Wix or Squarespace are the quickest start. You choose a template, swap in your text and photos and connect a domain. A simple site can be live within days. The cost shows up later, when you want something the template wasn't made for.
  • A WordPress theme set up by a freelancer or studio usually takes one to three weeks. Most of that time goes on content and bending the theme to fit it.
  • A custom-designed site takes longer up front, typically four to eight weeks for a business site, because the design is made for your content instead of borrowed. You get that time back in page speed, fewer plugins to update and a site that doesn't look like thousands of others.

If the platform question is still open for you, our comparison of Next.js and WordPress for business websites goes into it properly. On timeline alone, our rule of thumb is simple: the quickest route to launch is often the slowest route to the site you actually wanted.

How to launch sooner without cutting corners

Pushing a studio to design faster doesn't work very well. Removing the waits on your side almost always helps. Before the project starts, or in its first week:

  • Name one person who gives feedback and makes decisions, and make sure they actually have the authority to decide.
  • Write the texts for your five most important pages first. Rough drafts are fine, because an editor can polish a draft. Nobody can polish a blank page.
  • Collect real photos early. If you need a shoot, book it now instead of after the design is approved.
  • Put every login in one place: domain registrar, hosting, Google Business Profile, Google Analytics, social accounts and your payment provider.
  • Split the wishlist into "launch" and "later". A blog or a booking system can go live a month after the main site, and your visitors won't notice.
  • Agree the dates for feedback rounds at the start, the same way you'd agree a delivery date.

You also don't need the whole company to test the site before it goes live. Nielsen Norman Group's usability research found that testing with five users uncovers about 85% of usability problems. Five colleagues or loyal customers clicking through the preview on their own phones will catch most of what matters, in a day rather than a fortnight.

Our small business website checklist lists what to have ready before launch, in the order you'll need it.

Launch isn't the finish line

A site that goes live on Monday won't necessarily show up in Google on Tuesday. Google's own documentation says crawling can take anywhere from a few days to a few weeks. Submitting a sitemap in Search Console helps Google find your pages, but it doesn't promise a date.

Ranking takes longer again. A new page competes with sites that have been collecting links and reviews for years, so give organic traffic a few months before you judge it. Plan the launch around that. If you need enquiries in June, going live at the end of May leaves you very little room.

It also helps to agree before launch who looks after the site afterwards. Updates, backups and small content changes don't stop once the site is live, and deciding who owns them in week six is far easier than scrambling for someone when the first plugin warning or broken form appears.

The first weeks after launch also bring small fixes: a form that sends to the wrong inbox, a page that looks odd on an older phone, a price that changed last week. Leave a little time for these instead of treating launch day as the end of the project.

The verdict

For most Bulgarian small businesses, a well-run website project takes four to eight weeks from kickoff to launch, and an online store takes eight to fourteen weeks. If someone promises a custom site in a few days, expect a template with your logo on it. If someone quotes six months for a ten-page brochure site, ask what the extra time is for.

The biggest lever on the timeline sits with you, not the studio. Have your content, one decision-maker and your logins ready before work begins, and most projects land close to the date everyone agreed. Treat the build as a joint schedule with tasks on both sides, and you'll rarely be the business still waiting for its website when the season starts.

Frequently asked questions

How long does it take to build a simple website?

A one-page or small brochure site takes one to three weeks with a professional studio. On a website builder you can do it yourself over a weekend. Either way, the deciding factor is usually whether the texts and photos are ready when work starts.

How long does it take to build an online store?

Usually between eight and fourteen weeks. A shop with a few dozen products and standard card payments sits at the short end. Hundreds of products, courier integrations with Econt or Speedy, and links to invoicing or stock software push it towards the long end.

Can a website be built in a week?

Yes, if it's small, based on a template and every piece of content already exists. A custom design in a week is rarely realistic. Design needs at least one proper feedback round, and useful feedback takes more than a day or two to gather.

How many hours does it take to build a website?

There's no fixed number, because a landing page and a web app are different jobs. For a small custom business site, design and development together usually run to dozens of hours rather than hundreds, spread across several weeks. The calendar is longer than the working hours because of feedback rounds, content and waiting on outside parties.

Does a website redesign take less time than a new site?

Not always. The structure and much of the content already exist, which helps. But moving that content, setting up redirects so you keep your Google rankings and untangling old plugins can cancel out the head start. Plan for roughly the same timeline as a new site of the same size.

Does a bilingual site take longer to build?

A little, if you plan it from the start. The design and structure are shared, so the extra work is mostly translation, checking and a language switcher. Budget roughly an extra week for a small business site. Adding the second language after launch usually takes longer, because pages, URLs and forms have to be revisited one by one.

Is it faster to build a website with AI?

AI website builders can produce a first draft in minutes, which is useful for testing an idea. The draft still needs your real texts, photos, prices and contact details, and someone has to check that it reads well and works on a phone. AI shortens the first hour of the project. It does little for the weeks spent on content and decisions.

What should I prepare before a website project starts?

A short brief with your goals and audience, texts for your main pages, real photos, your logo files, and logins for your domain and hosting. Name one person who approves design and content. Those few things remove most of the delays described in this guide.

When will my new website show up on Google?

Google says crawling can take from a few days to a few weeks. Submitting a sitemap in Search Console speeds up discovery. Ranking well for competitive searches takes longer, often months, and depends far more on your content and links than on your launch date.

Need your site live by a specific date?

Tell us your deadline and what the site needs to do. We'll tell you honestly whether the date is realistic, what to prepare first and what can safely wait until after launch.

Get a timeline →