What should happen during a growth-driven website design consultation?

A growth-driven design consultation should end with a clear read on where the current site is losing business and a prioritized first step toward fixing it, not a rendered homepage or a contract to sign [1][2]. The methodology treats a website as a living asset built in phases: a short strategy phase, a fast launchpad build covering only the highest-impact pages, then continuous improvement in time-boxed sprints [3]. The consultation sits at the very front of that sequence, so its job is to collect the raw material the strategy phase will work from, namely measurable goals, genuine audience insight, and the current site's own analytics [1][2]. Visual design and firm pricing come later by design, because the strategy phase is where research into customer needs, journey mapping, and a ranked wish list of improvements actually gets built [1][4].

That framing changes what a productive first meeting feels like. Instead of a creative director presenting concepts, expect a strategist asking questions and pulling up your data, closer to a diagnostic appointment than a showcase [2]. A strong consultation is honest about what it does not yet know: it will not hand over finished strategy conclusions, because the audit of analytics and user feedback that produces them is billable work that runs several weeks in most growth-driven models [2]. What it can deliver is direction. By the end you should understand which pages and metrics the engagement would target first, what the phased timeline looks like, and roughly what the work would cost, framed as a range tied to scope rather than a single fixed number [3][6]. The rest of this answer covers the agenda, the metrics reviewed, the questions worth asking on both sides, what you should walk away holding, and how to separate a diagnostic session from a pitch.

Goals come first, because a website with no defined objective drifts into subjective revision cycles that never resolve [1][4]. A well-run consultation moves through five things in order: business goals, audience and buyer journey, a live look at the current site's data, how ideas will be prioritized, and an agreed next step [1][2][4].

Business goals and success metrics

The meeting should translate "we need a new website" into specific, measurable targets: more qualified leads, a higher demo-booking rate, a shorter sales cycle, whatever the business is actually trying to move [4]. Growth-driven design ties every later decision back to these goals, so a consultation that never nails them down has nothing to prioritize against [4].

Audience and buyer journey

Next comes who the site is for and how they decide. A good partner asks about your best-fit customers, the problems that bring them to the site, and the steps they move through from first visit to purchase, then sketches that journey out loud [1]. This is where persona and jobs-to-be-done thinking enters, because the strategy phase maps content to each stage of that journey [1].

A live look at the data

The consultation should pull up real analytics, not talk about them in the abstract. Reviewing current traffic and conversion behavior is part of the standard strategy audit, and starting it in the first meeting tells you the partner works from evidence rather than assertion [2]. The specific numbers that matter most are broken out in the next section.

How ideas get prioritized

Every improvement idea should be headed for a ranked list, not a build-everything scope. In the model, requirements are ranked by the impact each has on your goals against the time and effort to deliver it, and the first build ships only the top slice of that list [4]. A consultation that collects a long feature request with no ranking mechanism is not applying the method [4].

An agreed next step

The meeting should close on one concrete next action, usually a scoped strategy engagement with a timeline attached, rather than an open-ended commitment [3]. What that next step should and should not look like is covered further down.

A good partner spends most of the consultation asking questions rather than presenting, because the strategy phase runs on the answers [1][2]. The questions cluster around three areas: your goals, your buyers, and what your sales and support teams actually hear.

About goals and what success looks like

Expect direct questions about what the site must achieve and how you will know it worked: which metric matters most, what a good month looks like in numbers, and what a redesign needs to change about the business [4]. These answers become the SMART goals the whole engagement is measured against, so a partner who skips them has nothing to optimize toward [4].

About your buyers and their journey

The partner should dig into who buys from you, what problem sends them looking, and the questions and doubts they carry at each step [1]. Growth-driven strategy builds personas and maps the buyer journey from this input, then designs pages to move visitors from problem-aware to ready-to-buy, so the depth of these questions is a fair proxy for how seriously the partner takes the research [1].

About what sales and support hear

A strong consultation asks to talk to the people who speak with customers every day. Sales and support conversations surface the real objections, questions, and fears a website needs to answer, and pulling that qualitative input into the strategy is part of the empathy research the model calls for [1]. A partner who wants access to your sales team, or to call recordings and support tickets, is planning to build messaging from evidence rather than guesswork [1].

Ask for before-and-after performance numbers from past engagements, not a portfolio tour, because a set of attractive designs says nothing about whether those sites converted [5]. Four questions separate a growth partner from a vendor.

Ask for before-and-after performance data

Ask what specific metrics moved on recent projects, by how much, and over what period: bounce, conversion, leads, revenue [5]. Because growth-driven engagements are built to review performance against goals on a recurring cadence, a genuine practitioner has these numbers and can share them, and an inability to produce any is a signal in itself [2][5].

Ask who does the work and what happens after launch

Ask who will actually be assigned to your account and what the engagement looks like in the months after the site goes live [5]. Growth-driven design treats launch as the start of continuous improvement rather than the finish line, so a partner with no concrete post-launch plan, despite growth-driven positioning, is not really running the method [2][5].

Ask about minimum term, capacity, and pricing structure

Ask about the minimum commitment, the monthly capacity behind the fee, and how pricing is structured [6]. Practitioners put the workable floor at roughly 15 hours or $1,500 to $2,500 per month and treat growth-driven design as a multi-month retainer rather than a one-off build, so a quote well below that should come with a clear explanation of what it can realistically move [6].

Ask which metric the first sprint would target

Ask what the very first improvement sprint would focus on and why [3]. Every sprint in this methodology is built around a single focus metric, so a partner who can name a likely first target has already started thinking diagnostically about your site rather than selling a package [3].

You should walk away with a documented goal set, a candidate focus metric, a first-pass wish list on its way to an implementation plan, a phased timeline, and a rough scope range, not a signed contract [1][3]. The consultation's value is direction, and direction can be written down and checked.

A clear next step

The single most useful thing to leave with is one concrete, low-risk next action [3]. In practice that is usually a scoped strategy engagement rather than a full build commitment, which lets you judge the partner's thinking before committing to the larger cost [5]. A consultation that offers only sign-for-the-whole-project-or-nothing has skipped the phased logic the method is built on [3][4].

A rough scope, not a fixed bid

Expect a scope range tied to what the work involves, not a single fixed number produced before anyone has seen your data [6]. Experienced growth-driven sellers package mid-size engagements as a strategy-plus-launchpad fee with a monthly improvement retainer behind it, so a structure like that, expressed as ranges, is a healthier sign than a precise quote delivered on the spot [6]. A firm price named without a data review is a guess, and you inherit the risk of the guess [2].

A phase map with timeframes

You should also leave with the timeline drawn out: strategy work in roughly 10 to 14 days, a launchpad site live in about 60 to 90 days, then continuous improvement in short, repeating sprints [3]. Timeframes attached to phases let you hold the engagement accountable from week one, and their absence usually means the plan is not really phased [3].