What's Included in Web Design Services?
"Web design services." Ask ten different people what those three words mean and you’ll likely get a generic answer from all of them. But gently push for details and you’ll likely get different answers.
One studio maps out your content structure, gives you a CMS (content management system) you can manage yourself, tests across browsers, and supports the site after launch. Another covers the visual design and the build but leaves the content, testing, and ongoing maintenance entirely to you.
Same label. Different process and outcomes. So let's clear it up. In this post I’ll go over what’s included in a well-run web design engagement, where the boundaries usually sit, and the misconceptions that trip people up most often. The goal isn't to sell you on a particular process or methodology; it's to help you understand what to expect, so you can ask sharper questions of anyone you're thinking about hiring.
"Web Design" and "Web Development" Aren't the Same Thing
Web Design is where we figure out what the site should say (i.e. your site’s copy/content/text), how it should be structured, and what it should look like.
Web Development is where that design becomes a real, functioning website: code, a content management system, integrations, the works.
Design and development often get bundled together under one heading, which makes sense since most projects include both. But they ask different things of you. The design phase mostly needs your feedback, your content, and your sense of where the business is headed. Development also needs your feedback but also requires access to critical services, your hosting, your server, and more. It can be surprising how much access development requires so that’s worth knowing going in.
That all said, you can hire a web studio for design only, development only, or both—it depends on what they offer of course. The deliverables shift depending on which you choose and/or need.
How a Project Actually Unfolds
Most good web projects follow an arc: it starts with discovery (kickoff, getting necessary info for the project, and in the case of Block 81, it includes some high level planning), moves into design, then into development. Before launch there’s a dedicated phase for testing features, browser compatibility, performance, and accessibility. Part of that testing phase includes putting the site up on a staging (i.e. testing) URL so it can be reviewed in a real environment. Once the staging site is approved, a launch date gets scheduled and the site is deployed.
What You Actually Walk Away With
Let's talk about the deliverables, because this is where expectations and reality often part ways.
You should walk away with a built, functioning website, a CMS you can use to manage it, and usually some documentation. What clients typically don't walk away with is a pile of source files.
Many designers work in tools like Figma, and the working design files usually aren't part of the standard handoff. File ownership is worth clarifying up front with any web designer you hire, it's a fair question, and you should know the answer before you sign rather than assume it.
One more thing worth flagging: branding and logo work is often separate from web design. Some shops bundle it, some don't. If you need a logo or a brand identity, check whether it's part of the engagement or its own project.
The Misconceptions That Trip People Up
A few assumptions come up again and again. None of them make a client wrong, they're just gaps in what the industry has bothered to explain.
"A website is a one-time purchase."
This is the big one. People treat a website like something you buy once and own forever, like a piece of furniture. If we’re going to go with a similar analogy it’s more like a car (and yes, it’s a cliche but that’s because it’s a good analogy). At the end of the day though, a website is software. It's a certain kind of application, and like all software, it needs maintenance, mostly for security, but also because business needs and goals change.
A website is meant to be a living, breathing thing that changes along with your business. If it just sits there for five years, it ages, and not always gracefully. And when people are looking for businesses like yours, make no mistake, first impressions matter.
This is why a period of post-launch support should be included with the vast majority of website projects. It gives you time to settle in with the new site and get a feel for what ongoing support actually looks like. After that window, you can either take it from there or arrange an ongoing support and maintenance plan. Some businesses decide they don't need ongoing maintenance, and that's a legitimate choice, but it should be a choice you make on purpose, not something you realize after your site breaks or needs major security updates.
"Content and copywriting are included."
Sometimes it’s assumed the designer or developer will write the words. That's not a given especially since writing isn’t necessarily their specialty. Copywriting is a separate service, frequently handled by a professional copywriter. Many clients choose to write their own copy because hiring one reads as an added expense. But if you believe it’s just another expense, I’d ask you to re-think that framing.
Copywriting isn't a line item to trim, it's often what makes or breaks a website's ability to help a business sell. The words are what actually persuade a visitor to stay, to trust you, and to act. Great design gives those words the best possible stage, but the words still have to carry their weight. It's worth thinking of professional copy as an investment in the site's results rather than an expense tacked onto the project.
Either way, "design" doesn't automatically mean "someone else writes your content," so clarify who's responsible for the words before you start.
"A website will bring in customers on its own."
A website is a tool, not a magic switch. It works best as part of a larger picture: your marketing, your outreach, your reputation, all the things that actually drive people to it. On its own, a site can't manufacture demand that isn't being generated somewhere. A great website makes it far more likely that the people who do find you will trust you and take action, but something still has to send them there in the first place.
"More pages and more features make a better site."
Usually it's the opposite. Focus and clarity beat sheer volume. Every extra page and every extra feature is one more thing to maintain and one more thing that can distract a visitor from making a purchase or contacting you. The goal isn't to build the biggest site, it's to build the right one. A tight, well-considered site that says exactly what it needs will outperform a sprawling one nearly every time.
"I'll be able to change anything myself after launch."
You'll be able to manage your content through the CMS, updating text, swapping images, adding a blog post, and so on. That's what a CMS is for. But structural or design-level changes are a different kind of task, and those typically aren't something you'll handle yourself (nor should they be). It's worth understanding where that self-service line sits before launch, so you know what's a quick edit on your end versus what's a conversation with your developer.
"SEO means I'll rank number one right away."
Basic SEO builds a strong foundation, and it should absolutely be part of the process. But ranking is ongoing and competitive, not a switch that gets flipped at launch. Good structure, fast performance, and solid fundamentals put you in a position to compete, but they don't guarantee the top spot. Anyone promising instant number-one rankings is worth a healthy dose of skepticism.
A Few Things Worth Having an Opinion About
Beyond the deliverables, a lot of what's "included" comes down to how a studio chooses to work. Here are a few things worth understanding, and worth asking any designer about, because they directly affect what you get.
Fixed Prices vs. Hourly
Plenty of studios, mine included, price projects based on scope and value rather than the clock, and there's a good reason. Hourly billing has a quiet problem: it's just trading time for money, and it tends to ignore experience even at higher hourly rates. Someone with fifteen or twenty years behind them has seen the problems, the approaches, the dead ends, and they’ve built up their own processes and methodologies, so they solve things faster. On an hourly model, that experience actually works against them, because doing the job well and quickly earns less than doing it slowly. Fixed pricing means you're paying for the outcome and the expertise that produces it, not for how many hours it happened to take.
A Defined Number of Revisions
A clear number of revision rounds, rather than a vague promise of "unlimited," serves everyone better. A defined space to refine the work gives both sides a shared understanding of what you're working toward, and that focus is what makes the refinements count. Instead of endlessly circling, you sharpen the work you agreed on until it's genuinely excellent. If you need more revisions, or you want to expand what the site does, that's almost always possible, it just becomes part of the conversation, with the time and budget accounted for openly. The point isn't to limit you. It's to keep the project focused enough that every round of feedback moves the work forward rather than sideways.
A Partnership, Not an Order Taker
This is the one I feel most strongly about. Some clients just want someone to execute exactly what they ask, and that's a valid way to hire. But it's not the way Block 81 works, and honestly it's not what a good designer or developer does.
A partnership-oriented designer or developer brings their experience and expertise to your project with intention. They look at your site from the user's perspective. They propose approaches you may not have considered. Even if you don't take a suggestion, it gives you something to weigh, it either reinforces the instinct you already had or offers you a better path. That's value you don't get from an order taker, and it changes the final result, because you end up with more than you walked in expecting.
What a Smart Client Should Look For
If you want to make sure what's "included" is substantial and not hollow, here's what's worth paying attention to.
Look for a designer who brings their own ideas to the table, who proposes solutions and draws on what they've seen work before. That willingness to contribute thinking, rather than just take orders, is the clearest green flag that someone cares about your outcome and not just shipping a deliverable.
Then ask whether the fundamentals are baked into every step of the process, not bolted on at the end:
- Basic SEO. Is the site built to be found? And increasingly, this extends beyond traditional search into optimizing for AI-driven answers and agents. Ask how that's being considered.
- Accessibility. This matters more every year. A site that excludes people isn't a finished site.
- Performance. How fast the site loads and responds. Speed is part of the experience, not a nice-to-have. And it matters for search engine ranking.
- User experience. Does the site make sense for the people who'll actually use it? Remember that your visitors will use your website far more than you ever will, so it has to work for them first.
If a studio treats SEO, accessibility, performance, and UX as integral rather than optional extras, you're probably in good hands. If those things only show up as upsells at the end, that tells you something too.
The Bottom Line
"Web design services" should mean a thoughtful, structured process that leaves you with a real, functioning website you can manage, built on a solid content structure, and the fundamentals that make a site genuinely work for your organization. Not just a nice-looking shell. Not a one-time transaction you never think about again.
The best thing you can do as a client is ask. Ask what's included. Ask who owns what. Ask what happens after launch. Ask whether strategy is part of the deal or just execution. A good studio will have clear answers, and will probably be glad you asked.