The growth-driven design proposal: how to scope, price, and sell GDD projects

Project phasing. Break the engagement into distinct phases with separate approval gates. The standard phases are messaging/strategy, design direction, development, and ongoing optimization. Each phase should have its own deliverables, timeline, and price so the client can commit to one phase at a time.

Page-level scope. Identify which pages get premium custom treatment and which use templated layouts. Most B2B websites have 10 to 15 pages doing 80%+ of the work. Your proposal should name those pages explicitly and explain why they matter more than the 40 sub-pages that get minimal traffic.

Pricing structure. Phase-by-phase pricing with clear deliverables at each stage. More on this below.

Timeline. Specific week ranges for each phase. A full GDD engagement from strategy through launch typically runs 9 to 13 weeks, with ongoing optimization after that.

Risk mitigation. How you reduce the client's risk of committing to the full engagement. This is where pilot phases, guarantees, and phased commitments do the heavy lifting.

VIDEO TRAINING

Get the Growth Playbook.

Learn to plan, budget, and accelerate growth with our exclusive video series. You’ll discover:

• The 5 phases of profitable growth
• 12 core assets all high-growth companies have
• Difference between mediocre marketing and meteoric campaigns

How should you structure pricing in a GDD proposal?

GDD pricing should be modular and phase-based, not a single lump sum. The total investment for a full GDD website build typically ranges from $15,000 to $70,000+, but no client should see that number without understanding what each piece costs independently.

Here's how the phases typically break down:

At Lean Labs, we use a tiered model for the design blueprint phase that gives clients control over their investment level:

The advantage of this structure for agencies: you're not negotiating one big number. You're helping the client choose a starting point. Most clients pick the middle tier because it feels like the rational choice between "too basic" and "more than I need right now."

For buyers evaluating proposals: if an agency gives you a single $50K quote with no phase breakdown, that's a red flag. You're being asked to commit to everything before seeing anything.

How do you scope a GDD project without scope creep?

Scope creep in GDD almost always comes from one place: not understanding which pages actually matter. When every page gets treated as equally important, the project expands to fill whatever budget and timeline exist. The fix is ruthless page prioritization.

Start with analytics. Pull the traffic and conversion data for every page on the current site. You'll typically find that 5 to 10 pages account for the vast majority of meaningful traffic and conversions. Those are your premium pages. Everything else gets a templated layout that follows the design system established by the premium pages.

Your proposal should include a page inventory with three tiers:

Premium pages (custom design and copy). These are the homepage, core service/product pages, and primary conversion pages. Each gets unique layout, custom messaging, and dedicated design time. Typically 5 to 10 pages.

Standard pages (templated layout, custom copy). About/team pages, secondary service pages, resource hubs. These use the design system and templates established by the premium pages but get tailored copy. Typically 10 to 20 pages.

Basic pages (templated layout and content structure). Blog posts, knowledge base articles, legal pages. These use standard templates with minimal customization. Could be dozens or hundreds of pages.

When a client asks to add pages mid-project, you point back to this framework. "That page gets 200 visits a month. It fits the standard tier. Here's what that costs to add." No ambiguity, no emotional negotiation about whether a page is "important enough."

We've found that this page-tier model eliminates about 80% of the scope conversations that derail traditional web projects. The client understands why their CEO's favorite sub-page doesn't need the same treatment as the homepage, because the data makes the argument for you.

What's the best pricing model for GDD: hourly, fixed, or value-based?

Fixed-price per phase is the strongest model for GDD engagements. Hourly billing punishes efficiency and creates adversarial dynamics. Pure value-based pricing is theoretically ideal but practically difficult to implement unless you have deep trust with the client and reliable baseline metrics.

Here's how each model plays out in practice:

The phase-based fixed model works best for initial GDD builds because it gives the client price certainty while giving you margin upside when your process is dialed in. You're not billing for hours. You're billing for outcomes at each phase: a messaging framework, a design direction, a launched website.

For the ongoing optimization phase, a hybrid works well. Charge a fixed monthly retainer for a defined scope of work (number of experiments, pages optimized, reports delivered) with the option to layer in value-based bonuses tied to conversion improvements. This keeps the base predictable while rewarding you for producing real results.

How do you sell GDD instead of a traditional website redesign?

