{"id":226,"date":"2026-10-12T06:38:19","date_gmt":"2026-10-12T05:38:19","guid":{"rendered":"https:\/\/arrowlancer.ma\/blog\/?p=226"},"modified":"2026-10-12T06:38:19","modified_gmt":"2026-10-12T05:38:19","slug":"website-timeline-morocco-2026-phase-by-phase","status":"publish","type":"post","link":"https:\/\/arrowlancer.ma\/blog\/en\/website-timeline-morocco-2026-phase-by-phase\/","title":{"rendered":"2026 website timeline Morocco: how long a site really takes"},"content":{"rendered":"

On a twelve page brochure site, the day a developer writes the first line of code rarely arrives before week three. Ahead of it sit a scoping workshop, an approved sitemap, a hunt for copy and photos, two or three mockups and at least one round of corrections. That mostly invisible block of work decides whether the site goes live in six weeks or in five months.<\/p>\n

Quotes sent to Moroccan SMEs almost always price the build and almost never the rest. Hence the usual gap between what is announced and what happens: the provider writes “4 to 6 weeks”, the managing director hears “live by end of November”, and launch lands in February because the 180 product pages were never written. Budget is a separate question, covered in our guide to professional website pricing in Morocco<\/a>.<\/p>\n

A brochure or ecommerce project breaks into six phases. Two of them barely depend on your provider, and those are exactly the two that move the launch date.<\/p>\n

The clock starts before the first mockup<\/h2>\n

The signature date and the actual start date are two different things. In between you need a paid deposit, a named contact on the client side, access to the domain name, the logo in vector format, and sometimes the credentials for hosting bought three years ago by someone who has since left the company.<\/p>\n

When nobody has prepared those items, one to two weeks disappear into chasing access. The domain is the worst case: if the .ma was registered by the previous provider under their own account, taking back control means exchanges with the registrar and sometimes a signed request on company letterhead. Start that process on the day you sign, not in launch week.<\/p>\n

One line in the quote frames the whole issue: the schedule starts on the day the deposit, the access credentials and the project owner are all in place. Until that date is written down, every date after it is theoretical.<\/p>\n

Scoping and content: the phase quotes forget to price<\/h2>\n

Scoping a brochure site fits in one to two weeks: objectives, sitemap, page templates, contact journey, acceptance criteria. For a shop, allow two to three weeks, because you have to settle questions with heavy technical consequences: variants and sizes, delivery zones, a shipping grid for Casablanca and other cities, CMI card payment or cash on delivery, returns policy, and whether stock syncs with what you already run.<\/p>\n

\"2026<\/p>\n

Then comes content, and that is where months vanish. A twelve page brochure site needs 4,000 to 6,000 words of useful copy, recent photos of the premises and the team, and client references you actually have permission to name. For ecommerce, do the arithmetic before signing: 200 references, each with a title, an 80 word description, three retouched photos, a weight, dimensions, a price and an opening stock figure. Even at fifteen entries a day, assuming the photos already exist, that is close to three weeks of full time work for someone on your team.<\/p>\n

Two decisions keep this phase from stalling. Name in the quote who produces the copy (you, the provider, an external writer) and the date each batch is due. And accept launching with forty well made product pages instead of waiting for two hundred: a partial catalogue online is working for you, a complete catalogue sitting in a spreadsheet is not.<\/p>\n

Design and sign off: how many rounds, how many weeks<\/h2>\n

Producing mockups takes one to two weeks for a brochure site: home page, one inner page template, the contact page, the mobile views. Ecommerce adds the product page, the filtered listing, the cart and the checkout, so roughly one week more.<\/p>\n

What stretches this phase is not production, it is approval. Each round costs the provider two to three days and the client anywhere from two days to two weeks, depending on who has to say yes. When a mockup circulates by email to five people including a director who is travelling, every round becomes a two week episode. Three rounds later the project has lost six weeks without a line of code written.<\/p>\n

What works in practice: approve the sitemap in writing before anyone designs, cap the number of included rounds (two is reasonable, the third is billable), and run the review as a meeting with the decision maker in the room. A 90 minute session often replaces ten days of email thread.<\/p>\n

Build: three different rhythms depending on what you are making<\/h2>\n

Development is the most predictable phase of the project, which surprises a lot of business owners. The spread comes mainly from the type of site.<\/p>\n