A double-digit homepage lift and pages in a day

How Beqi moved Quo (formerly OpenPhone) to Webflow one page at a time and ran its marketing site for 3+ years inside its Slack.

Double-digit

Homepage increase from Beqi's CRO work

<1 day

To build a new page on the component system

3+ years

Working together, from one landing page to the full site

FROM THE CLIENT

"I highly recommend Beqi to anyone looking for a Webflow partner. Their craftsmanship, care, and Slack responsiveness make them feel like a true extension of our team."
John MacGaffey, Senior Manager, Growth Marketing at Quo

John MacGaffey

Senior Manager, Growth Marketing, Quo

Key takeaways

Quo's marketing site was built and maintained by front-end developers shared with product, so every change waited in an engineering queue.

Beqi moved the site to Webflow one page at a time, built a style system and component library, and ran it as a monthly partnership from April 2023.

CRO work led to a double-digit increase on the homepage, new pages took under a day to build, and the site carried Quo through a full rebrand.

01

The Challenge

Quo's marketing team ships constantly. Its website could not keep up.

Product launches, industry pages, integration pages and campaigns all land on the website. But the site was built and maintained by Quo's front-end developers, who also worked for product. Every change went the same way: a task, a dev ticket, resourcing, coding, QA and publishing. Even a new CMS field had to be requested.

That process was slow, expensive and hard to scale, and marketing was always competing with product for the same developers.

Why a partner, not more developers

Quo needed its marketing pages off the engineering queue, and a Webflow team that could keep pace without the site drifting out of shape. Later, that team would also have to carry the site through a full rebrand, from OpenPhone to Quo.

02

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 3+ years.

What Beqi did

  • Style system first. A style system and component library came before any page, so every new page stayed consistent and fast to build.
  • Pages and overhauls. New pages and sections for marketing and product launches, plus rebuild-level overhauls of existing pages.
  • CMS. Collection structure, references and templates, with guardrails so content edits did not break layouts or tracking.
  • Training. Beqi taught Quo's marketing team to create and update pages, add CMS collections and connect tools like Zapier, so it could manage content itself.
  • The rebrand. Website support for the move from OpenPhone to Quo, including a site-wide sweep of links and copy afterward.
  • Performance and SEO. Core Web Vitals work, page-weight audits, metadata, canonicals, redirects and URL structure.
  • Experiments. CRO tests built and run in Webflow Optimize.
The Quo integrations directory on Webflow
The integrations directory on quo.com, driven by Webflow CMS.

Team, timeline 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, with no account-manager relay.
  • One Slack. Beqi worked inside Quo's Slack as part of the team.
  • Rhythm. A weekly async update covering what shipped, what was next and what was 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 behavior.
  • 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.
03

The Results

A single landing page became a marketing site Quo's team could run, and a partnership of 3+ years.

  • A double-digit increase on the homepage. CRO tests were built and run in Webflow, and what worked could be rolled out across the site almost overnight instead of waiting for an engineering sprint.
  • New pages in under a day. With the style system and component library in place, new pages were assembled from existing blocks.
  • Marketing managed its own content. Training meant Quo's team could create and update pages and CMS content without a developer.
  • Through a full rebrand. Marketing and product launches kept shipping while the site moved from OpenPhone to Quo.
"Our recent work on CRO led to a double-digit increase on our homepage." - John MacGaffey
Customer stories page on quo.com
Customer stories on quo.com, under the Quo brand.

The partnership was presented at Webflow Conf 2024 and featured on Webflow's blog. Quo's site now runs on Webflow Enterprise.

Visit the live site: quo.com

About these results

FAQs

What did Beqi do for Quo?
How long did Beqi work with Quo?
What were the measurable results?
How did QA work on the Quo site?
Did Beqi design the Quo site?
Next case study

Continu

Trusted by 140+ enterprise and fast-growing teams

A Webflow partner for everything that comes next.

New campaigns, product launches or a rebrand ahead? Bring Beqi into your marketing team for ongoing Webflow development, CMS updates and a steady release rhythm.