What Should an Agency Know Before the First Meeting?

A first agency conversation should clarify the problem — not prove you already solved it. You do not need a finished sitemap, final copy, a locked CMS choice or a complete website brief before you talk. You need enough context for the meeting to be useful.

This article is about buyer preparation for an initial conversation. It is earlier and lighter than a formal brief, lighter than discovery, and separate from how proposals document commitment.

Why “now” matters more than the solution

Be ready to say what triggered the project. Competition shifted. Sales complains the site does not explain the offer. Hiring needs a better career path. A redesign is overdue. Inbound leads stall. Something changed — or something stopped working.

“We need a new website” is a tactic. “Prospects leave without understanding who we help” is a problem. Agencies ask better questions when the trigger is clear.

What is not working commercially

Name the friction in business language: wrong inquiries, slow handoffs, buried services, mobile forms that fail, pages sales never sends, trust that never builds. You do not need analytics screenshots for every claim — honesty beats theatre.

If you do have Search Console, CRM or call notes that show the pattern, bring them. If you do not, say so. Unknown is useful information.

What the website should help do

Be explicit about the job: generate leads, explain complex services, support sales conversations, book meetings, recruit, enable self-service — or a ranked mix. “Look modern” is not a job. Knowing the job keeps the first meeting from becoming a preference tour of colours and layouts.

Who it is for

Name the primary audiences and what each needs to understand or do. If buyers and candidates share the homepage, say that. Vague “everyone” answers produce vague advice.

What already exists

A short inventory is enough:

• Current site (or none)
• Content that can be reused vs rewritten
• Analytics and CRM access (or who owns them)
• CMS, hosting, booking tools, forms
• Brand assets and constraints

You are not building the project plan yet. You are helping the agency ask accurate questions about migration, integrations and content capacity.

If organic visibility exists, mention important URLs you care about protecting — even roughly. You do not need a migration map; you need to flag that SEO equity is part of the conversation before anyone proposes a clean-slate rebuild.

Constraints and who decides

Timeline pressure, seasonal launches, legal review, limited subject-matter experts, budget posture where you are comfortable sharing it, and who can actually approve a next step — these change the conversation more than most design preferences.

One decision owner with named contributors beats a committee that “all need to be happy.” If marketing and sales disagree about lead quality, put that tension on the table early. Silent conflict resurfaces as revision theatre later.

How to use the first meeting

Arrive ready to describe the problem and leave ready to decide a next step: deeper discovery, a written brief, a scoped proposal or a polite no-fit. A useful agency will push on constraints and trade-offs. An agency that only presents a portfolio and asks when you want to start is selling theatre.

Take notes on whether they asked about organic URLs to protect, content ownership, CRM handoff and who decides. Those questions signal process quality more than moodboards do.

What you do not need yet

You do not need a predetermined redesign concept, a vendor-selected stack, or a twenty-page PDF. Choosing an agency is still a process question; preparation for the first meeting is simply reducing wasted time for both sides.

A useful first conversation identifies uncertainty. It does not pretend uncertainty is already gone. Bring the problem, the audience, the constraints and the decision-makers — then let web design or website redesign discovery do the interpretive work.