ChallengeAn Amsterdam-headquartered B2B SaaS company (EUR 42M ARR, 380 employees, serving enterprise customers in 14 European countries from their Amsterdam base) needed to redesign their corporate and product marketing website. The existing website: (1) was English-only — while the product UI was localized in 8 languages, the marketing website existed only in English. This created a disconnect: Dutch prospects searched for "supply chain software" in Dutch on Google.nl but found no Dutch-language results from the company. German prospects (the company's second-largest market) could not find the company through German-language search queries. The company's SEO analysis showed they were invisible for non-English search terms representing 60% of their addressable market search volume, (2) GDPR compliance was inadequate — the existing cookie consent implementation used a "cookie wall" (requiring consent before accessing the website) which Dutch AP had explicitly ruled illegal. The privacy policy was a US-style legal document — not the clear, transparent Dutch-language policy that AP expects. Analytics ran Google Analytics Universal (deprecated) without IP anonymization. The company's DPO (Data Protection Officer) flagged the website as a compliance risk, (3) did not reflect the company's European positioning — the website looked like a Silicon Valley SaaS company (aggressive conversion tactics, pop-up modals, auto-playing video, excessive exclamation marks in copy). This visual language felt wrong for the European enterprise market — Dutch and German enterprise buyers are skeptical of aggressive marketing and trust understated, informational presentations. Several enterprise prospects had mentioned in sales calls that the website "didn't feel European" and "felt like they were trying too hard," (4) the blog was underperforming — 450 blog posts had been published over 4 years but traffic was declining. Analysis revealed: posts were keyword-stuffed and thin (500-800 words of generic content), no technical depth (the company's engineering team had expertise that never reached the blog), and no multilingual content strategy (all content English-only, missing European language search opportunities), and (5) performance was poor — mobile PageSpeed score: 28. The site loaded 4 JavaScript frameworks simultaneously (React, jQuery, a legacy Angular module, and an embedded Vue component from a third-party widget). Time to interactive on mobile: 8.2 seconds on 4G connection.
SolutionWe redesigned on Next.js with Storyblok CMS (chosen for its multilingual capabilities) over 12 weeks: (1) Multilingual architecture: full website in 5 languages — Dutch (primary), English, German, French, and Spanish. Each language: professionally translated by subject-matter translators (B2B SaaS terminology requires specialist translation — "supply chain visibility" has specific equivalents in each language that generic translators miss), separate URL structure (/nl/, /en/, /de/, /fr/, /es/) with hreflang tags, language-specific SEO (keyword research in each language — German search terms for supply chain software are fundamentally different from English equivalents), and language-specific content (not just translation — some blog posts and case studies written specifically for German or Dutch audiences, addressing local market dynamics). Language detection: visitors from Dutch IP ranges see Dutch content by default with a non-intrusive language switcher. Storyblok CMS: multilingual content management with translation workflow — content created in one language, automatically queued for translation with review stages. (2) Dutch design system: visual design reflecting Dutch design values rather than Silicon Valley aesthetics. Typography: Neue Haas Grotesk (the original Helvetica, honouring the Swiss-Dutch typographic tradition) — clean, authoritative, and universally legible. Colour: deep blue primary (trust, authority — the dominant colour in Dutch financial and corporate design), warm gray secondary, and single accent colour (amber) for CTAs and interactive elements. Layout: generous whitespace, grid-based with clear information hierarchy — every page designed to be scannable (Dutch users are efficient and decisive in their browsing behaviour). Photography: real product screenshots, real team photography (no stock imagery — Amsterdam audiences detect and distrust stock photography instantly), and customer environment photography showing actual European enterprise settings. Removed: pop-up modals, auto-playing video, aggressive CTAs, and exclamation marks from copy. Replaced with: clear product demonstrations, technical depth, and measured confidence. (3) GDPR/AP-compliant implementation: cookie consent replaced with Cookiebot (AP-recommended platform). Implementation: genuine reject button (same size and visual weight as accept), granular consent categories (necessary, functional, statistical, marketing — each explained in clear Dutch), no cookie wall (website fully accessible without consent), consent logging with timestamp and categories, and quarterly consent report generation for DPO. Analytics: Google Analytics 4 with IP anonymization enabled, consent-mode integration (analytics only fire after explicit consent), and server-side tagging (reducing client-side data exposure). Privacy policy: rewritten in clear Dutch and English (not legalese) explaining in plain language: what data is collected, why, with whom it is shared, and how to exercise data rights. Contact forms: each form field with clear purpose justification (data minimization principle — every field must have a processing purpose documented in the privacy policy). (4) Technical content strategy: blog relaunched as a technical resource centre. 450 existing posts audited: 120 consolidated/updated, 280 retired (thin, keyword-stuffed content removed), 50 retained as-is. New content strategy: technical deep-dive articles written by the engineering team (2,000-3,000 words, genuine technical depth — "How we reduced supply chain visibility latency from 4 hours to 12 minutes" rather than "5 Benefits of Supply Chain Software"), industry analysis in multiple languages (Dutch-language content targeting Dutch supply chain market, German-language content targeting German Mittelstand), and customer case studies (anonymized where required) with genuine business outcomes. Monthly publishing: 4 posts in English, 2 in Dutch, 2 in German — creating a multilingual content engine. (5) Performance rebuild: Next.js replacing the multi-framework chaos. Single framework (React/Next.js) with: static generation for marketing pages (instant page loads), incremental static regeneration for blog content, and dynamic rendering only where necessary (pricing calculator, demo booking). Mobile PageSpeed: from 28 to 94. Time to interactive: from 8.2 seconds to 1.4 seconds. Core Web Vitals: LCP 1.8s, CLS 0.02, INP 120ms — all in "good" range. (6) Conversion architecture: replaced aggressive pop-up tactics with conversion paths suited to European enterprise buying behaviour. Product demonstration: interactive product demo (not gated — European enterprise buyers distrust gated content and prefer to evaluate before providing contact information), technical documentation publicly accessible (not behind registration walls), and "request demo" positioned as a natural next step after self-service evaluation — not a barrier to information. Pricing: transparent pricing page (European buyers expect pricing transparency — hidden pricing signals untrustworthiness in Dutch and German markets).
OutcomeMultilingual SEO: organic search traffic increased 340% within 9 months. Dutch organic traffic: from zero to 12,000 monthly sessions (the company was previously invisible for Dutch-language search). German organic traffic: from 2,400 to 18,000 monthly sessions (650% growth). French and Spanish: combined 8,000 monthly sessions (new). Enterprise leads from non-English search: from 4 per month to 28 per month (600% increase). The company's largest deal in year one (EUR 420K ACV) originated from a German-language Google search. GDPR compliance: AP-compliant consent management implemented. DPO confirmed zero compliance findings. Cookie consent rate: 62% opt-in (versus the previous cookie wall's forced 100% — the 62% represents genuine consent, which is more valuable for GDPR compliance and analytics accuracy). Brand perception: enterprise prospect feedback shifted from "the website didn't feel European" to "the website feels like a company we'd want to partner with." The redesign was featured in Emerce (Dutch digital industry publication) as an example of excellent B2B web design. Content performance: technical blog posts averaged 4x more engagement than previous generic content. Average time on page: from 1:20 to 4:45. The engineering team's deep-dive articles became the primary organic acquisition channel — outperforming paid advertising for enterprise lead quality. Mobile performance: PageSpeed from 28 to 94. Mobile bounce rate from 64% to 31%. Mobile conversion rate from 0.4% to 1.8% (350% improvement). Overall: website-sourced pipeline increased from EUR 4.2M to EUR 14.8M annually (252% growth). Development cost: EUR 168,000. Payback period: 6 weeks based on pipeline increase.