Hire an agency when the site is a revenue asset and you need it right the first time. Build in-house when you will change the site constantly and can afford a person who does that all day. The deciding factor is not budget. It is how often the site needs to change after launch.
We are an agency, so read this with that in mind. We also turn work down regularly, usually because the company in front of us would be better served by hiring one good person. That is a genuinely better outcome for them, and pretending otherwise wastes everybody's time.
What follows is the honest version of the comparison, including the parts that do not flatter us.
It means owning the design, the build, the content structure, the SEO, the performance work, and the ongoing maintenance yourself. Webflow makes the build accessible, which is why so many teams try it. The gap is rarely the tool. It is the range of skills a good site quietly requires.
A marketing site needs someone who can design a page that converts, structure a CMS that will not fall apart in a year, write markup that search engines and AI answer engines can read, and keep the thing fast as tags accumulate. Those are four different skill sets. One talented generalist can cover them. Most people cover two well and fake the rest.
Webflow University is free and genuinely excellent, which changes the math for anyone willing to invest the time. Someone motivated can learn to build competently in a few months. The question is whether the person you have in mind has a few months, or whether they already have a full-time job doing something else.
Speed and judgment, mostly. A studio that has shipped many sites already knows which layouts convert, which CMS structures break, and which performance problems appear at launch. You pay for the decisions being right the first time rather than being discovered over three rebuilds.
The other thing you are buying is a fixed end date. In-house projects drift, because the person building the site also has a day job and the site is nobody's deadline. Across our own work a typical project runs four to eight weeks, with landing pages closer to three or four and larger builds stretching to ten. That constraint is a feature, not a limitation.
What an agency does not give you is availability. We are not sitting in your Slack at 9pm when a product launch changes. That is the real trade, and it is the one most people underestimate when they compare quotes.
The platform cost is identical whichever route you take, and it is smaller than people expect. Webflow's site plans start free on Starter, move to Basic at $15 a month billed yearly for a site without a CMS, and reach Premium at $25 a month billed yearly for content-driven sites with the CMS included.
The tiers are worth understanding before you budget. Starter gives you a webflow.io domain, two static pages, and 1 GB of bandwidth, which is enough to learn on and nothing more. Basic adds a custom domain, 300 static pages, 10 GB of bandwidth, and unlimited form submissions. Premium is where the CMS, code components, and site search live.
Webflow's pricing page puts the CMS limits at up to 20,000 CMS items and 40 CMS Collections on the top site plan. For almost every marketing site that is not a constraint you will ever meet. If it is, you are building something closer to a product than a website, and that changes the conversation entirely.
None of this is where the money goes. The platform is a rounding error next to the cost of the person or the studio building on it, which is exactly why platform price should not drive the decision. We break the full picture down in our guide to what a Webflow website costs.
When the site changes weekly. If you run frequent campaigns, publish constantly, or test landing pages as a core motion, an in-house builder pays for themselves quickly. Agency retainers are a poor fit for work that arrives in small, urgent pieces with no notice.
It also makes sense when the site is genuinely simple and will stay simple. A five page site for a business that changes its messaging once a year does not need a studio. It needs someone competent to build it once and a plan for who updates the copy.
The third case is the one people miss. If you already employ a strong designer who wants to learn Webflow, that is often the best investment available. They already understand your brand and your customers, which is the expensive part. The tool is the cheap part.
When the site has to perform, not just exist. If organic search is a real channel, if the site is your main sales surface, or if a redesign is tied to a funding round or a launch date, the cost of getting it wrong is much larger than the cost of the build. That is when experience earns its price.
It is also the right call when nobody internally owns the site. Sites without an owner rot. Every marketing team has a homepage that three people can technically edit and nobody actually maintains, and it shows in the load time and the broken links. An agency at least forces a clear point of responsibility.
The third case is migration. Moving from WordPress, Squarespace, or a custom stack onto Webflow without losing search rankings involves redirect mapping, URL structure decisions, and technical SEO that punishes small mistakes badly. It is the highest risk moment in a site's life and a bad time to be learning.
Maintenance and drift. A site launches fast and clean, then accumulates marketing tags, unoptimized images, and one-off pages built under deadline pressure. Two years later it loads in four seconds and nobody can point to the change that did it, because no single change did.
This happens to in-house builds and agency builds equally. The difference is who notices. An agency on a retainer has a reason to watch the numbers. An in-house owner watching their own work rarely audits it, not through carelessness but because the site looks fine to the person who built it.
Whichever route you pick, put a recurring audit in someone's calendar. Twice a year is enough to catch the drift while it is still cheap to fix, and it costs almost nothing compared with a rebuild.
Insist on a proper handover as part of the contract, not as a favor afterwards. You should end up owning the Webflow project, holding the billing, and having documentation of how the CMS and the class system are structured. If an agency resists any of that, the resistance is the answer.
Webflow makes this easier than most platforms, because a project can be transferred and site billing can be moved to the client's own account. There is no technical reason for an agency to hold your site hostage, which means any that does is choosing to.
We wrote up how we run this process in our guide to Webflow client handoff. Our own view is simple. A studio that builds a site the client cannot maintain has not finished the job, whatever the invoice says.
Ask what happens after launch, ask to see the last three sites they shipped rather than the best three, and ask for a fixed quote rather than an hourly estimate. The answers tell you more about how a studio works than any portfolio page will.
The fixed quote question matters most. Hourly billing puts you and the studio on opposite sides of every decision, because every extra revision earns them more. We scope properly and then quote a fixed price for exactly this reason, across three tiers depending on the size of the build. Once the number is agreed, we are both trying to make the same site as good as possible.
Also ask who actually does the work. Plenty of agencies sell you a senior team and staff the project with whoever is free. Across more than 150 projects we have learned that continuity matters more than headcount, and it is a fair question to ask directly.
If you are still weighing studios, our piece on how to choose a web design studio covers the rest of the questions worth asking.
Count how many times your site will meaningfully change in the next twelve months. If the answer is more than about twenty, hire someone in-house. If it is fewer, and the site matters commercially, hire a studio to build it properly and keep a smaller retainer for changes. That single question settles most cases.
The worst outcome is the middle, where a company hires an agency for a beautiful build and then has nobody internally who can update it. The site slowly goes stale, and everyone concludes the agency was a waste of money when the real gap was ownership. Decide who owns the site before you decide who builds it.
If you want to talk it through honestly, including the version where we tell you to hire instead, let's talk. We're happy to give you a straight read at phoenix.studio.
Tell us where you want to go. We'll tell you how we'd get you there.