How Long Does Business Website Development Take, and What Drives the Timeline?

The company made valves for the chemical industry and had booked a booth at the most important trade show in its sector, scheduled for April. In January it hired a firm to build its new website with an eight-week timeline, enough on paper to arrive with room to spare. The prototype was approved in the third week, and that is when the waiting began.

The copy for the four product lines depended on three engineers busy with quotes. The plant photos were never taken. The domain was registered to a previous vendor, and regaining access took three weeks of emails. In the sixth week, the CEO saw the website for the first time and asked to change the entire home page.

The trade show arrived and the sales team handed out business cards with the address of the old website, which still showed a catalog with discontinued products. The new website went live two months after the show, when the prospects who had visited the booth had already received proposals from other suppliers.

The timeline depends on scope, ready content, approval speed, integrations and technical access. Once those points are settled, a website with three to six pages goes live in a few weeks.

A timeline without written dependencies ends in a date nobody can meet

When a company asks how long its website will take, it expects a number. The number exists, and it depends on two clocks running at the same time. The first measures the work of the people who design and develop: architecture, prototype, design, programming and testing. The second measures what your company delivers: copy, photos, access, feedback and approvals. A serious proposal accounts for both clocks, and a weak one only promises the first.

That is why two companies that hire the same website can launch it weeks apart. The one that arrives at kickoff with its material gathered and one person who approves moves at the pace of the design team. The one that gathers everything along the way moves at the pace of its slowest response.

The stages of a build and who is responsible for each one

A business website goes through stages that repeat in most projects. First comes discovery, where the team defines what the company sells, who it sells to and what action the visitor is asked to take. Next come the architecture and the prototype, which set the pages and the order of the content. Then each page type is designed, the site is programmed, forms and analytics are connected, and finally everything is reviewed on mobile, tablet and desktop before launch. Every stage has a delivery from the agency and a response from your company. If the response is late, the next stage waits.

Scope sets the baseline of the calendar before the first line of code

The first factor is the real size of the project. A single page for a campaign takes days. A corporate website with one page per service, another per industry and a contact section is measured in weeks. A project with an extensive catalog, a private portal or several languages for different markets needs its own calendar, because each new feature adds design, programming and testing.

Pages, templates and languages

The number of pages matters less than the number of distinct templates. Ten product pages with the same structure share a single design and are then filled with content. Five pages with different structures require five designs, five reviews and five approvals. Each additional language adds translation, a review of technical terms and the setup search engines need to show the right version to each visitor.

Features that require custom development

A quote calculator, a product search with filters, a portal with a username and password or an online store go beyond informational pages. Each one needs business rules, testing with real data and, often, a connection to another company system. If your project includes one of them, it makes sense to move it to a later stage or ask for a specific calendar for it, because it is the part of the website that accumulates the most adjustments.

Content that arrives late moves the entire calendar

In the projects we review, the most frequent delay shows up in the material. The design of a page depends on how many services the company has, how long each text is and which photos exist. If the content arrives after the design, the design gets adjusted, reviewed again and approved again. It pays to gather the information you need before design up front; here we focus on how it affects the timeline.

Writing from scratch and technical validation

When the agency writes the copy, your team is still essential. Someone has to confirm capabilities, standards, materials and lead times, because a wrong technical detail on the website goes straight to a buyer's desk. That validation usually falls on engineers or managers with full calendars. If it is not assigned to anyone with a date, each page sits in an inbox while the calendar moves on.

Approvals stretch the project when nobody has the final say

The third factor is decision speed. A prototype that waits a week for feedback delays everything that follows by a week. The problem grows when several departments weigh in and none of them has the final decision, because each comment opens an internal conversation before it reaches the agency.

Approval committees and late changes of direction

The most expensive case is the executive who sees the project for the first time when it is already programmed. A change to the home page at that point forces the team back to design, to redo the programming of that page and to repeat the tests. To avoid it, everyone with a vote should review the prototype, which is the stage where a change costs hours of work instead of weeks.

Review rounds agreed on in the proposal

Every project should state how many review rounds it includes and how much time your team has to respond in each one. A well-used round gathers in a single document the comments from every department, already reconciled among them. Additional rounds are possible, and each one adds days to the calendar and, in many cases, a cost.

Integrations and access: the delays that appear in the final week

The fourth and fifth factors show up at the end, just when the website looks finished. A form that has to send every prospect to the customer relationship management system (CRM), analytics that have to record conversions or a domain that has to point to the new server all depend on access many companies do not have at hand.

Domain, DNS and corporate email

To launch, someone has to modify the domain settings, known as DNS (domain name system). The domain is often registered to a previous vendor or to an employee who has left the company, and regaining access can take weeks. In addition, a bad DNS change can leave the entire company without email. That is why it pays to locate those credentials on kickoff day, while there is still room in the schedule.

Connecting the CRM and analytics

Connecting the website to the CRM requires a user with permissions, the list of fields sales needs and tests with real requests. Analytics requires access to the current analytics tool to keep the visit history. If the new website replaces one with traffic, you also need a redirect plan. Each of these steps is short when the access exists and becomes long when someone has to track it down.

How to calculate a realistic timeline for your company's website

Before you accept a date, review these points with your team:

• Count the pages and, above all, how many distinct templates they need.

• Flag the features that require custom development and decide whether they belong in the first stage.

• Define who writes, who validates the technical data and how quickly each one responds.

• Name a single person with the final say and ask the whole committee to see the prototype.

• Locate access to the domain, the CRM and analytics before kickoff.

• Work backward from the date that matters, such as a trade show or a launch, and leave room for testing.

If the date that matters falls before the resulting timeline, it makes sense to trim the scope of the first stage and keep the testing time intact. A website with fewer pages and everything working serves your sales team better than a complete one with forms that fail.

At Artisma we work with timelines in business days that you know from day one. The Landing package, a single page, is delivered in 7 business days; the Essential, with three pages, in 14; and the Enterprise, with six pages, in 21. Before you pay the deposit you review a prototype of your website, and at kickoff we confirm access and schedule the reviews. If your date is close, the express option delivers in half the time for an additional fee, as long as your material is complete and you respond within 24 hours. Projects with custom features get a quote with their own calendar.

Frequently Asked Questions

What should I do if my website has to be ready by a fixed date?

Work backward from that date and separate what is essential from what is nice to have. Launch first the pages your prospects will check, such as home, services and contact, and leave the full catalog or the blog for a second stage. From day one, secure the technical access and one person who approves within 48 hours.

Why does a project fall behind if the agency meets its deadlines?

Because part of the calendar depends on your company. While a prototype waits for feedback, a text waits for validation or a credential is still missing, the project stops even if the design team is available. That is why the proposal should state what your company delivers at each stage and within how many days.

Does it make sense to launch the website in stages?

Yes, when there is a close date or complex features. A first stage with the main pages lets you start receiving prospects, and the features that require custom development are added later with more testing time. The condition is to plan the complete structure from the start, so each stage adds pages without rebuilding the ones that already exist.

If your company needs its website for a trade show, a launch or the start of a campaign, the timeline is decided in the first weeks: in the scope, in the material and in who approves. Schedule a 15-minute call and we will tell you which package fits your project and in how many business days you would have it live.