What 'It's a Simple Website' Really Means

Every freelance web designer eventually develops the same reflex. The moment a client says “it’s just a simple website,” your stomach tightens.

You smile and nod. You ask follow-up questions. You take notes. But inside, you’ve already added 40% to your mental estimate. Because “simple” never means simple.

This isn’t a joke. It’s the most reliable predictor of project complexity in the freelance web design industry. The clients who describe their projects as simple are almost always describing something complex. The translation problem is structural: the client and the designer mean different things by “simple.”

Here’s the translation guide. And here’s how to scope around it before it becomes a problem.

What “simple” means to a client

When a client says their project is simple, they’re usually describing one of these:

A small page count. “Just 5 pages.” From the client’s perspective, 5 pages is simple because the deliverable feels small. They’re not thinking about how each of those pages needs to be designed, written, tested, and optimized.

Familiar functionality. “Just like Squarespace.” From the client’s perspective, the product exists, so building something like it is a known quantity. They’re not thinking about the years of engineering work that went into Squarespace.

Their internal sense of urgency. “We just need something quick.” This is less about complexity than about timeline. The client doesn’t want a long process. “Simple” here means “fast.”

Limited budget. “Something simple should be cheap, right?” The client is trying to anchor the price low by labeling the project as minimal.

Unfamiliarity with web design. “I just need a website.” For a client who’s never had one, the entire concept feels simple because they don’t know what it involves.

The common thread: “simple” describes how the client wants to feel about the project. Not the actual scope of the work.

What “simple” actually requires

Let’s take the canonical “simple” project: a 5-page website for a small business.

What’s actually involved:

Design phase.

• Discovery and brief
• Information architecture (sitemap, page hierarchy, content prioritization)
• Wireframes for each unique page template
• Visual design for each unique page template
• Style guide (typography, colors, components)
• Responsive design considerations for mobile, tablet, desktop
• Two rounds of revisions

Build phase.

• CMS setup (WordPress, Webflow, or framework of choice)
• Template implementation for each page type
• Content integration (copy, images, video)
• Responsive testing across breakpoints
• Cross-browser testing (Chrome, Safari, Firefox, Edge)
• Performance optimization (images, scripts, fonts)
• Basic SEO setup (meta tags, sitemap, robots.txt)
• Form integration (contact, newsletter)
• Analytics setup

Pre-launch phase.

• Accessibility audit
• QA across devices
• Stakeholder review and approval
• DNS and hosting setup
• SSL certificate
• Final content review
• Backup and migration plan

Launch phase.

• Site migration to production
• DNS cutover
• Post-launch monitoring
• Documentation handoff
• CMS training for the client

That’s the actual checklist for a “simple” 5-page site. It’s at minimum 30 hours of work for an experienced freelance designer, often 50-70 hours for a designer still building their efficiency.

The client thought it was a weekend project. It’s actually 4-6 weeks of focused work.

The translation table

Here’s how specific client phrases translate into actual scope, in my experience.

Client says	Actually means
”Just a simple 5-page website”	30-50 hours of work across 4-6 weeks
”Just like [competitor’s site]"	"Build me a site that took a team 6 months in 4 weeks"
"Just a quick refresh”	Full redesign, but they want it priced like a coat of paint
”Just basic e-commerce”	At minimum 60 hours additional for cart, checkout, and product management
”Just a contact form”	Form + spam protection + email routing + CRM integration
”Just a booking system”	Calendar integration + payment processing + email confirmations + admin dashboard
”Just integrate with [tool]“	Investigate the API, build the integration, test edge cases, document
”Just a few revisions”	Unlimited revisions unless your contract is specific
”Just keep it simple”	Don’t show me your design process; make me feel smart about my decisions

Almost every “just” is hiding 10-30 hours of work. The pattern is so consistent that you can use it as a pricing rule: every “just” in a client’s project description adds 25% to your mental estimate.

The scoping conversation that prevents disasters

When a client says “it’s a simple project,” your next move determines whether the project goes smoothly or becomes a months-long scope dispute.

Don’t agree. Don’t disagree. Ask questions that surface the actual scope.

“What does ‘simple’ mean to you in terms of timeline?” Their answer reveals their urgency anchor. If they say “two weeks,” you know they’re underestimating dramatically. Now you can have an honest conversation about realistic timeframes.

