Case study
Capital For Life
A Next.js container that hosts Webflow marketing and Lovable.dev application surfaces under one domain — so the brand stays coherent while each surface keeps the tools that suit it best.
The problem
Capital For Life had two surfaces with different gravity. The marketing site needed to move at the speed of a content team — which meant Webflow. The application views needed the speed of an internal product team — which Lovable.dev was already serving well. Stitching them together by domain alone meant brand drift and visitors who could feel the seams.
The shape we built
A Next.js container app sits at the apex domain and routes to each surface as a sub-application. Webflow renders the marketing pages; Lovable.dev renders the application views; the container handles everything that has to be true across both — navigation chrome, error pages, analytics, and the parts of the brand that can't be allowed to drift.
What it gives the team
- Marketing keeps Webflow's authoring speed.
- Product keeps Lovable.dev's iteration speed.
- Visitors get one consistent experience — one nav, one identity, one footer.
- Engineering owns one container, not three half-integrated stacks.
Why this pattern matters
Most "hybrid" Webflow setups end up as glorified iframes or worse — proxy routes that break the moment a tool updates. The container pattern flips it: each tool keeps its native authoring environment, and the container is the only thing that has to know how they're stitched together. When a tool changes, the seam moves; the surfaces don't.
Got a similar shape?
If you have a marketing surface and an application surface and they're starting to drift apart, we'd like to hear about it.
Tell us about your project