
Stop Picking a CMS and Start Picking an Outcome
TL;DR
- An enterprise migration brief should define a measurable outcome and a deadline before naming a platform, because a CMS name promises nothing about results.
- The same CMS can produce a site your team can run alone or one needing a developer ticket per headline. Your choice of architecture, content model, and governance decide which.
- Platform choice still matters after the outcome is set: it determines how fast and safely you reach it, and whether you can leave without rebuilding.
A platform name is the least useful line in an enterprise migration brief (and it's usually the first one written). "Migrate to Webflow" tells a vendor which software to install, but it doesn’t say much about how fast your team needs to publish, how much organic traffic you can afford to lose at cutover, or whether marketing can change a headline without filing a ticket. Those are the things you're paying for, and none of them come bundled with the license.
I dug into this with Crowd Favorite CEO Karim Marucchi and Director of Client Delivery Adam Buckeridge on a recent episode of Building the Next Web. Karim's read is that large companies have stopped choosing between CMS A and CMS B and started choosing the outcome first. I agree that's where the brief should start. The platform question still matters, though. It just belongs second in line, and answering it well is what separates a migration that ends on schedule from one that spends its first quarter in damage control.
Your brief should name a result and a date before it names a platform
At Edgar Allan, we start every migration scope with what we call the logo test.
The logo test: Strip the platform name out of your migration brief and read what's left. If nothing measurable remains (no result, no date, no number someone can check on a dashboard), what you're holding is a software request, and five vendors will hand you five very different scopes for it.
A brief that passes the logo test is outcome-first: the site's job and deadline come first, and the platform is chosen afterward for how quickly and safely it can do that job. Here's what that looks like next to the usual version:
Each item on the right can be priced, planned, and held to a date, while the ones on the left push every hard decision past the contract signature, the most expensive moment to make one. (We cover the agency side of this in what to look for in a WordPress-to-Webflow migration agency.)
Enterprise buyers stopped asking for a CMS by name because budget follows results
Inside large companies, finance now approves a migration the way it approves any other spend: show it the dollar figure, the quarter it shows up in, and who owns the result. Karim's example of a pitch that gets approved is someone telling a department head they can save millions a quarter by replacing an incumbent CRM in 90 days. Those numbers are his illustration, so don't read them as typical, but the shape holds: a number, a deadline, and no platform loyalty anywhere in it.
Adam sees the same thing in Crowd Favorite's inbound. "People don't care about what the CMS is anymore," he told me. Some leads still ask for WordPress by name, but Karim noted that the most advanced clients have moved past naming a tool at all, which leaves Adam's team to suss out the goal and steer toward the platform that serves it. AI has sped this up, too: Crowd Favorite now sends working prototypes in the time a proposal used to take, and my guess is that buyers will soon expect to test-drive the outcome before they sign for it.
Karim goes a step further and says every major CMS he named, Webflow included, is "in a lot of trouble." I'd narrow that to the platforms that expect buyers to adapt to them. Webflow has started building toward something closer to a web harness, a layer you can set on top of other stacks, and a platform that hands teams primitives like that can adapt to the buyer instead. That difference shows up in speed, risk, and portability, which I'll get to below.
A platform name doesn’t tell you what you’re getting
Two companies can license the same CMS in the same month and end up with one marketing team delivering a campaign page on a Tuesday afternoon while the other waits two sprints to change a headline. The difference lives in the content model, the components editors can combine, publishing permissions, and how templates handle exceptions. A brief that only name-drops the platform leaves all of that to the vendor, and vendor defaults tend to favor the build window over the years your team will spend running the site.
Walker & Dunlop shows what the outcome looks like when the architecture is built for it. Update lead time dropped from more than ten business days to under one without engineering support, new page builds went from months to days, overall traffic grew 150%, and organic search traffic rose 30%. A lead-time number like that belongs in a brief on day one, because once it's written down, the content model, components, and permissions all get designed to hit it.
Where choice of platform still decides speed, safety, and portability
Once the outcome is on paper, the platform still decides how fast you get there, how much risk you carry at cutover, and whether you can leave later without starting over.
- Speed. Most of our more than 100 enterprise migrations have moved teams from WordPress, Sitecore, Drupal or AEM to Webflow. They’ve run from two weeks to 12 months, and a typical 200 to 500 page B2B SaaS site takes 12 to 20 weeks. Where you land in that range depends far more on data cleanliness, template exceptions, integrations, and decision speed than on page count. Our fastest projects all had one empowered owner on the client side with a 48-hour feedback commitment. On a rigid platform, every template exception becomes a dev ticket, and even the best owner ends up refreshing a Jira board instead of making decisions.
- Safety. When redirects are built before cutover and Search Console is verified within 24 hours of launch, organic traffic stabilizes in six to 10 weeks. Incremental releases lower the risk further. When we moved 1-800-GOT-JUNK from Drupal to Webflow, the project was scoped as two deployments over five to six months. We built a custom reverse proxy and a testing dashboard and delivered a release every week instead, which kept every release small enough to check.
- Portability. Karim's summary of what enterprise clients want was blunt: "They don't want to adapt to your product. They want your product to adapt to them." When the Webflow team asks me what I need, my answer is primitives, meaning first-party access so that if a client needs to pull content from Sanity or connect to AEM, the platform makes room. It's how I cook, too: I find the best, in-season ingredients first and write the menu second. The pan matters, but nobody chooses dinner because of the pan.
Use these benchmarks as a yardstick for any proposal you receive:
Seven smart lines in a brief will do more for your timeline than any platform feature
These seven lines turn a platform request into a brief a vendor can scope and you can hold them to.
- The outcome, in numbers. Two or three results that would make the project a success a year from now, such as publishing speed or developer hours spent on content changes, each one checkable on a dashboard.
- The deadline, and the reason for it. A date tied to a contract renewal, launch, or budget cycle gives vendors a real constraint. Arbitrary dates get padded.
- An editor self-sufficiency target. 30 days after launch is a reasonable bar. Name the editors and what they should be able to do without help.
- A search equity baseline. Export current organic traffic, top pages, and backlinks, and require redirects built before cutover.
- An integration inventory. Every system the site touches (CRM, marketing automation, search, analytics, SSO) and who owns it.
- A named internal owner. One person with decision authority and a 48-hour feedback commitment. If you only add one line, this is the one: it moves the timeline more than any of the other six.
- A deploy-anywhere requirement. Ask how content and data move in and out, where the site can be hosted, and what leaving would take. Adam's advice is to find out on day one what IT will reject, from hosting and data residency to approved vendors and AI policy.
When the draft is done, run the logo test on it. Delete every platform name and check whether all seven lines still make sense.
The right partner will talk you out of their favorite platform
Ask every agency how they'd scope your outcomes before writing a proposal, and which platform they'd recommend if your goals pointed away from their favorite. Adam's point, which I'd echo, is that the partners worth hiring have no incentive to sell you what your outcome doesn't need. Crowd Favorite runs without salespeople, and so do we. I've wondered whether I was sitting on my hands by not building an outbound team, but when I went back through our numbers, over half of our new projects had come through referrals. That only works if we keep recommending what the outcome needs.
At Edgar Allan, we scope from an audit against your outcomes before anyone writes a proposal. I'll own the bias up front: we're an enterprise Webflow partner, and most of the teams who find us are leaving WordPress, Sitecore, or Drupal because marketing can't touch its own site without a developer. When the audit says publishing speed and editor self-sufficiency matter most, it usually points to Webflow, which marketing can own and enterprises can deploy where their security teams need it. When the outcome is a heavily custom application, or content that has to feed several products at once, the audit may point to a headless CMS like Sanity with Webflow on top, or away from Webflow entirely, and you'll hear that from us before you see a price. More clients now count AI search visibility as an outcome too, so our Visibility & Optimization work runs from the same audit. If you're still building a shortlist, our data-backed rankings of the best Webflow agencies and our look at SOC 2 compliant agencies in the Webflow ecosystem are good places to start.
Before the RFP goes out, write down what the site has to do by when. The platform conversation gets a lot shorter and a lot more honest from there, and it's where I'd want to start with you: bring your outcomes and your deadline, and we'll scope an audit against them. Let's start a project.
This article is the first in a series that grew out of a conversation between Edgar Allan founder Mason Poe and two guests from Crowd Favorite, CEO Karim Marucchi and Director of Client Delivery Adam Buckeridge, for Building the Next Web. It's the same series that's brought us conversations with Finsweet's Alex Iglesias, ourCMO's Josh Webb, Code & Wander's Alessia Sannazzaro, Edgar Allan's own Witt Langstaff, Webflow's Nathan Huening, and more.
FAQs
How long does an enterprise CMS migration take?
Across more than 100 enterprise migrations, Edgar Allan projects have ranged from two weeks to 12 months. A typical B2B SaaS site of 200 to 500 pages takes 12 to 20 weeks. Timeline depends far more on data cleanliness, template exceptions, integration complexity, and decision speed than on page count. The fastest projects have one empowered owner on the client side who turns feedback around within 48 hours.
Should we run a feature-by-feature CMS comparison before writing the RFP?
Start with the outcome and the deadline, then compare platforms against them. A feature matrix shows what each platform can do in theory, and it only becomes useful once you know what the site has to do for your team. Once outcomes like editor self-sufficiency, publishing speed, and search equity preservation are written down, the platform comparison gets shorter and much easier to defend internally.
What should a WordPress to Webflow migration brief include?
A WordPress to Webflow migration brief should include seven lines: two or three measurable outcomes, a deadline with the reason behind it, an editor self-sufficiency target, a search equity baseline with redirects built before cutover, an inventory of every integration, a named internal owner with a 48-hour feedback commitment, and a deploy-anywhere requirement. Name the platform last. If the brief still makes sense with “Webflow” deleted, any agency can scope it accurately.
How do we protect organic search traffic during a CMS migration?
Build and test the full redirect map before cutover, and verify the new site in Google Search Console within 24 hours of launch. When both happen on time, organic traffic stabilizes within six to ten weeks. Benchmark your current traffic, top pages, and backlinks before the project starts so you have a baseline to measure against. Redirects built after launch turn the first months into damage control.
How much does an enterprise website migration cost?
Enterprise migrations and redesigns typically reach six figures or more. Total cost of ownership gives a far more useful comparison across agencies than hourly rates. That includes team size, CMS complexity, migration risk, integrations, and post-launch support. A brief with clear outcomes and an integration inventory lets agencies price the work accurately instead of padding for unknowns.
How soon can our marketing team edit the new site without developer help?
A well-built site with proper CMS architecture and editor training should reach editor self-sufficiency within 30 days of launch. That depends on decisions made during the build: how the content model is structured, which components editors can use, and who has publishing rights. Write the target into your brief so the architecture gets designed for it. Walker & Dunlop's update lead time dropped from more than ten business days to under one, without engineering support.