Scribe

Who Scribe is and why its new brand needed a new Webflow build

Scribe helps teams capture how work gets done and turn it into context for people and AI agents. Its website is owned by a small product marketing team led by Meg Zabrowski, working with Ivan Salim, Scribe's in-house designer and developer. We already knew them well: Scribe was a Fri3nds subscription member, and we had shipped pages for their product launch the year before. Then Scribe refreshed its brand. The rebrand came from Scribe's brand partner, and Scribe asked Fri3nds to bring it to life as a brand new Webflow development project. The team was lean, and Meg had never hidden it.

"we're very understaffed internally. So while we have this sprint, we will always have a need for dev support."
Meg Zabrowski, Lead Product Marketing, Scribe

The challenge: a new brand, a fixed launch window and millions of visitors

A new brand is a promise with a date attached. For Scribe, the new site had a hard launch date that could not move, and at kickoff Ivan put the build window plainly: "Three weeks and a half is going to be a little bit tight." The old site couldn't carry the new look either. Pages had been built fast, one at a time, and as Ivan had told us when we first opened the project, "I don't think any of it is a component." Speed alone wasn't the goal, though. Meg set the bar for how we would get there, and it shaped every decision that followed.

"I never want quality to be given up in exchange for speed when it comes to the website. We've got millions of people who visit our site every month."
Meg Zabrowski, Lead Product Marketing, Scribe

How we built a 40+ component system for Scribe's new brand

We started the way we always do, by aligning on goals and priorities with Meg and Ivan, then putting every page and component on one shared board. Instead of patching the old project, we started a fresh Webflow project on the MAST framework and built it on its own staging domain, straight from the brand partner's Figma files. Components came first. Richard built the library to the new brand while Nico and Terry led delivery, so every page was assembled from the same parts. That order was deliberate: it is slower on day one and much faster on every page after. Ivan liked where it was heading from the kickoff call.

"I like that there's like more of a system now."
Ivan Salim, Scribe

How we launched Scribe's new site without a risky migration

A new project called for a smart release. Rather than a big-bang Webflow migration, we served the new pages through a reverse proxy from scribe.com to the refreshed project, so Scribe could switch its new brand on without moving everything at once. We rebuilt Scribe's Intellimize setup on the new site too, so the testing program came along for the move. Scribe flipped the switch inside its launch window, about four weeks after kickoff, and their team posted three words in our shared channel: "New site is live." We spent the next days tuning the launch with them, page by page.

• 40+ components built to Scribe's new brand
• ~4 weeks from kickoff to the new site live

What changed for Scribe's web team

The biggest change isn't a single page. It's how the site is put together. Before the Refresh, every new page started from scratch. Now a shared component library sits underneath the homepage, the product pages for Capture and Optimize, Enterprise and the solution templates, which is exactly what a small team needs to keep up with a company moving this quickly. The launch was never the finish line either. Meg already had the next slices of pages planned before the first one shipped.

"we'll probably have two more tranches... maybe 20 more pages or something like that to come after."
Meg Zabrowski, Lead Product Marketing, Scribe

What happened after launch

We're still Scribe's Webflow team, building on the new system as the next tranches of pages come in. The work follows the same flow as the Refresh: align on what matters most, put it on the board, build it on staging, release it, then pick up the next slice. Scribe has now leaned on us through two very different moments, a product launch and a full rebrand. Meg said it best while reflecting on our work together.

"I can't even tell you how huge of a help you guys were... there just would have been zero chance that we could have accomplished what we needed without you guys."
Meg Zabrowski, Lead Product Marketing, Scribe

Credits

• Client: Scribe. Meg Zabrowski (Lead Product Marketing), Ivan Salim
• Brand: Scribe's brand partner
• Webflow development and component system: Fri3nds (Richard, Nico, Terry)
• Services: Webflow development, Webflow component system, reverse proxy launch, Intellimize setup, Fri3nds subscription