Reaching out to a web design agency is one of those business decisions that can feel bigger than it should.
You might know your website needs attention.
You might even have budget set aside.
But there’s still that hesitation before the first message goes out – usually because you’re not sure what happens next, how quickly things move, or whether you’re about to be dragged into a heavy sales process.
In reality, the early stages are usually far more practical than people expect. A good agency wants to understand what you’re trying to achieve, what’s getting in the way, and whether a new website is genuinely the right move.
Below is a clear breakdown of what typically happens from first enquiry through to kickoff – and what you can do to make the process smoother on both sides.
🔑 Key Takeaways
- The first conversation is usually scoping, not selling
- Agencies need clarity on goals, audience, and functionality before quoting accurately
- A proper discovery stage prevents expensive rebuilds and drifting timelines
- Good proposals define deliverables, responsibilities, and what happens after launch
- Sometimes the best advice is to fix fundamentals before rebuilding the whole site
🧭 Jump to:
The initial enquiry
The first contact is usually straightforward. Most enquiries come through a form, email, referral introduction, or a quick phone call.
At this stage, an agency is generally trying to work out three things:
- What the business does (and who the website needs to speak to)
- What the website needs to achieve (enquiries, sales, bookings, recruitment, credibility, lead capture)
- What type of project this is (new build, redesign, ecommerce, or improvement work)
If the enquiry is vague, a good agency will ask follow-up questions rather than guessing. That’s a positive sign – it usually means they’re trying to scope things properly before discussing costs.
If you’re contacting Media Village, the goal of the early conversation is simple: understand the situation, identify the quickest path to a better outcome, and confirm whether we’re the right fit.
What a good first conversation should feel like
A useful first conversation should feel more like a diagnostic discussion than a sales pitch.
The goal at this stage is to understand the situation before suggesting solutions. That means asking questions about goals, customers, constraints, and what the current website is actually doing.
If a conversation jumps straight to pricing without exploring context, the advice is unlikely to be accurate. Websites only work well when they’re built around clear commercial objectives rather than assumptions.
The discovery call
This is where the real clarity begins. A discovery call is rarely about features in isolation. It’s about context.
Expect questions like:
- What’s working currently? (and what isn’t)
- Who is the customer? (and what convinces them to take action)
- What does success look like? (more leads, higher quality leads, better conversion rate)
- What’s the current website doing? (traffic, enquiries, drop-off points)
- Are there technical constraints? (platform, plugins, integrations, hosting)
This stage is also where you’ll get an early sense of how the agency thinks. Do they talk about outcomes and structure, or do they jump straight to visuals?
If your current site gets traffic but doesn’t convert, this is usually the point where the conversation becomes more commercial. (This links closely to why websites get traffic but no enquiries.)
Scoping and requirements
After the discovery call, the agency will usually translate what you’ve shared into a scope. This is where the project becomes real.
A good scope typically includes:
- Site structure (key pages, user journeys, priorities)
- Functionality (forms, ecommerce, booking, membership, integrations)
- Platform (WordPress, Shopify, bespoke builds, or other approaches)
- Content requirements (new copy, rewriting, photography, video)
- SEO considerations (migration, redirects, architecture, internal linking)
Some agencies include a light strategy stage here, especially if the project needs more thinking before design begins. If that’s the case, it’s usually a good sign the work will be structured properly. (We cover this thinking in how we plan website structure before design.)
Proposal, budget, and next steps
Once the scope is clear, the agency can put forward a proposal that outlines what you’re getting, what the process looks like, and what the investment typically is.
At this stage, many businesses also ask about budget expectations. While exact pricing varies depending on scope, functionality and content requirements, early guidance usually helps confirm whether the project direction is realistic before deeper planning begins.
A strong proposal should include:
- Project stages (discovery, design, development, testing, launch)
- Deliverables (what’s included and what isn’t)
- Timeline guidance (with realistic dependencies)
- Responsibilities (what the agency needs from the client, and when)
- Post-launch options (support, improvements, ongoing optimisation)
If you’re comparing agencies, this is also the moment where the differences become obvious. Some proposals are glossy but vague. Others are clear and operational.
If you’re still deciding what type of site you need, brochure vs ecommerce website is a useful starting point.
Typical web design agency process
| Stage | What happens | Purpose |
|---|---|---|
| Initial enquiry | First contact via form, email or phone | Understand the basic project context |
| Discovery conversation | Discussion around goals, audience and current website issues | Clarify what the website needs to achieve |
| Scoping | Agency defines structure, functionality and technical requirements | Translate ideas into a workable project plan |
| Proposal | Timeline, deliverables and estimated investment shared | Allow both sides to confirm fit |
| Project kickoff | Planning, design and development phases begin | Move from planning to execution |
Kickoff and early project stages
If you move forward, the project usually starts with a kickoff meeting. This is where timelines become more concrete, responsibilities are agreed, and the agency begins collecting what it needs to build properly.
In most projects, the early stages look something like:
- Kickoff and asset collection (logins, brand materials, access, existing data)
- Structure planning (site map, page priorities, conversion journeys)
- Wireframes (layout planning before final design)
- Design development (visual direction and page designs)
- Development (build, CMS setup, responsiveness, integrations)
- Testing and refinement (speed, usability, cross-device checks)
- Launch (go-live plan, redirects if needed, tracking checks)
One common misconception is that “design” is the first step. In practice, structure and content clarity usually dictate how effective the design will be.
If you want a better idea of what happens next, what happens after a website launch breaks down how performance improvements typically unfold.
Timeline expectations
Timelines depend heavily on scope, but delays are usually caused by the same predictable issues:
- Content not ready (copy, imagery, approvals)
- Scope changes mid-project (new pages, new functionality)
- Stakeholder bottlenecks (waiting on decisions)
- Legacy technical constraints (poor hosting, unstable plugins, messy builds)
This is why a structured discovery stage matters. It reduces surprises and prevents the project drifting into a vague “we’ll figure it out as we go” approach.
In many projects, delays actually happen on the client side rather than the development side, usually because content approvals or internal decision-making takes longer than expected.
Timeline and cost are also closely linked. Larger websites with custom functionality require more planning and development time. Our guide to website costs in the UK explains the main factors that influence project investment.
If you’re planning around a specific deadline, it’s worth reading how long it takes to build a website for realistic expectations.
When a new website isn’t the right move
Not every enquiry results in a project – and that’s often a good thing.
Experienced web design and development agencies occasionally advise businesses not to proceed with a full rebuild yet, especially if the underlying issue lies elsewhere.
Common examples include:
- Low or inconsistent traffic, where marketing or SEO activity needs attention before a rebuild will deliver meaningful results
- Messaging and positioning issues, where the site could improve through better copy and structure rather than a full redesign
- Unrealistic timelines that make it difficult to deliver quality and test properly
- Unclear project goals, where the website needs strategic thinking before development begins
In these situations, a responsible agency will explain the risks openly rather than pushing ahead with work that may not deliver the best outcome.
Sometimes that means a smaller step first – improving messaging, refining conversion paths, fixing tracking, or resolving technical constraints – then revisiting the rebuild once the foundations are in place.
What to send in your first message
If you want to speed up the process, there are a few details that help immediately. You don’t need a perfect brief, but a little structure goes a long way.
Include:
- A link to your current website
- What you want the website to achieve (leads, sales, credibility, bookings)
- Any specific issues (slow speed, low conversions, hard to update, poor mobile experience)
- Examples of websites you like (for style and user experience)
- Any non-negotiable functionality (booking, ecommerce, memberships, integrations)
- Rough timing (ideal launch month, key deadlines)
If you’re not sure how to structure this, how to write a website brief breaks it down clearly.
FAQs
These are the most common questions businesses ask when they’re considering contacting an agency but still working out what the process involves.
Do I need to know exactly what I want before contacting an agency?
No. You’ll get better results if you have clarity on your goals, but part of an agency’s role is helping you define structure, requirements, and priorities. The early conversations exist to bring clarity.
Will I get a quote in the first call?
Sometimes you’ll get early guidance, but accurate pricing usually requires proper scoping. If an agency quotes immediately without understanding requirements, that figure is rarely reliable.
What’s the difference between a redesign and a rebuild?
A redesign usually focuses on visuals and layout. A rebuild often involves changes to structure, content, CMS setup, and underlying technical architecture. If performance is the goal, structure matters as much as design. This guide to redesign vs updates can help.
What if we don’t have content ready?
This is common. Agencies can often help with copywriting, photography, and content planning, but missing content is one of the most common causes of delays. If content is likely to be a blocker, it’s best to raise it early.
What happens after the website goes live?
Launch is the start of the performance phase. Tracking, iteration, conversion improvements, and SEO compounding typically happen in the weeks and months that follow. Here’s what that usually looks like.
Next step
Contacting a web design agency doesn’t need to feel like a big commitment. The early stages are usually about clarity, fit, and identifying the right approach before anyone talks about timelines and deliverables in detail.
If you’re exploring a website project and want a clear view of what might be involved, we’re happy to have an initial conversation and point you in the right direction.
👉 If you’re considering a new website or a rebuild, explore our website design and development services to see how we approach structure, clarity, and performance from the start.