“What are the must-have features for launch versus the nice-to-haves?” This surfaces the functionality they’re imagining without realizing it requires real work. The client who says “we just need a contact form… oh, and a booking calendar… and we should probably take payments through it” has a 60-hour project they thought was a 10-hour project.

“Are you providing the content, or do you need help with it?” Content gaps are the #1 cause of project delays. If they say “oh, I’ll write it” but don’t have a content strategy, the project will stall after week two.

“Who else needs to approve the design?” “Just me” often turns into “well, my business partner has thoughts” three weeks in. Surface the stakeholders before you start.

“What’s the budget range you have in mind?” Their answer relative to your standard pricing tells you whether the project is realistic or whether they have wildly underestimated the scope.

These five questions take 10 minutes on a discovery call. They prevent every “wait, that’s not what I meant by simple” conversation that would otherwise happen in week three.

How to price the “simple” project

Once you understand what’s actually involved, the pricing conversation gets easier.

Build a quote that reflects the real work. The breakdown should be visible, with line items the client can understand:

Base 5-page website: €3,500

• Design and brief
• 5 page templates (Home, About, Services, Portfolio, Contact)
• Responsive design
• CMS integration (WordPress)
• 2 rounds of revisions
• Basic SEO setup
• QA and launch

Add-ons (selected):

• Custom contact form with spam protection: €400
• Newsletter integration (Mailchimp): €300
• Google Analytics setup: €200
• Accessibility audit (WCAG AA): €1,200

Total: €5,600

Timeline: 5 weeks from kickoff to launch.

The client sees that “just a simple website” actually has multiple components. They can choose which add-ons to keep. They can see why the timeline isn’t two weeks.

Most of the “wait, why is it so expensive?” pushback goes away when the breakdown is visible. The client wasn’t trying to get a deal. They just didn’t understand the scope.

When the budget doesn’t match the reality

Sometimes the breakdown reveals a gap. The client wanted a €1,500 project. The actual scope is €5,500. What do you do?

You have three real options.

Option 1: Reduce the scope to match the budget. “If €1,500 is the target, I can deliver a 3-page site with a basic contact form, no e-commerce, no booking system, and you provide all the content. That’s a tighter version of the project but it fits the budget.”

Option 2: Refer them to someone cheaper. “It sounds like the budget is below what I work with, but I can refer you to [designer name] who works in your range. They do good work and might be a better fit.” This builds goodwill and protects your time.

Option 3: Decline politely. “Based on the scope and budget, this isn’t going to be the right fit. If your budget changes or you’d like to revisit the scope, happy to reconnect.”

What you don’t do: discount your work to make their budget fit. The “simple project” at half-price becomes a draining, resentment-filled engagement that produces a result you can’t put in your portfolio.

The clients who don’t fall into this trap

Some clients describe their projects accurately from day one. “We need a 5-page website with e-commerce for 30 products, multi-language support for German and English, and integration with our existing CRM. Our budget is €8,000-€12,000 and we need it by November.”

These clients are gold. They’ve thought through the project. They know roughly what it should cost. They have a realistic timeline.

If you find one, treat them well. They’ll refer other clients like them. The freelance designers who run sustainable businesses are usually serving more clients like this than the “just a simple website” type.

The way to attract more of them: be specific in your own materials. If your website says “I build websites for small businesses,” you’ll attract every “just a simple website” inquiry. If your website says “I build 5-25 page websites for B2B service businesses with budgets of €5,000-€15,000,” you’ll attract clients who can describe their project accurately because they’ve already self-selected as matching your offer.

Niching down attracts the clients who don’t say “simple.”

The reframe

A client saying “it’s a simple website” isn’t a problem. It’s a starting point.

It’s a client telling you they don’t yet know what their project actually involves. Your job is to translate their fuzzy mental picture into a defined scope, walk them through the implications, and either book them at a price that reflects reality or refer them to someone who fits their budget.

Done well, this conversation makes you look more professional, not less. The client appreciates someone who can explain why the simple project isn’t as simple as they thought. That perceived expertise is worth more than the discount they were hoping to negotiate.

When the next inquiry calls their project “simple,” smile. You know what to do.

---

debrieft turns every “simple website” conversation into a structured intake form. The client answers specific questions, and the AI generates a brief that surfaces real scope before any quote gets written. Your client gets a portal. You get a dashboard. Both in sync. Try it free at debrieft.app