The biggest mistake agencies make when selling GDD is leading with methodology. Clients don't care about your process. They care about reducing risk and getting to value faster. If your pitch leads with "here's our methodology," you've already lost their attention.

Sell the pilot, not the project. The most effective GDD sales approach is an escalation model: start with a small, low-risk engagement that proves your value, then expand from there.

At Lean Labs, we think of it as an appetizer model. The first engagement is a design blueprint, a 4-week sprint that costs $6,000 to $12,000 and produces a tangible deliverable: a fully designed key page that establishes the visual direction for the entire site. The client sees real work, evaluates the quality, and decides whether to continue. No multi-month commitment required upfront.

We describe this internally as "drive, watch, graduate." In the early phases, we drive while the client watches. As we move into optimization and ongoing work, they drive while we watch. Eventually, they've built the internal capability to maintain and improve the site on their own. That framing resonates because it positions the engagement as building capability, not creating dependency.

For agencies building their own GDD offering, here's the escalation model that works:

1. Paid discovery or messaging sprint ($3,000-$12,000). Low commitment, high value. Produces a deliverable the client keeps regardless of whether they continue. This replaces the free proposal or unpaid pitch.
2. Design direction phase ($6,000-$12,000). A focused sprint that proves your design capability on one key page. Client approves the visual direction before you build anything.
3. Scoped build ($10,000-$25,000+). Development of the approved design into a live site. Scope is already locked because the client approved the direction.
4. Ongoing optimization (~$5,000/month). Monthly retainer that only starts once the site is live and generating data.

Each step gives the client a natural off-ramp. Counterintuitively, this makes clients more likely to continue because they never feel trapped. The agency that says "sign a $60K contract and we'll start in two weeks" loses to the agency that says "let's start with a $6K design sprint and see if we're a good fit."

FREE GROWTH TOOL: AI GROWTH GRADER

Identify your growth roadblocks

Get 3 FREE AI-Powered reports that reveal what’s costing you leads, conversions, and revenue. Then, get expert insights for how to fix it.

• Marketing maturity score:  Find out where your strategy is weak (and how to fix it).
• Website copy critique: Pinpoint the weak points in your messaging (and what to say instead).
• Landing page audit: See what's blocking conversions on your landing pages (and how to solve it).
  

Get your growth score now – FREE!

How do you handle risk reversal in a GDD proposal?

Risk reversal is the single most effective element you can add to a GDD proposal. When the agency absorbs more of the risk, the client's decision gets easier.

At Lean Labs, our approach is called "No Yay, No Pay." If the client isn't happy with the design blueprint within the first three weeks, they get a full refund. That's not a satisfaction guarantee buried in fine print. It's the lead offer. We put it on the first page because it reframes the entire buying decision from "should I risk $50K on this agency?" to "should I spend $6K to find out if this agency is right for me, knowing I can get it back if they're not?"

The structural elements that make risk reversal work in GDD proposals:

Phase-gated commitment. The client only commits to the next phase after approving the current one. They never pay for work they haven't evaluated.

Tangible deliverables at every stage. Even if the engagement ends after phase one, the client walks away with something useful: a messaging framework, a design direction, a style tile. There's no sunk cost because each phase produces standalone value.

Paid in the rears, not upfront. Billing after delivery rather than before it shifts the risk to the agency. It signals confidence in your own work. If you can't afford to do this, it may signal that you're not confident enough in your delivery to back it up.

Money-back window. A defined period where the client can walk away with a full refund. This only works if the window is early enough that you haven't invested heavily in delivery. A three-week window on a four-week design sprint is aggressive but effective because it forces you to front-load the impressive work.

For agencies: risk reversal isn't charity. It's a conversion tool. We've found that offering a genuine guarantee increases close rates enough to more than offset the occasional refund. And "occasional" is the key word. When your process is strong, almost nobody takes the refund.

What separates a good GDD proposal from a bad one?

A good GDD proposal reads like a roadmap. A bad one reads like a menu of services with prices attached. The difference is whether the client finishes reading and thinks "I understand exactly what happens next" versus "I still don't know what I'm actually getting."

Signs of a strong GDD proposal:

• Names specific pages and explains why they were prioritized
• Shows phase-by-phase pricing so the client can enter at their comfort level
• Includes a clear timeline with milestones and approval gates
• Addresses what happens if the client isn't happy at any stage
• Defines what "done" looks like for each phase
• Explains the ongoing optimization model and when it starts

