A growth-driven design contract and retainer should define six things: the scope and deliverables across the strategy, launchpad, and continuous improvement phases; a monthly capacity measured in hours or agile points; the focus metric each sprint reports against; ownership of the site and its data; exit and pause terms; and the price floor below which the model stops producing measurable results [8][1][3]. Practitioner guidance puts the workable floor at about 15 hours or $1,500 to $2,500 per month, with survey-reported packages near $3,300, $8,300, and $14,600 per month [1]. Full-service retainers on the open market commonly run $5,000 to $12,500 per month across nine to twelve months, while optimization-only tiers are published as low as $800 per month [2][4]. A complete agreement enumerates deliverables, timeline, pricing, and success metrics the way a standard web development agreement does, then adds a reporting cadence and monthly reprioritization rights so both sides judge progress against evidence [7][2].
\n","summary":"Survey data from 350 agencies, published tier pricing, and open-market retainer ranges show what a workable growth-driven design agreement covers: phase scope and deliverables, a monthly hours or points capacity, a named focus metric with a reporting cadence, ownership of the site and its data, exit and pause terms, and the protections that keep both sides honest, down to the price floors below which the retainer stops moving the numbers.","publishedAt":"2026-07-17T14:26:08.652","verifiedAt":"2026-07-17T00:00:00","editorialStatus":"APPROVED","lastReviewedAt":"2026-07-17T14:26:08.519","nextReviewDueAt":"2027-01-17T00:00:00","templateVersion":"v2","aliases":["what goes into a growth-driven design retainer","GDD contract terms","growth-driven design retainer pricing","what should a GDD agreement include","website continuous improvement retainer scope","GDD engagement minimums","growth-driven design retainer hours","GDD retainer ownership and exit terms","how much does a GDD retainer cost per month","growth-driven design contract deliverables","GDD reporting cadence and focus metric","fractional growth-driven design retainer scope"],"confidenceScore":85,"confidenceLabel":"High","canonicalUrl":null},"contributor":{"id":"dc83f9a1-5273-4639-bffb-43d5fa44c2bf","slug":"lean-labs","displayName":"Lean Labs","websiteUrl":"https://lean-labs.com/","sameAs":["https://lean-labs.com/","https://www.linkedin.com/company/lean-labs"]},"contributorOrganizationProfile":{"entityId":"dc83f9a1-5273-4639-bffb-43d5fa44c2bf","legalName":null,"description":"Lean Labs is a HubSpot Diamond Solutions Partner that helps B2B SaaS startups and scaleups grow through AI-powered marketing services, including lead generation websites, Answer Engine Optimization (AEO), and Loop Marketing. Founded in 2013, the company combines expert strategy with AI agents to deliver scalable, high-ROI growth systems for funded startups from Seed to Series C.","websiteUrl":"https://lean-labs.com/","imageUrl":"https://www.leanlabs.com/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Flogo.0d6c5685.png&w=256&q=75","sameAs":["https://lean-labs.com/","https://www.linkedin.com/company/lean-labs"],"slogan":"Experts at strategy, marketing, design and development augmented by AI","subtitle":"Growth marketing agency ยท HubSpot partner","facts":["Practicing GDD on client sites since 2017","Contributes published answers on 3 topics: Growth-Driven Design, Growth-Driven Design for B2B, Answer Engine Optimization"],"coiNote":"Sells services in this topic. All answers reviewed independently.","foundingDate":"2013-01-01T00:00:00","numberOfEmployeesText":null,"contactPoint":{"email":"hello@lean-labs.com","contactType":"sales"},"address":{"city":"Land O' Lakes","state":"FL","country":"US","postalCode":"34638","addressType":"operational","streetAddress":"16703 Early Riser Ave, Suite 111"},"headquartersText":"Land O' Lakes, FL, US","organizationType":null},"contributorPerson":{"slug":"kevin-barber","displayName":"Kevin Barber"},"sections":[{"id":"f2d40499-6826-4f84-97db-9160fd31c3d0","sectionKey":"overview","sectionType":"markdown_section","heading":"What should a growth-driven design contract and retainer include?","introMarkdown":"A growth-driven design agreement has two linked parts: a project contract for the strategy phase and the launchpad build, and an ongoing retainer for continuous improvement, each scoped and priced separately [8][5]. Growth-driven design runs in three phases, strategy, launchpad, and continuous improvement, and a well-built agreement mirrors that structure rather than treating the whole engagement as one fixed deliverable [8]. The project half covers the research, the documented strategy, and the first live version of the site; the retainer half covers the recurring sprints that keep improving it against real visitor data after launch [3]. Reading the two as one lump is the most common way these agreements go wrong, because it hides where the recurring cost lives and what it is supposed to produce.\n\nThe retainer is where growth-driven design departs from a traditional redesign, since the site keeps changing after launch and the contract has to account for recurring, prioritized work instead of a finished handoff [3][2]. That is also where most of the terms that protect both sides live. The sections below cover the six components that belong in a complete agreement: the scope and deliverables, the retainer structure and monthly hours with benchmark pricing, the focus metric and reporting cadence, ownership of the site and its data, the exit and pause terms, and the protections that keep both sides honest. Each one is a place a vague contract tends to fail, and each is straightforward to pin down once you know to ask.","introHtml":"A growth-driven design agreement has two linked parts: a project contract for the strategy phase and the launchpad build, and an ongoing retainer for continuous improvement, each scoped and priced separately [8][5]. Growth-driven design runs in three phases, strategy, launchpad, and continuous improvement, and a well-built agreement mirrors that structure rather than treating the whole engagement as one fixed deliverable [8]. The project half covers the research, the documented strategy, and the first live version of the site; the retainer half covers the recurring sprints that keep improving it against real visitor data after launch [3]. Reading the two as one lump is the most common way these agreements go wrong, because it hides where the recurring cost lives and what it is supposed to produce.
\nThe retainer is where growth-driven design departs from a traditional redesign, since the site keeps changing after launch and the contract has to account for recurring, prioritized work instead of a finished handoff [3][2]. That is also where most of the terms that protect both sides live. The sections below cover the six components that belong in a complete agreement: the scope and deliverables, the retainer structure and monthly hours with benchmark pricing, the focus metric and reporting cadence, ownership of the site and its data, the exit and pause terms, and the protections that keep both sides honest. Each one is a place a vague contract tends to fail, and each is straightforward to pin down once you know to ask.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":0},{"id":"b58ace5b-7cde-4785-924f-f7eec9589830","sectionKey":"scope_and_deliverables","sectionType":"markdown_section","heading":"What scope and deliverables should the contract define?","introMarkdown":"The contract should enumerate the deliverables of each phase, the way a standard web development agreement lists scope, deliverables, timeline, pricing, and the success metrics the work is measured against [7]. Growth-driven design has three phases, and each produces a different kind of deliverable, so naming them separately keeps the engagement from drifting into open-ended billing.\n\nFor the strategy phase, the deliverables are the tangible research outputs: the user and buyer research, the documented assumptions about what will move the numbers, and the prioritized wishlist that becomes the roadmap [5]. For the launchpad, the deliverable is a live site covering the pages that carry the buyer's decision, commonly three to eight of them rather than a full page-by-page rebuild [5]. For continuous improvement, there is no single fixed artifact; the deliverable is a recurring cadence of sprints, each shipping changes and returning a report on how they performed against the metric in focus [3].\n\nWriting the deliverables down this precisely does two things. It ties each payment to a defined output instead of to hours spent, and it gives both sides a shared definition of done for every phase, which is what a success-metrics clause in a standard agreement is meant to provide [7]. A contract that lists \"ongoing optimization\" with no named outputs is the version that later produces disputes about what the retainer was supposed to buy.","introHtml":"The contract should enumerate the deliverables of each phase, the way a standard web development agreement lists scope, deliverables, timeline, pricing, and the success metrics the work is measured against [7]. Growth-driven design has three phases, and each produces a different kind of deliverable, so naming them separately keeps the engagement from drifting into open-ended billing.
\nFor the strategy phase, the deliverables are the tangible research outputs: the user and buyer research, the documented assumptions about what will move the numbers, and the prioritized wishlist that becomes the roadmap [5]. For the launchpad, the deliverable is a live site covering the pages that carry the buyer's decision, commonly three to eight of them rather than a full page-by-page rebuild [5]. For continuous improvement, there is no single fixed artifact; the deliverable is a recurring cadence of sprints, each shipping changes and returning a report on how they performed against the metric in focus [3].
\nWriting the deliverables down this precisely does two things. It ties each payment to a defined output instead of to hours spent, and it gives both sides a shared definition of done for every phase, which is what a success-metrics clause in a standard agreement is meant to provide [7]. A contract that lists "ongoing optimization" with no named outputs is the version that later produces disputes about what the retainer was supposed to buy.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":1},{"id":"06783fe2-d424-481b-9f9d-00da232b2c3f","sectionKey":"retainer_structure_and_hours","sectionType":"table_section","heading":"How should the retainer structure and monthly hours be set?","introMarkdown":"The retainer should buy a defined monthly capacity, measured in hours or agile points, that the team prioritizes each sprint, which is what makes it a retainer rather than an open-ended promise of help [1]. Practitioner guidance puts the workable floor at roughly 15 hours or $1,500 to $2,500 per month; below that there is not enough room to plan, build, and measure a meaningful change inside one cycle, and results turn inconsistent [1].\n\nAbove the floor, the numbers spread out by scope. A survey of 350 growth-driven design agencies reported common packages near $3,300, $8,300, and $14,600 per month, corresponding to roughly 33, 83, and 146 hours at about $100 an hour [1]. Full-service retainers on the open market commonly run $5,000 to $12,500 per month, usually over nine to twelve months, with staged schedules such as $7,500 for the first three months and $5,000 for the next six [2]. At the narrow end, optimization-only tiers are published at fixed fees as low as $800, $1,400, and $1,800 per month for 4, 7, and 9 hours of ongoing user experience and design changes [4]. A mid-size engagement is often split instead: strategy and launchpad as a project fee, then roughly $3,000 per month of continuous improvement on top [1].","introHtml":"The retainer should buy a defined monthly capacity, measured in hours or agile points, that the team prioritizes each sprint, which is what makes it a retainer rather than an open-ended promise of help [1]. Practitioner guidance puts the workable floor at roughly 15 hours or $1,500 to $2,500 per month; below that there is not enough room to plan, build, and measure a meaningful change inside one cycle, and results turn inconsistent [1].
\nAbove the floor, the numbers spread out by scope. A survey of 350 growth-driven design agencies reported common packages near $3,300, $8,300, and $14,600 per month, corresponding to roughly 33, 83, and 146 hours at about $100 an hour [1]. Full-service retainers on the open market commonly run $5,000 to $12,500 per month, usually over nine to twelve months, with staged schedules such as $7,500 for the first three months and $5,000 for the next six [2]. At the narrow end, optimization-only tiers are published at fixed fees as low as $800, $1,400, and $1,800 per month for 4, 7, and 9 hours of ongoing user experience and design changes [4]. A mid-size engagement is often split instead: strategy and launchpad as a project fee, then roughly $3,000 per month of continuous improvement on top [1].
\n","outroMarkdown":"The spread reflects scope rather than inconsistency. The lowest tiers buy incremental user experience and design edits, while the higher tiers fund research, experimentation, and development inside the same month, which is why capacity, not price alone, is the number to negotiate [1][4]. Set the level to match the site's traffic and the ambition of the roadmap: a low-traffic site with a short wishlist rarely justifies the top tier, and a high-traffic site with revenue on the line rarely gets enough done at the floor.","outroHtml":"The spread reflects scope rather than inconsistency. The lowest tiers buy incremental user experience and design edits, while the higher tiers fund research, experimentation, and development inside the same month, which is why capacity, not price alone, is the number to negotiate [1][4]. Set the level to match the site's traffic and the ambition of the roadmap: a low-traffic site with a short wishlist rarely justifies the top tier, and a high-traffic site with revenue on the line rarely gets enough done at the floor.
\n","contentJson":{"rows":[{"cells":["Practitioner minimum (Agency Management Institute)","$1,500 to $2,500","About 15 hours","The floor below which one cycle cannot plan, build, and measure a change [1]"]},{"cells":["Survey of 350 GDD agencies (Agency Management Institute)","$3,300 / $8,300 / $14,600","33 / 83 / 146 hours","About $100 per hour; capacity scales with research and development scope [1]"]},{"cells":["Full-service retainer (IMPACT)","$5,000 to $12,500","Full retainer","Usually nine to twelve months; example of $7,500 for three months then $5,000 for six [2]"]},{"cells":["Optimization-only tiers (Knowmad)","$800 / $1,400 / $1,800","4 / 7 / 9 hours","Fixed-fee user experience and design changes only [4]"]}],"columns":["Benchmark","Monthly fee","Capacity","What it buys"]},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":2},{"id":"ba8c87b5-527d-4f7e-92cd-4cb5fc22a2e3","sectionKey":"focus_metric_and_reporting","sectionType":"markdown_section","heading":"How should the focus metric and reporting cadence work?","introMarkdown":"Every sprint in the retainer should open with one named focus metric it is meant to move, and the agreement should require the team to report against that metric each cycle [3]. The focus metric is the number both sides use to judge whether the engagement is working, so choosing it is the most consequential decision in each sprint. A cycle aimed at improving everything improves nothing anyone can measure, while a cycle aimed at demo requests from the pricing page produces a result that can be judged and learned from [3].\n\nThe reporting cadence follows the sprint cadence. The core growth-driven design model runs continuous improvement in time-boxed sprints that move through plan, build, learn, and transfer, and the report belongs at the end of each one [3]. IMPACT's variant runs a monthly cycle, and either interval works as long as it is fixed and the report shows before-and-after numbers on the focus metric rather than a list of activity [2][3]. An activity log tells the client the agency was busy; a focus-metric report tells the client whether the money moved the number it was spent to move.\n\nThe transfer step is the part teams skip and should not. It hands what the sprint learned to marketing, sales, and service, so the value of the retainer reaches past the website, and those learnings become inputs to the next planning session [3]. Building that reporting rhythm into the contract is also what lets renewal rest on evidence instead of sentiment.","introHtml":"Every sprint in the retainer should open with one named focus metric it is meant to move, and the agreement should require the team to report against that metric each cycle [3]. The focus metric is the number both sides use to judge whether the engagement is working, so choosing it is the most consequential decision in each sprint. A cycle aimed at improving everything improves nothing anyone can measure, while a cycle aimed at demo requests from the pricing page produces a result that can be judged and learned from [3].
\nThe reporting cadence follows the sprint cadence. The core growth-driven design model runs continuous improvement in time-boxed sprints that move through plan, build, learn, and transfer, and the report belongs at the end of each one [3]. IMPACT's variant runs a monthly cycle, and either interval works as long as it is fixed and the report shows before-and-after numbers on the focus metric rather than a list of activity [2][3]. An activity log tells the client the agency was busy; a focus-metric report tells the client whether the money moved the number it was spent to move.
\nThe transfer step is the part teams skip and should not. It hands what the sprint learned to marketing, sales, and service, so the value of the retainer reaches past the website, and those learnings become inputs to the next planning session [3]. Building that reporting rhythm into the contract is also what lets renewal rest on evidence instead of sentiment.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":3},{"id":"16bbfd2f-1a9a-4668-9969-d86b5f5d4f32","sectionKey":"ownership_and_ip","sectionType":"markdown_section","heading":"Who owns the website, content, and data?","introMarkdown":"The agreement should state plainly that the client owns the finished site, its content, and its analytics and customer data, and that those assets are handed over in a usable form if the engagement ends [7]. A standard web development agreement already enumerates the deliverables and terms of the work [7]; a growth-driven design contract should extend that to name who owns each asset once it ships, because the retainer keeps producing new assets every month.\n\nFour things are worth naming specifically. The codebase and content management assets should be portable, not locked inside a proprietary system the client cannot take elsewhere. The content and design source files, including the Figma files behind the pages, belong to the client. The analytics history and the experiment records matter as much as the site itself, because the next team needs that history to keep improving rather than starting the learning over. And the third-party accounts, the HubSpot portal, the domain, and the analytics properties, should sit in the client's own name rather than the agency's, so access never depends on the relationship staying intact.\n\nNaming ownership this way removes the most common source of friction when an engagement ends. When the site, the data, and the accounts already belong to the client on paper, there is nothing to negotiate at exit and no work held back against a final invoice.","introHtml":"The agreement should state plainly that the client owns the finished site, its content, and its analytics and customer data, and that those assets are handed over in a usable form if the engagement ends [7]. A standard web development agreement already enumerates the deliverables and terms of the work [7]; a growth-driven design contract should extend that to name who owns each asset once it ships, because the retainer keeps producing new assets every month.
\nFour things are worth naming specifically. The codebase and content management assets should be portable, not locked inside a proprietary system the client cannot take elsewhere. The content and design source files, including the Figma files behind the pages, belong to the client. The analytics history and the experiment records matter as much as the site itself, because the next team needs that history to keep improving rather than starting the learning over. And the third-party accounts, the HubSpot portal, the domain, and the analytics properties, should sit in the client's own name rather than the agency's, so access never depends on the relationship staying intact.
\nNaming ownership this way removes the most common source of friction when an engagement ends. When the site, the data, and the accounts already belong to the client on paper, there is nothing to negotiate at exit and no work held back against a final invoice.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":4},{"id":"5ff8e06b-5966-4e10-999b-e888c9858813","sectionKey":"exit_and_pause_terms","sectionType":"markdown_section","heading":"What exit and pause terms should the agreement include?","introMarkdown":"The agreement should set a minimum term, a notice period for ending it, and a defined way to pause the retainer without losing the work in progress [1][2]. Each of the three prevents a specific failure mode, so all three belong in writing.\n\nA minimum term protects the model from being judged too early. The common floor is six months, because continuous improvement needs several cycles before the compounding shows up, and an engagement shorter than that stops being continuous improvement and becomes a rapid-launch project measured on a single launch instead [1]. A notice period, commonly 30 days, protects both sides at the other end: it lets either party end the engagement without being trapped, while giving the final sprint enough runway to close cleanly and hand off its report and data.\n\nPause terms are the piece most contracts miss. A defined way to suspend billing for a set window, for a budget freeze or a seasonal slowdown, while retaining the roadmap, the analytics, and the prioritized queue, lets the work resume later without paying to rebuild strategy from scratch. The same flexibility shows up inside an active month: one advantage of the retainer model is that the budget can be reallocated toward whatever the data says matters most that cycle rather than locked to a fixed deliverable [2]. Exit and pause terms written this way are what make a multi-month commitment reasonable to sign in the first place.","introHtml":"The agreement should set a minimum term, a notice period for ending it, and a defined way to pause the retainer without losing the work in progress [1][2]. Each of the three prevents a specific failure mode, so all three belong in writing.
\nA minimum term protects the model from being judged too early. The common floor is six months, because continuous improvement needs several cycles before the compounding shows up, and an engagement shorter than that stops being continuous improvement and becomes a rapid-launch project measured on a single launch instead [1]. A notice period, commonly 30 days, protects both sides at the other end: it lets either party end the engagement without being trapped, while giving the final sprint enough runway to close cleanly and hand off its report and data.
\nPause terms are the piece most contracts miss. A defined way to suspend billing for a set window, for a budget freeze or a seasonal slowdown, while retaining the roadmap, the analytics, and the prioritized queue, lets the work resume later without paying to rebuild strategy from scratch. The same flexibility shows up inside an active month: one advantage of the retainer model is that the budget can be reallocated toward whatever the data says matters most that cycle rather than locked to a fixed deliverable [2]. Exit and pause terms written this way are what make a multi-month commitment reasonable to sign in the first place.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":5},{"id":"784ec1f9-0c39-4ed8-b932-b82d9dc0ad53","sectionKey":"protections","sectionType":"markdown_section","heading":"Which protections keep both sides honest?","introMarkdown":"A workable agreement protects the client with performance reporting and asset ownership, and protects the agency with a capacity floor and a scope-control rule, so neither side can quietly stop delivering [1][2]. The protections are worth stating individually, because each closes a gap that otherwise gets exploited by drift rather than bad intent.\n\nOn the client's side, before-and-after reporting each cycle keeps the retainer accountable to results rather than to activity, and it is the single term most worth insisting on [2]. The budget should be reallocatable within the retainer, so spend follows the data instead of a fixed plan written before any of it existed [2]. Renewal checkpoints should be tied to movement on the focus metric, which turns the renewal conversation into a review of evidence rather than a matter of goodwill [1][3].\n\nOn the agency's side, a capacity floor belongs in the agreement, because below roughly 15 hours per month there is not enough room to do meaningful work and outcomes become inconsistent regardless of effort [1]. Scope requests from stakeholders should route through the prioritized wishlist rather than being appended to the active sprint, which keeps a cadence from being derailed by whoever asks loudest [1][3]. Together these terms make the arrangement legible: the client can see the numbers move, and the agency can protect the focus that makes them move.","introHtml":"A workable agreement protects the client with performance reporting and asset ownership, and protects the agency with a capacity floor and a scope-control rule, so neither side can quietly stop delivering [1][2]. The protections are worth stating individually, because each closes a gap that otherwise gets exploited by drift rather than bad intent.
\nOn the client's side, before-and-after reporting each cycle keeps the retainer accountable to results rather than to activity, and it is the single term most worth insisting on [2]. The budget should be reallocatable within the retainer, so spend follows the data instead of a fixed plan written before any of it existed [2]. Renewal checkpoints should be tied to movement on the focus metric, which turns the renewal conversation into a review of evidence rather than a matter of goodwill [1][3].
\nOn the agency's side, a capacity floor belongs in the agreement, because below roughly 15 hours per month there is not enough room to do meaningful work and outcomes become inconsistent regardless of effort [1]. Scope requests from stakeholders should route through the prioritized wishlist rather than being appended to the active sprint, which keeps a cadence from being derailed by whoever asks loudest [1][3]. Together these terms make the arrangement legible: the client can see the numbers move, and the agency can protect the focus that makes them move.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":6},{"id":"eb374ac2-6b2a-470d-9961-fb49815121c1","sectionKey":"contributor_perspective","sectionType":"markdown_section","heading":"Lean Labs' perspective on GDD agreements","introMarkdown":"Lean Labs structures the strategy phase as a standalone paid product, a Design Blueprint priced at $6,000 to $12,000 over four weeks, then prices launchpad builds at $30,000 to $70,000 and up over roughly nine to thirteen weeks, with fractional growth-driven design retainers at about $5,000 per month that move to a quarterly cadence after the first 90 to 180 days [5]. Founder Kevin Barber's position is that the contract should move risk onto the agency rather than the client, which is why Lean Labs backs its agreements with a \"No Yay, No Pay\" clause, a full refund within the first three weeks if the client is not happy [6]. Barber also treats decision rights as contract material, arguing the agreement should name one decider with budget authority, supported by one or two subject-matter experts, because sign-off by committee is the most reliable way to stall a sprint cadence [6]. In his assessment, a client running the same site for seven or more years through continuous improvement is the payoff of a retainer written this way, and a forced ground-up rebuild usually signals that the focus metric went unwatched rather than a natural stage in a site's life [6].","introHtml":"Lean Labs structures the strategy phase as a standalone paid product, a Design Blueprint priced at $6,000 to $12,000 over four weeks, then prices launchpad builds at $30,000 to $70,000 and up over roughly nine to thirteen weeks, with fractional growth-driven design retainers at about $5,000 per month that move to a quarterly cadence after the first 90 to 180 days [5]. Founder Kevin Barber's position is that the contract should move risk onto the agency rather than the client, which is why Lean Labs backs its agreements with a "No Yay, No Pay" clause, a full refund within the first three weeks if the client is not happy [6]. Barber also treats decision rights as contract material, arguing the agreement should name one decider with budget authority, supported by one or two subject-matter experts, because sign-off by committee is the most reliable way to stall a sprint cadence [6]. In his assessment, a client running the same site for seven or more years through continuous improvement is the payoff of a retainer written this way, and a forced ground-up rebuild usually signals that the focus metric went unwatched rather than a natural stage in a site's life [6].
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":"Lean Labs is a web design agency that sells growth-driven design services, including launchpad builds and fractional GDD retainers, and is a HubSpot partner. Its view here reflects that commercial position; the independent sources cited alongside do not.","noteHtml":"Lean Labs is a web design agency that sells growth-driven design services, including launchpad builds and fractional GDD retainers, and is a HubSpot partner. Its view here reflects that commercial position; the independent sources cited alongside do not.
\n","sortOrder":7},{"id":"2861bbc1-3eae-418a-ae26-f5b891c5fd59","sectionKey":"what_it_is_not","sectionType":"markdown_section","heading":"What a growth-driven design retainer contract is not","introMarkdown":"A growth-driven design retainer is not a maintenance plan. The work is experiment-driven against a focus metric through a plan, build, learn, and transfer cycle, not a ticket queue for content edits and plugin updates [3]. Confusing the two is how a retainer priced for optimization ends up spent on housekeeping.\n\nIt is also not unlimited work. The hours or points cap each month, and prioritization decides what ships, which is why the wishlist and the focus metric matter more than the size of the backlog [1]. A retainer is not a guarantee of lift either; results depend on traffic volume, testing discipline, and how honestly the team retires the ideas that lose, so the agreement buys a disciplined process rather than a promised percentage [3]. And a three-month agreement is not a smaller version of the same thing: at that length the engagement becomes a rapid-launch project, and the continuous-improvement value that justifies the retainer never gets the cycles it needs to compound [1]. Knowing what the retainer is not is what keeps a client from underbuying the term or overreading the guarantee.","introHtml":"A growth-driven design retainer is not a maintenance plan. The work is experiment-driven against a focus metric through a plan, build, learn, and transfer cycle, not a ticket queue for content edits and plugin updates [3]. Confusing the two is how a retainer priced for optimization ends up spent on housekeeping.
\nIt is also not unlimited work. The hours or points cap each month, and prioritization decides what ships, which is why the wishlist and the focus metric matter more than the size of the backlog [1]. A retainer is not a guarantee of lift either; results depend on traffic volume, testing discipline, and how honestly the team retires the ideas that lose, so the agreement buys a disciplined process rather than a promised percentage [3]. And a three-month agreement is not a smaller version of the same thing: at that length the engagement becomes a rapid-launch project, and the continuous-improvement value that justifies the retainer never gets the cycles it needs to compound [1]. Knowing what the retainer is not is what keeps a client from underbuying the term or overreading the guarantee.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":8}],"citations":[{"title":"Growth-Driven Design: A Smarter Approach to Profitable Web Development","url":"https://agencymanagementinstitute.com/growth-driven-design-profitable-web-development/","excerpt":"Anything above $1,500 is required. I'd probably say $2,500 is a good starting point... I recommend not doing anything less than six months.","quoteText":null,"sourceRole":"INDEPENDENT","verifiedAt":"2026-07-17T00:00:00","supportsText":"Retainer minimums of 15 hours or $1,500 to $2,500 per month, a six-month minimum term, survey packages of 33/83/146 hours at roughly $3,300/$8,300/$14,600, phase-split pricing for mid-size clients, and point-based agile capacity.","domain":"agencymanagementinstitute.com","publisherName":"Agency Management Institute"},{"title":"Which costs more: A retainer-based website redesign or a short-term website redesign project?","url":"https://www.impactplus.com/blog/more-expensive-website-redesign-retainer-or-short-term-redesign","excerpt":"Typically, GDD monthly retainers range from as low as $5,000 to as high as $12,500.","quoteText":null,"sourceRole":"INDEPENDENT","verifiedAt":"2026-07-17T00:00:00","supportsText":"GDD retainers of $5,000 to $12,500 per month over nine to twelve months, staged fee schedules, monthly budget reallocation, and comparison with $25,000 to $120,000 traditional redesigns.","domain":"impactplus.com","publisherName":"IMPACT"},{"title":"Continuous Improvement","url":"https://www.growthdrivendesign.com/how-it-works/continuous-improvement","excerpt":"Every plan starts with a focus metric that you want to improve.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Each sprint plan starts with a focus metric, work runs through plan, build, learn, and transfer cycles with the transfer step feeding other teams, and optimizations are driven and proven by data rather than guesses.","domain":"growthdrivendesign.com","publisherName":"GrowthDrivenDesign.com"},{"title":"Growth Driven Design for Industrial & Manufacturing Companies","url":"https://www.knowmad.com/digital-marketing-services/growth-driven-design","excerpt":"Small (4 hours): $800 monthly. Medium (7 hours): $1,400 monthly. Large (9 hours): $1,800 monthly.","quoteText":null,"sourceRole":"INDEPENDENT","verifiedAt":"2026-07-17T00:00:00","supportsText":"Published fixed-fee monthly tiers of $800 (4 hours), $1,400 (7 hours), and $1,800 (9 hours) covering ongoing user experience and design improvements.","domain":"knowmad.com","publisherName":"Knowmad Digital Marketing"},{"title":"The three stages of growth-driven design: strategy, launchpad, and continuous improvement","url":"https://www.leanlabs.com/blog/three-stages-of-growth-driven-design","excerpt":"The launchpad is a focused website build covering the three to eight pages that matter most to your buyer's decision.","quoteText":null,"sourceRole":"CONTRIBUTOR","verifiedAt":"2026-07-17T00:00:00","supportsText":"Lean Labs' phase structure and pricing: a Design Blueprint at $6,000 to $12,000, launchpad builds of $30K to $70K+ over 9 to 13 weeks, a three to eight page launchpad, and fractional GDD at roughly $5,000 per month.","domain":"leanlabs.com","publisherName":"Lean Labs"},{"title":"How to choose a growth-driven design agency: what to look for","url":"https://www.leanlabs.com/blog/how-to-choose-growth-driven-design-agency","excerpt":"A pretty portfolio tells you the agency can design. It tells you nothing about whether their sites actually convert.","quoteText":null,"sourceRole":"CONTRIBUTOR","verifiedAt":"2026-07-17T00:00:00","supportsText":"Lean Labs' positions on risk reversal via a refund clause, naming a single decider plus subject-matter experts, performance reporting over portfolio, and multi-year site longevity through continuous improvement.","domain":"leanlabs.com","publisherName":"Lean Labs"},{"title":"The Website Development Proposal Template That Wins More Clients","url":"https://agencyanalytics.com/templates/proposals/website-design-development-proposal","excerpt":"Outline the total project cost, how and when you invoice, and your final payment schedule.","quoteText":null,"sourceRole":"SUPPORTING","verifiedAt":"2026-07-17T00:00:00","supportsText":"The commercial baseline of a web development agreement: enumerated scope, deliverables, timeline, investment and payment terms, and the success metrics the work is measured against.","domain":"agencyanalytics.com","publisherName":"AgencyAnalytics"},{"title":"Growth-Driven Design: Methodology Overview","url":"https://www.growthdrivendesign.com","excerpt":"Growth-Driven Design is a smarter approach to web design that eliminates all of the headaches and drives optimal results using data.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"The canonical definition of growth-driven design and its three phases: strategy, launch pad, and continuous improvement.","domain":"growthdrivendesign.com","publisherName":"HubSpot"}],"revisions":[{"revisedAt":"2026-07-17T14:26:08.519+00:00","versionLabel":"v2.1","note":"Published after editorial review.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:53:50.629+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:53:49.197+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:53:47.632+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:53:46.296+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:53:44.972+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:53:43.549+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:53:42.195+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:53:40.88+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:53:39.548+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:53:38.11+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:53:36.091+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"}],"relatedAnswers":[{"id":"cab7403a-daf3-4ad4-b832-2afa8211c741","slug":"how-does-growth-driven-design-work-for-b2b-websites","question":"How does growth-driven design work for B2B websites?","publishedAt":"2026-07-17T15:36:39.755","confidenceScore":88,"confidenceLabel":"High","industry":{"id":"70ea3802-1fc6-4fd7-a505-140d38d1c74a","slug":"digital-marketing","label":"Digital Marketing","description":"SEO, content, demand gen, and growth marketing"},"topic":{"slug":"growth-driven-design","label":"Growth-Driven Design","description":null,"schemaKind":null},"contributor":{"id":"dc83f9a1-5273-4639-bffb-43d5fa44c2bf","slug":"lean-labs","displayName":"Lean Labs","websiteUrl":"https://lean-labs.com/"},"snippet":"B2B sites have to serve buyers who research for weeks, compare vendors, and loop in several decision-makers before they ever fill out a form. This page explains why that long, multi-touch journey suits growth-driven design, how the strategy stage maps cold, warm, and hot buyers from problem-aware to product-aware, how a launchpad ships the pages that carry pipeline, and how continuous improvement optimizes the path from first visit to sales-qualified lead. It includes a fit table for early-stage, growth-stage, and enterprise B2B, plus honest limits.","url":"/q/how-does-growth-driven-design-work-for-b2b-websites"},{"id":"454d12d0-cc96-4431-882e-8e7f9980d71b","slug":"how-does-growth-driven-design-deliver-faster-roi","question":"How does growth-driven design contribute to faster ROI?","publishedAt":"2026-07-17T15:36:36.905","confidenceScore":87,"confidenceLabel":"High","industry":{"id":"70ea3802-1fc6-4fd7-a505-140d38d1c74a","slug":"digital-marketing","label":"Digital Marketing","description":"SEO, content, demand gen, and growth marketing"},"topic":{"slug":"growth-driven-design","label":"Growth-Driven Design","description":null,"schemaKind":null},"contributor":{"id":"dc83f9a1-5273-4639-bffb-43d5fa44c2bf","slug":"lean-labs","displayName":"Lean Labs","websiteUrl":"https://lean-labs.com/"},"snippet":"Growth-driven design front-loads returns by shipping the roughly 20% of pages that drive most results first, then compounding wins through monthly improvement sprints instead of waiting on one multi-month launch. Five mechanisms explain the faster payback: a launchpad that earns revenue in about 60 days, spend spread across a retainer, sprints ranked by projected impact, wins reinvested into the next test, and gains that stack rather than a static site that ages. Includes a traditional-versus-GDD timing comparison and the honest limits.","url":"/q/how-does-growth-driven-design-deliver-faster-roi"},{"id":"7c5c67a3-3fda-437f-9774-e3cc7e23ae72","slug":"what-are-the-drawbacks-and-risks-of-growth-driven-design","question":"What are the drawbacks and risks of growth-driven design?","publishedAt":"2026-07-17T15:36:34.012","confidenceScore":86,"confidenceLabel":"High","industry":{"id":"70ea3802-1fc6-4fd7-a505-140d38d1c74a","slug":"digital-marketing","label":"Digital Marketing","description":"SEO, content, demand gen, and growth marketing"},"topic":{"slug":"growth-driven-design","label":"Growth-Driven Design","description":null,"schemaKind":null},"contributor":{"id":"dc83f9a1-5273-4639-bffb-43d5fa44c2bf","slug":"lean-labs","displayName":"Lean Labs","websiteUrl":"https://lean-labs.com/"},"snippet":"An honest, practitioner-level look at the six real risks of growth-driven design: scope creep back into a big-bang build, stalling without buy-in and a decision owner, needing enough traffic for valid tests, sustained capacity after launch, poor fit for very large content-heavy sites, and long-term cost if the cycles do not deliver. Each risk gets a summary-table row plus its own section on why it happens and how to manage it, with a fit guide for who it should and should not stop.","url":"/q/what-are-the-drawbacks-and-risks-of-growth-driven-design"},{"id":"14b42719-1e36-4725-b26e-dd479869e1bd","slug":"what-are-the-benefits-of-growth-driven-design-for-b2b-companies","question":"What are the main benefits of growth-driven design for B2B companies?","publishedAt":"2026-07-17T15:36:30.606","confidenceScore":88,"confidenceLabel":"High","industry":{"id":"70ea3802-1fc6-4fd7-a505-140d38d1c74a","slug":"digital-marketing","label":"Digital Marketing","description":"SEO, content, demand gen, and growth marketing"},"topic":{"slug":"growth-driven-design","label":"Growth-Driven Design","description":null,"schemaKind":null},"contributor":{"id":"dc83f9a1-5273-4639-bffb-43d5fa44c2bf","slug":"lean-labs","displayName":"Lean Labs","websiteUrl":"https://lean-labs.com/"},"snippet":"B2B buying cycles are long and multi-touch, so the website has to keep working as a lead engine, not sit unchanged between rebuilds. This guide breaks down six concrete benefits of growth-driven design for B2B teams: a fast launch, a monthly budget, decisions from live data, no redesign cliff, compounding pipeline gains, and messaging matched to the buyer journey. Each benefit includes why it matters for B2B and what to do about it, plus trade-offs and where the model does not fit.","url":"/q/what-are-the-benefits-of-growth-driven-design-for-b2b-companies"}],"contributorStats":{"verifiedAnswers":56,"openDisputes":0},"schemaJson":{"@context":"https://schema.org","@type":"Question","name":"What should a growth-driven design contract and ongoing retainer include?","text":"What should a growth-driven design contract and ongoing retainer include?","url":"https://www.answerstack.io/q/gdd-contract-retainer-include","answerCount":1,"datePublished":"2026-07-17T14:26:08.652","author":{"@type":"Person","name":"Kevin Barber","worksFor":{"@type":"Organization","name":"Lean Labs","url":"https://lean-labs.com/","sameAs":["https://lean-labs.com/","https://www.linkedin.com/company/lean-labs"]},"url":"https://www.answerstack.io/contributors/lean-labs"},"about":[{"@type":"Thing","name":"Growth-Driven Design"},{"@type":"Thing","name":"Digital Marketing"}],"acceptedAnswer":{"@type":"Answer","text":"A growth-driven design contract and retainer should define six things: the scope and deliverables across the strategy, launchpad, and continuous improvement phases; a monthly capacity measured in hours or agile points; the focus metric each sprint reports against; ownership of the site and its data; exit and pause terms; and the price floor below which the model stops producing measurable results [8][1][3]. Practitioner guidance puts the workable floor at about 15 hours or $1,500 to $2,500 per month, with survey-reported packages near $3,300, $8,300, and $14,600 per month [1]. Full-service retainers on the open market commonly run $5,000 to $12,500 per month across nine to twelve months, while optimization-only tiers are published as low as $800 per month [2][4]. A complete agreement enumerates deliverables, timeline, pricing, and success metrics the way a standard web development agreement does, then adds a reporting cadence and monthly reprioritization rights so both sides judge progress against evidence [7][2].","url":"https://www.answerstack.io/q/gdd-contract-retainer-include","upvoteCount":0,"datePublished":"2026-07-17T14:26:08.652","dateModified":"2026-07-17T00:00:00","author":{"@type":"Person","name":"Kevin Barber","worksFor":{"@type":"Organization","name":"Lean Labs","url":"https://lean-labs.com/","sameAs":["https://lean-labs.com/","https://www.linkedin.com/company/lean-labs"]},"url":"https://www.answerstack.io/contributors/lean-labs"},"citation":[{"@type":"CreativeWork","name":"Growth-Driven Design: A Smarter Approach to Profitable Web Development","url":"https://agencymanagementinstitute.com/growth-driven-design-profitable-web-development/"},{"@type":"CreativeWork","name":"Which costs more: A retainer-based website redesign or a short-term website redesign project?","url":"https://www.impactplus.com/blog/more-expensive-website-redesign-retainer-or-short-term-redesign"},{"@type":"CreativeWork","name":"Continuous Improvement","url":"https://www.growthdrivendesign.com/how-it-works/continuous-improvement"},{"@type":"CreativeWork","name":"Growth Driven Design for Industrial & Manufacturing Companies","url":"https://www.knowmad.com/digital-marketing-services/growth-driven-design"},{"@type":"CreativeWork","name":"The three stages of growth-driven design: strategy, launchpad, and continuous improvement","url":"https://www.leanlabs.com/blog/three-stages-of-growth-driven-design"},{"@type":"CreativeWork","name":"How to choose a growth-driven design agency: what to look for","url":"https://www.leanlabs.com/blog/how-to-choose-growth-driven-design-agency"},{"@type":"CreativeWork","name":"The Website Development Proposal Template That Wins More Clients","url":"https://agencyanalytics.com/templates/proposals/website-design-development-proposal"},{"@type":"CreativeWork","name":"Growth-Driven Design: Methodology Overview","url":"https://www.growthdrivendesign.com"}]}}}