"How soon can we launch?" is usually the second question on a first call. Code is rarely the bottleneck. Content, feedback and third-party approvals are.
These ranges come from our own projects, not a sales deck.
Typical timelines
- Five-page marketing site: four to six weeks from kickoff, assuming copy and photos arrive on schedule.
- Ten to fifteen pages with a CMS: six to eight weeks.
- Online store with 100 to 300 products: eight to twelve weeks, including product data and test orders.
- Custom software or SaaS first release: six to eight weeks to something usable, then two-week milestones.
The delay that affects almost every project
Waiting on final text and photography costs more launch days than design and development combined. Writing plainly about your own business is hard when you are also running it, and it is easy to keep postponing.
The fix is unglamorous: assign each page to one person, set a date for a rough draft, and review real copy inside the layout rather than in a document. Rough copy in place beats perfect copy in a drawer.
Where integrations add time
Payment provider verification, POS exports, booking systems and accounting software all involve another company’s process. Merchant accounts can take a week to approve; a POS vendor may take three days to answer an email. Build that into the plan rather than discovering it in week six.
Bilingual launches add a translation round, and translation usually needs approved English copy first. Sequence it rather than running both at once.
Phasing a fixed date
If you have a hard date, split the work. Launch the essential pages, mobile layout and enquiry path first; add the blog, secondary services or deeper integrations a month later. A smaller site that is live and correct beats a complete site that misses the season.
Whatever the plan, keep a week for testing at the end. The last-minute rush is how broken forms and mistyped phone numbers get published.