![\"WordPress,](\"https:\/\/storage.googleapis.com\/arrowlancer-prod.firebasestorage.app\/blog-ma\/wordpress-webflow-sur-mesure-site-vitrine-maroc-2026\/1.jpg\")
<\/p>\nBefore you ask for three quotes, there is a better question than “WordPress or Webflow?”: who is going to edit this site eighteen months from now, and on what annual budget?<\/p>\n
Most Moroccan managers who call us already have a platform in mind, usually recommended by an agency or by a peer who is happy with theirs. All three can produce a perfectly good brochure site, so the technology argument is mostly a dead end. What actually separates them is the recurring cost they commit you to, whether someone on your team can change a page without calling a developer, and where the data from your contact form ends up.<\/p>\n
“Brochure site” covers very different objects. A five-page online business card has nothing in common with a thirty-page site the marketing team feeds in French and Arabic, or with a site carrying a price simulator and a booking form wired into the sales team’s calendar.<\/p>\n
Before comparing platforms, write down four answers: how many pages at launch and in two years, how often the content changes and who changes it, which languages (Arabic shifts the whole calculation), and which systems the site will have to talk to. Without those answers a quote is a guess, which is also why two proposals for “the same site” can differ by a factor of four.<\/p>\n
One more item, almost always forgotten: who pays the recurring bill, and from which budget line. A monthly subscription in dollars and an annual maintenance contract in dirhams are not defended in front of the same finance director.<\/p>\n
WordPress remains the default in Morocco, and for sound reasons. The ecosystem is mature, hosting is available from a local provider or a European one, and you are not locked to a single supplier: if the relationship goes bad, finding another WordPress developer in Casablanca or Rabat takes days. That market liquidity is often worth more than any technical argument.<\/p>\n
<\/p>\n
On substance, WordPress is a very solid CMS as soon as the content has to live: service pages that multiply, pages per city, articles, Arabic and French versions handled by the same team. User roles, SEO plugins, redirects after a redesign, all of it was solved long ago.<\/p>\n
The trade-off is paid in discipline. An unpatched WordPress becomes an open door, and most of the hacked Moroccan sites we are asked to recover were running a plugin two years out of date. Add annual licences billed in foreign currency (a premium page builder, a multilingual extension), which means an international payment card and a renewal calendar nobody owns in a thirty-person company.<\/p>\n
A field note: be suspicious of a brochure site delivered with thirty plugins. Every plugin is one more dependency and one more future update conflict. A clean site runs on fewer than ten.<\/p>\n
Webflow and its equivalents sell an attractive idea: hosting, CDN, certificates, backups and updates are handled by the platform, so technical maintenance disappears from your plate. That part is true, and it is a real relief for an SME with no IT department. The visual result is usually tighter too, because the tool is built for designers.<\/p>\n
The promise stops where your local constraints begin.<\/p>\n
For a ten to fifteen page site driven by a marketing team that wants a polished result and zero technical load, the arithmetic often lands on the right side. For a site meant to grow in content and languages, it is more debatable.<\/p>\n
For a purely editorial brochure site, custom web development is rarely the right call: you are funding an architecture to display pages a CMS displays perfectly well. The investment holds up in narrower cases.<\/p>\n
Technically, “custom” no longer means rewriting everything: a modern stack (static generation, headless CMS, CDN delivery) gives you a fast site with almost no public attack surface. Watch for the classic trap: a custom build delivered without an admin interface forces you to call the provider to change a phone number. The line between an enriched brochure site and an application is decided with the same criteria as the choice between SaaS and custom software<\/a>.<\/p>\n The ranges below reflect what circulates on the Moroccan market for a professional brochure site, copywriting and photography excluded. Use them against your quotes, not as a price list.<\/p>\n The recurring side weighs more than most owners expect: MAD 600 to 2,500 a year for decent shared hosting, MAD 1,500 to 5,000 a year for a VPS, MAD 1,000 to 3,000 a year in plugin licences on WordPress, a Webflow subscription billed per site per month in dollars, and a maintenance contract between MAD 500 and 2,500 a month depending on scope. Over five years the recurring total can exceed the build. Our guides on professional website pricing in Morocco<\/a> and on maintenance budgets<\/a> break that down line by line.<\/p>\n Picking a platform is mainly deciding who absorbs the technical load. On self-hosted WordPress, all of it lands on you: server, certificate, backups that have actually been restored once (restored, not merely scheduled), core and plugin updates, application firewall. “You” means a maintenance contract or a named person internally. With neither, the site holds for a year, then turns into a blank page or a redirect to a betting site.<\/p>\n On Webflow, infrastructure and updates leave your scope. What remains is access management (an employee leaving should not walk away with the owner account), the billing, and dependence on one vendor.<\/p>\n On a custom build it depends on the architecture. A static front on a CDN needs little visible upkeep, but dependencies still age: after two years an unmaintained build pipeline no longer compiles, and nobody notices until a page has to change. Hence the clause that really matters: who holds the code repository, the domain name, the DNS and the hosting accounts. That clause decides whether you can switch IT provider<\/a> without rebuilding from scratch.<\/p>\n The moment a contact form exists, you are processing personal data and Law 09-08 applies: the filing with the CNDP, information given to the person, a declared purpose, a retention period. That holds for all three options. What changes is where the data sits.<\/p>\n A WordPress instance hosted in Morocco or in Europe lets you control where messages land. One caveat: most form plugins save every submission to the database on top of sending the email, and nobody purges that table. After three years you hold thousands of contact records with no defined retention period.<\/p>\n With Webflow, submissions are stored on the vendor’s infrastructure, outside Morocco. Transferring personal data abroad is not forbidden, but it is regulated and has to appear in your file: check the applicable regime on the CNDP website before you choose, not after launch. The same question arises for a custom build hosted on a foreign cloud, except that you still control the database.<\/p>\n Two habits that pay off anywhere: ask only for what you genuinely need (a national ID number has no place in a contact form), and handle newsletter consent separately from the message itself. Legal notices and the cookie banner follow the same logic, covered in our piece on website CNDP compliance<\/a>.<\/p>\n A fourth question is worth asking even though it is uncomfortable in a kick-off meeting: how do you get out of this choice? WordPress migrates, Webflow gets rebuilt, a custom site can be taken over provided the code and documentation are yours. The same reasoning, with different parameters, applies when you pick an ecommerce platform<\/a>.<\/p>\n At Arrowlancer we build websites and web applications<\/a> on all three approaches, because the right answer depends on your team rather than on our technical taste. If a quote is already on your desk, we can review the platform it assumes before the project heads the wrong way: describe your situation through the contact form<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" WordPress, Webflow or a custom build: the criteria that actually decide a brochure site, 2026 budgets in dirhams and the CNDP risk in your contact form.<\/p>\n","protected":false},"author":0,"featured_media":276,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[1009,63,1012,1015,1018,1021],"class_list":["post-275","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tech_et_development","tag-cms-en","tag-cndp-en","tag-custom-web-development-en","tag-showcase-website-en","tag-webflow-morocco-en","tag-wordpress-morocco-en"],"_links":{"self":[{"href":"https:\/\/arrowlancer.ma\/blog\/wp-json\/wp\/v2\/posts\/275","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/arrowlancer.ma\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/arrowlancer.ma\/blog\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/arrowlancer.ma\/blog\/wp-json\/wp\/v2\/comments?post=275"}],"version-history":[{"count":1,"href":"https:\/\/arrowlancer.ma\/blog\/wp-json\/wp\/v2\/posts\/275\/revisions"}],"predecessor-version":[{"id":278,"href":"https:\/\/arrowlancer.ma\/blog\/wp-json\/wp\/v2\/posts\/275\/revisions\/278"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/arrowlancer.ma\/blog\/wp-json\/wp\/v2\/media\/276"}],"wp:attachment":[{"href":"https:\/\/arrowlancer.ma\/blog\/wp-json\/wp\/v2\/media?parent=275"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/arrowlancer.ma\/blog\/wp-json\/wp\/v2\/categories?post=275"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/arrowlancer.ma\/blog\/wp-json\/wp\/v2\/tags?post=275"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}What a showcase website Morocco buyers want really costs in 2026<\/h2>\n
\n
Hosting, updates, security: who carries what<\/h2>\n
CNDP and the contact form: what changes with each platform<\/h2>\n
Three questions to settle it before you sign<\/h2>\n
\n