Signs of a weak GDD proposal:

• Bundles everything into one price with no phase breakdown
• Uses vague language like "up to 20 pages" without specifying which ones
• Focuses on process methodology instead of client outcomes
• Has no risk mitigation or guarantee language
• Treats the proposal as the final scope document rather than a starting point for collaboration

One detail that's easy to overlook: include a budget planning tool or calculator that helps the client see how different scope choices affect cost. When the client feels like they're building the budget alongside you rather than receiving a number from above, they're far more likely to move forward.

How much should you charge for a GDD proposal itself?

If you're giving away proposals for free, you're doing it wrong. The proposal phase in GDD should be a paid engagement because it produces real strategic value.

The industry is split on this, but the agencies winning the most GDD work have moved to paid discovery. A messaging sprint or strategy engagement ($3,000 to $12,000) replaces the traditional free proposal. The client gets a deliverable they own. You get compensated for strategic work. And the dynamic shifts from "pitch me for free and I'll decide" to "let's invest together in understanding the problem before we commit to a solution."

At Lean Labs, the design blueprint serves this function. It's not a proposal. It's the first phase of the project, and it produces a Figma mockup, a style tile, and a full visual direction that the client can take to any developer if they choose not to continue with us. That's a meaningful deliverable, not a sales document dressed up as strategy.

For agencies that aren't ready to charge for discovery: at minimum, keep your free proposal short. Two to three pages maximum. Save the detailed scoping, page inventories, and strategic recommendations for the paid phase. The free proposal should answer two questions: what are the phases and what does each cost? Everything else is work you should be paid for.

How does GDD proposal structure differ by client size?

The core structure stays the same, but the emphasis shifts based on the buyer.

For startups and small businesses ($15K-$30K total budget). Lead with the messaging sprint and design blueprint as standalone deliverables. These clients often can't commit to a full build upfront, but they can invest $9K-$18K in strategy and design direction, then bring those assets to a developer. Your proposal should make it clear that each phase produces value on its own.

For mid-market B2B companies ($30K-$70K total budget). This is the core GDD buyer. Your proposal should cover all four phases with detailed page-level scope. Emphasize the escalation model and phase-gated commitment. These buyers have been burned by traditional redesigns before and respond strongly to risk reversal language.

For enterprise and larger organizations ($70K+ total budget). The proposal needs to address stakeholder alignment, governance, and integration complexity. Enterprise buyers care less about the total price and more about predictability, timeline, and internal approval processes. Build in more discovery time and plan for longer approval cycles between phases.

Regardless of client size, the principle is the same: make it easy to say yes to the first phase and let your work sell the next one. A $6,000 design blueprint that impresses a VP of Marketing will close the $40,000 development phase faster than any proposal document ever could.

Common mistakes when writing GDD proposals

Promising specific traffic or conversion outcomes. You can share benchmarks and case studies, but guaranteeing "300% increase in leads" in a proposal creates an expectation you can't control. Promise the process and the methodology. Let the data speak for results during the optimization phase.

Underpricing the strategy phase. Agencies often discount or give away the messaging and strategy work to win the build contract. This devalues the most important phase of GDD and trains clients to expect strategic thinking for free. If your messaging sprint isn't worth paying for on its own, it probably isn't rigorous enough.

Overcomplicating the document. A 30-page proposal signals that you're trying to justify your price through volume rather than clarity. The best GDD proposals we've seen are 5 to 8 pages. Phase breakdown, page scope, pricing table, timeline, guarantee, next steps. Everything else is noise.

Skipping the budget conversation. Too many proposals arrive as a surprise number. Use a budget planning calculator or a scoping call to arrive at the budget together before the proposal lands. When the client already knows the number, the proposal is a formality. When the number is a surprise, the proposal is a gamble.

Ignoring the 95% who need positioning work first. Most companies that come to an agency for a website redesign actually have a messaging problem, not a design problem. If your proposal jumps straight to design and development without addressing messaging and positioning, you're building a pretty house on a shaky foundation. We've found that roughly 95% of the companies we talk to need some level of positioning work before design makes sense. Build that into your default proposal structure.

Related resources

• How much does growth-driven design cost?
• Growth-driven design vs. traditional web design
• How much should a website design cost?
• Hourly vs. fixed price vs. value billing
• Why Lean Labs