A useful project calendar makes decisions visible. The design and code are only part of the work: someone also has to provide the text, photos, prices, account access and approvals. Set an owner and a due date for each before the build begins.
A practical sequence
Before week one: confirm the goal, pages, languages, integrations, budget and launch date. Collect domain and hosting access, logos, photos, product or room data, and the person who can approve the work.
Week one: agree on the page map and content. Review a homepage direction and the key customer journey. Do not polish every page before the structure and call to action are settled.
Week two: build the agreed pages, connect the forms and test on phones. For an e-shop, enter sample products and test shipping, tax settings and checkout with the relevant providers. For a booking site, test availability, confirmation messages and cancellation steps.
Before launch: review every page, replace sample content, check links and forms, confirm analytics and privacy choices, and test redirects if URLs change. Keep a launch owner available to approve the final checklist.
Treat dates as a plan, not a promise
JupiWeb’s quote calculator currently estimates roughly 14 working days for a business website, 25 for an e-shop and 35 for a booking system. These are based on the selected project scope and assume decisions and materials arrive on time. The timeline grows when pages, languages or integrations are added. The season launch planner helps work back from an opening date; add your own buffer for approvals, payment-provider setup and seasonal workload.
Ask for milestones in writing: scope sign-off, content ready, design approval, review site, final testing and launch. If one slips, decide together what moves rather than quietly compressing testing.