Meteoblue runs one of the most widely used weather services in the world, and its B2B arm sells weather data through APIs: forecasts, maps, measurements, and datasets. The B2B website had to sell to businesses the way the product deserved, and the team had built a complete design system in Figma to do it.
Then implementation stalled. Their previous partner had significant difficulties turning that design system into working components. The team was rightly skeptical of the next agency promising it would be different, so they asked every shortlisted provider a hard question: prove that your platform and your team can implement our design system, before we commit.
The requirements behind that question were real: a component library their own team could build pages with, six planned languages, a pricing and checkout flow for API products connected to their CRM, and GDPR compliance across multiple domains including a main site with thousands of auto-generated location pages. Webflow's own Partner team made the introduction through the Webflow Experts marketplace; the proof of concept closed it.
The proof of concept
Instead of a longer pitch, we rebuilt the first four sections of their landing page in Webflow in under 5 hours, from their Figma file, with minimal custom code, and sent it over with a video walkthrough. The reply came the next day: "It looks very promising!" That afternoon of work answered the exact question their previous partner had failed: yes, the design system translates to Webflow components.
Development
We built the component library and page structure so that meteoblue's own team creates pages and manages content without us. That was the explicit goal from the first call: allocate the build to us, then hand over control. The client entered content and visuals themselves on a QA'd site about nine weeks after kickoff. For a five-language B2B platform, that is time to market measured in weeks, not quarters.
Their design system stayed exactly theirs. We translated every Figma component into Webflow with the spacing, type, and states intact, and the ongoing collaboration runs designer-to-developer: meteoblue's designer comments in Figma, our developer ships it, pixel-accurate, in days.
The pricing and checkout flow was the most complex piece: a multi-step checkout for four API products (Premium Weather API, Weather Maps Tile API, Measurements API, and Dataset API), with the final step gated on a successful response from their CRM, so no lead ever silently disappears. We designed the integration architecture together with the client's CRM integrator and validated it live before launch.
Localization
We evaluated Crowdin, Weglot, and Webflow's native Localization against their six-language plan, consulted Webflow's team directly, and recommended native Webflow Localization on the advanced plan. The first locale went live in January 2026. Today the site runs in five languages: English, German, Spanish, French, and Italian, with a shared component system keeping all locales consistent.
Compliance and handover
GDPR and cookie compliance shipped across three meteoblue domains via CookieScript, with our lawyer handling the legal configuration, including the IAB consent framework variant for the main site's thousands of auto-generated location pages. Handover came with a tutorial video library: a video per component, recorded for their team's daily workflow. Since February 2026 the engagement has run on prepaid support packages with client-visible time tracking, covering new pages, design updates, and analytics: a GA4 event funnel now tracks the checkout end to end.
The Results
| Metric | Result | Context |
|---|---|---|
| Under 5 hours | for the proof of concept that won the engagement: the first 4 landing-page sections rebuilt from Figma after a prior vendor failed. | |
| 480 URLs live across 5 languages | 96 unique pages each in English, German, Spanish, French, and Italian, verified August 2026. | |
| ~9 weeks from kickoff to content-ready | Kickoff December 1, 2025; meteoblue's team entering content on a QA'd site by early February 2026. | |
| 50 solution pages and 20 product pages | built on the component system, plus articles, pricing, checkout, and company pages. | |
| A self-service team | meteoblue builds pages without us, supported by a per-component tutorial video library. | |
| 10+ months and counting | Build, then prepaid support packages since February 2026, with a dedicated developer and an active design-update workflow. |
“Creative Corner rebuilt the first four sections of our landing page in under five hours as a proof of concept, and that's exactly how the whole project went: fast, precise, and easy to work with. Two months after kickoff our team was already building pages ourselves, in five languages, with the checkout wired into our CRM.”
Philipp Kowatzki
Deputy Head of Product Meteoblue AG
Services we delivered
- Webflow Development: full Figma-to-Webflow build of the component library and site structure, built for client self-service
- Proof of Concept: 4 sections in under 5 hours to de-risk the decision after a failed prior vendor
- Localization: platform evaluation (Crowdin vs Weglot vs native), Webflow Localization setup, 5 locales live
- Checkout and CRM Integration: multi-step API-product checkout with CRM-confirmation-gated completion
- GDPR Compliance: cookie consent across 3 domains including the IAB consent framework, configured with our lawyer
- Analytics: GA4 and Google Tag Manager event tracking across the pricing funnel
- Ongoing Support: prepaid hour packages since February 2026, dedicated developer, client-visible time tracking
