Webflow
From January 2025 to October 2026, I worked in Webflow directly for Circula: new pages, customer stories in two languages, navigation and consent.
The homepage hero builds up on load: heading, two buttons, three badges and a view of the app.
189 of 213
tickets assigned to me completed
Asana export, as of Oct 5, 2026
44 of 44
customer stories in German and English share one CMS item, previously 3
QA report on the Webflow CMS, Jun 25, 2026
634
days from the first ticket to the handover
Asana export, as of Oct 5, 2026
The starting point
Circula sells software for travel expenses, out-of-pocket expenses and company cards to finance teams. The website runs on Webflow in German and English, with Google Tag Manager, HubSpot forms and Usercentrics, and Cloudflare in front. Marketing, SEO and performance marketing kept needing new pages, campaigns and tests, but Circula had no Webflow team of its own.
Requests went through an Asana board to an external website team. Within that team, I worked in Webflow directly for Circula from January 2025, with designs coming in as Figma files. Every change had to hold up in both languages, and marketing had to be able to maintain pages without a developer.
Approach
01
I prepared the homepage test in September 2025 without changing the live homepage. The badges in the hero are variants of a Webflow component. The new travel expense page also went live in 2025 while the old version stayed in place, hidden, as a fallback and as the B variant.
The homepage hero builds up on load: heading, two buttons, three badges and a view of the app.
02
From February 2025 to July 2026, I maintained and extended the navigation in twelve tickets: new items for AI, webinars and reports, a new highlight card, the international version. When the menu was considered too sensitive in July 2026, I recommended a rebuild. A hover delay would only have worked in some browsers.
The mega menu opens with the product list and a card for the Finance Transformation Report.
03
In July 2026, I compiled all spacing, font sizes, radii, buttons and colors from the website's Client-First style guide as a reference for Figma. One click on desktop, tablet or mobile swaps all values, and each one can be copied.
In the token overview, one click on mobile swaps all spacing and font sizes for the values for small screens.
04
Result
From the first ticket on January 9, 2025 to the handover on October 5, 2026, 213 tickets were assigned to me, and 189 of them are done. They include the pricing page for the launch in February 2026, the product page for incoming invoices, and webinar and partner pages. For the editorial team, I built placeholders like {{excel}} that insert ready-made CTA blocks into blog articles. In July 2026, I set up Consent Mode v2 to default to “denied” before Tag Manager loads; the script for this came from Circula's tracking team.
For the customer stories, I merged the German and English versions: on June 25, 2026, each of the 44 pairs sat on a single CMS item, up from 3 before. The overview filters through readable URLs like ?branche=maschinenbau, and the canonical points to /de/kunden.
I haven't measured how the work affected visits, demo requests or load times; the numbers from Search Console, GA4 and HubSpot are with Circula. That's why this page shows scope and evidence, not conversion figures.
Webflow, Cloudflare, Google Tag Manager, Usercentrics, HubSpot, Figma, Asana
Testimonial
More case studies
Free 30-minute check
The quickest way to sort out the rest is a conversation: 30 minutes by video call, no sales pressure.
Prefer email? [email protected]
