All Work

Atlantic Partners Asia

Full Webflow redesign for a cross-border payments firm: 13 layouts, three built fully headlessly through the API.

Live Site ↗
Industry ·
Financial services (cross-border payments and FX)
Engagement ·
Project-scoped
13
Layouts Built: 10 Static Pages Plus 3 CMS Templates
41
FAQ Answers With Filter And Search
99.1%
Of Webflow's 50,000-Character Custom-Code Cap At Peak, Survived Via A Comment-Stripping Build Script
Atlantic Partners Asia

The Challenge

Atlantic Partners Asia is a cross-border payments and FX company operating across Asia and Europe. The engagement began as technical maintenance and auditing of their existing Webflow site, then grew into a full redesign: a new Webflow project built from scratch on a Relume base with the Client-First class system, from Figma designs supplied by the client, who is also the designer.

The locked scope covers 13 layouts: 10 static pages (Home, three Products pages, Platform, Company, Contact, Resources, FAQ, Legal) plus three CMS templates, replacing the current site at launch with every URL preserved or 301-redirected. The launch is scheduled for late August 2026, so this entry describes a build in its final stretch rather than a shipped outcome.

Engagement
Intake · CMS
Client
Atlantic Partners Asia
Industry
Financial services (cross-border payments and FX)
Engagement
Project-scoped

What I Shipped

Headless Page Builds From Figma

Three of the thirteen layouts were built fully headlessly through the Webflow API rather than in the Designer, with logged build times: sections translated from Figma frames into native Webflow elements, classes, and styles via the MCP toolchain. The remaining layouts were built in the Designer with generated code embeds. Measured wall-clock times for the headless builds: Global Accounts in roughly 1h05m from first API write to staging, plus about 15m of QA fixes, and Platform in roughly 1h35m from first API write to staging-verified, with asset export and upload included.

A 41-Question FAQ System

Turned the client's FAQ document into a full page: 8 categories, 41 questions and answers, a custom accordion with a category filter and live search, and FAQPage JSON-LD generated on the page. Built headlessly as a static page so nothing depends on runtime CMS calls.

Engineering Around The 50,000-Character Cap

Webflow caps each custom-code field at 50,000 characters, and the contact page (an international form with a country combobox, phone input, service multiselect, and field rules) reached 99.1 percent of it. The fix is a build script that assembles the page's code comment-free from individual source files, using a real JavaScript parser rather than regex, splits it across the head and footer fields, and asserts the load-bearing script order so a bad edit fails the build instead of silently breaking the page. The homepage's interactive hero globe gets the same treatment, with assertions that every embedded base64 flag survives the strip.

CMS Migration And Integrity Monitoring

Staged the content migration across 6 collections and 44 items, including a new Onboarding collection that replaces 20 static pages, with all assets re-uploaded so nothing depends on the old site. Before launch, the project also gained a three-layer integrity monitor: weekly field-level CMS baselines (129 text fields), rendered-page checks across 49 live URLs (metadata, robots, canonicals, JSON-LD, forms), and a monthly full-content archive committed to git as a restore source.

Build Log
Excerpt · CMS

The Results

The site launches at the end of August 2026, so there are no outcome numbers to report yet, and none are claimed. What exists today: 13 layouts built and verified at desktop and wide breakpoints, with mobile passes on the later layouts and the FAQ page's interactive-code paste still outstanding as of 2026-08-28, a measured build log for the three headless page builds, a redirect map protecting every existing URL, and monitoring in place from day one. This entry will be updated with post-launch facts once they are measured.

Audit Results
Verified · CMS
Metric
Before
After
Figures as stated in the engagement changelog
Headless page builds|Global Accounts ~1h05m first API write to staging, plus ~15m of QA fixes; Platform ~1h35m to staging-verified|build log FAQ page|8 categories, 41 Q&As, custom accordion with category filter and search, FAQPage JSON-LD|built 2026-08-28 Custom-code budget|contact page peaked at 99.1% of the 50k cap; JS now generated comment-free, split across head and footer with load-order assertions|in place Hero globe|interactive canvas globe with generated embed pair and base64 flag-count assertions|in place CMS migration|6 collections, 44 items staged; a new Onboarding collection replaces 20 static pages|staged Integrity monitors|3 layers: 44 CMS items and 129 text fields baselined, 49 live pages watched, monthly content archive in git|set up 2026-08-28
Upwork review
Read it on Upwork

Have a Build Like This One?

Thirty minutes, your project on screen. You leave with a scoped plan and a number, whether or not we work together.

30 MIN · GOOGLE MEET · EUROPE/PARIS