Site development timelines: what they actually depend on

The question "how long does a site take" expects a number. An honest number without a scope is a guess. A landing with ready texts and one form lives in different weeks than a store with payment, delivery and an export into an accounting system. Below is not a price list and not a promise of a date. It is what usually moves the date.

What lengthens the calendar

• Texts and photos that do not exist on day one. A mockup without them is approved blind, then redone.
• The number of people who say "this needs a change". One acceptor is faster than three rounds of approval.
• Integrations: CRM, payment, delivery, accounting. Each adds not a screen but someone else's calendar.
• An account area and roles. That is already a product, even if the conversation calls it "a couple of pages".
• Fixes after ads start. Better to budget them than to treat them as a surprise.

A short landing can be assembled quickly if the offer, the contacts and the examples are already on the table. A corporate site gets stuck on structure and texts. A store gets stuck on products, price rules and who confirms an order. Until that is named, any figure in a proposal is decorative.

Lexora names a timeline after the scope, not before it. If you need to hit a campaign date, we will say which volume fits that date and what has to be cut.