From one landing page to Webflow Enterprise
How Quo (formerly OpenPhone) ran its marketing site for more than three years with Beqi building, testing, and shipping inside its Slack.
The Challenge
Quo's marketing team ships constantly: product launches, industry pages, integration pages, campaigns. The website is where all of it lands.
The team needed a Webflow partner that could keep up with that pace without the site drifting out of shape - and one that could carry the site through a full rebrand, from OpenPhone to Quo.
The Solution
The work started with one landing page. It grew into the full marketing site on Webflow, then into a monthly partnership that ran for almost three years.
What Beqi did
- Pages and overhauls. New pages and sections for marketing and product launches, plus rebuild-level overhauls of existing pages.
- Component system. A reusable component library, maintained and extended so new pages stayed consistent and fast to build.
- CMS. Collection structure, references, and templates, with guardrails so content edits did not break layouts or tracking.
- The rebrand. Website support for the move from OpenPhone to Quo, including a site-wide sweep of links and copy afterwards.
- Performance and SEO. Core Web Vitals work, page-weight audits, metadata, canonicals, redirects, and URL structure.
- Experiments. Tests built and run in Webflow Optimize.
Team, timelines, and collaboration
- Design. Quo supplied the designs. Beqi built from them. Beqi does not design.
- Development. A senior Webflow lead worked directly with Quo's marketing team - no account-manager relay.
- Rhythm. A weekly async update covering what shipped, what is next, and what is blocked, plus a weekly or bi-weekly working session.
- Turnaround. Requests were answered within one business day. Standard work typically started within one to three business days. Larger pieces were scoped into milestones with target dates.
- Urgent issues. Same-day response and a triage plan for anything affecting the live site.
QA on this engagement
- Before every release. Each page was tested across breakpoints and the major browsers before it went live.
- Every week. A health check of the main pages: calls to action, images, and responsive behaviour.
- After content changes. Checks that CMS updates had not broken layout, performance, or tracking.
- Regressions. Shared components and naming standards kept a change on one page from breaking another.
The Results
A single landing page became a partnership of more than three years.
The relationship grew from one page to the full marketing site, then to a monthly partnership that ran from April 2023 to early 2026.
The site kept pace with the company. Marketing and product launches shipped continuously, through a full rebrand from OpenPhone to Quo.
Quo's site now runs on Webflow Enterprise.
FAQ
Beqi built and ran Quo's Webflow marketing site: new pages, a reusable component system, CMS structure, performance and SEO work, and experiments in Webflow Optimize.
More than three years, from 2022 to early 2026, including a monthly partnership from April 2023.
Every page was tested across breakpoints and major browsers before release, and the main pages got a weekly health check of calls to action, images, and responsive behaviour.
No. Quo supplied the designs and Beqi built them in Webflow. Beqi does not do design.
