From two-week page cycles to next-day launches
How Beqi migrated Loom's marketing site to Webflow and gave the team the publishing speed it needed during a high-growth stage.
The Challenge
Loom's productwas moving quickly, but the marketing website could not keep up. Everymeaningful page update required engineering involvement, which meant themarketing team had to wait for tickets, sprints, and development availabilitybefore campaigns could move forward.
That delaycreated a serious operating problem. A page that should have supported alaunch, feature update, campaign, or growth experiment could take roughly twoweeks to ship. By the time the page was live, the moment behind it couldalready be losing momentum.
For ahigh-growth SaaS company, the website needed to act like an extension of themarketing team, not a dependency on the product engineering roadmap. Loomneeded a system where marketing could launch pages, update content, and iteratequickly without pulling engineers away from product work.
The challengewas not simply to move the site to Webflow. The challenge was to rebuild theoperating model behind the website so the marketing team could publish withspeed and confidence after launch.
The Solution
Beqi migratedLoom's marketing site to Webflow in three weeks, rebuilding the site around anew design and a structured CMS that the marketing team could operateindependently.
We rebuilt thecomponent architecture from scratch so pages could be assembled and maintainedfaster. This gave the team a more flexible foundation for campaign pages,product messaging, and future website updates.
The CMS wasstructured around marketing use, not developer convenience. That meant thepeople responsible for publishing could manage content without touching code oropening engineering tickets for routine updates.
After themigration, Beqi continued supporting Loom so the team could be trained,onboarded into the new system, and supported as new page needs came up. Theproject was not just a launch - it was a transition into marketing-ownedpublishing.
The Results
The biggest result was speed: Loom's marketing team could move whilecampaign momentum was still active.
Page launchcycles dropped from roughly two weeks to one or two days. That changed how themarketing team could plan and execute. Instead of waiting on engineeringavailability, the team could publish closer to the moment of need.
The new Webflowfoundation gave Loom a cleaner way to create and manage marketing pages. Fasterpublishing meant more room for campaign iteration, stronger timing aroundproduct moments, and less friction between idea and launch.
Engineering wasalso protected. Routine marketing updates no longer needed to compete withproduct roadmap work. Webflow gave marketing more control while allowingengineering to focus where it created the most leverage.
The deepervalue was operational independence. Loom did not just get a migrated site - itgot a website system the marketing team could actually run.
FAQ
Beqimigrated Loom's full marketing site to Webflow, rebuilt the design, andstructured a CMS that gave the marketing team independent publishing control.
Thefull migration and redesign were delivered in three weeks.
Page launch cycles dropped from roughly two weeks to one ortwo days.
Loomneeded to reduce engineering dependency and give marketing the ability topublish and iterate faster.