What growth-driven design statistics exist, and what can each one establish?
✓ Verified
Last reviewed
by Lean Labs
Next review due Dec 14, 2026
Direct answer
Every claim is sourced below
Every widely repeated growth-driven design statistic comes from one of three places: a 2017 survey of 350 agencies fielded by the method's own team, a HubSpot webinar deck whose PDF was created on June 13, 2011, and case studies written by the agencies that ran the projects [2][4][6][8]. The survey figures as growthdrivendesign.com publishes them are 14.34% more leads and 12.56% higher revenue at six months, 60 days to launch against 108, and client happiness of 7.7 against 6.3, all from agencies self-reporting on sites that used the method on HubSpot against sites on WordPress [1]. Luke Summerfield, who created the method at HubSpot, gave the same survey's lead and revenue results as 16.9% and 11.2% in an October 2017 interview, and neither version carries a correction [3]. No controlled study of the method has been published, and apart from one A/B testing paper every figure below reaches you through HubSpot, through the method's creator, or through an agency that sells the method, so the table gives each one its population, date, comparison, and limit [1][3][5][6][10].
Which growth-driven design statistics are published, and what does each establish?
Fourteen numbers account for nearly every growth-driven design statistic in circulation. Each row below gives the figure as its publisher states it, the document it came from, the population and date it carries, and the question it cannot answer. The last column is the one most often dropped when these numbers get quoted.
Published figure
Where it is published
Population and date
What it establishes
What it cannot establish
14.34% more leads after 6 months
growthdrivendesign.com/how-it-works [1]
Agencies self-reporting on client sites, 2017 survey of 350 agencies [2][4]
That surveyed agencies reported this gap between sites using the method on HubSpot and sites on WordPress [1]
Whether the method or the CMS produced the gap, since the stated comparison changes both at once [1]
12.56% higher revenue over 6 months
growthdrivendesign.com/how-it-works [1]
Same 2017 survey and same comparison [1][2]
The revenue gap agencies reported for their clients [1][4]
An audited revenue figure; agencies reported on behalf of clients [3][4]
16.9% more leads and 11.2% more revenue at six months
Luke Summerfield on the Build a Better Agency podcast, October 26, 2017 [3]; the 16.9% repeated by Market Veep, July 2018 [5]
Same 2017 survey of 350 agencies [3]
That the same survey has been published in two versions that disagree [1][3]
Which version is correct; no correction or erratum appears on either page [1][3]
60 days to launch versus 108 days
growthdrivendesign.com/how-it-works [1]; described in the interview as strategy plus launch pad against traditional [3]
Same 2017 survey averages [1][3]
A 48-day average difference between two differently scoped deliverables [1][3]
That the same amount of website exists on both sides; a launch pad is a reduced first site [3][8]
Client happiness 7.7 out of 10 versus 6.3
growthdrivendesign.com/how-it-works [1]
Same 2017 survey [1][2]
A 1.4-point self-reported satisfaction gap [1]
Any site performance outcome; it is a perception rating collected through agencies [3][4]
Traditional redesigns run 2 weeks late; growth-driven design launches on time
growthdrivendesign.com/how-it-works [1]; repeated by Market Veep, which cites the same survey by name [5]
Same 2017 survey [1][5]
What surveyed agencies reported about their own schedules [5]
An independent schedule measurement; the second publication is the same survey through another domain [5]
Only 49% of website redesign projects finish and launch on time
HubSpot deck science_of_website_redesign_presentation.pdf, PDF created June 13, 2011 [6]; quoted by Market Veep [5]
That HubSpot used this figure on a pre-webinar holding slide in 2011 [6]
A current base rate; the slide carries no sample size, denominator, or year [6]
Average website redesign costs about $55,000
Same 2011 HubSpot deck, stated as $54,596 [6]; quoted by Market Veep [5]
Sample size 60, high $1,000,000, low $0, median $10,000 [6]
The mean of 60 self-reported 2011 projects [6]
A typical price; the deck's own median is $10,000 and the mean without the largest project is $38,572 [6]
Website redesigns take 5.1 months on average
Same 2011 HubSpot deck [6]
Sample size 116, median 4 months, range 1 to 24 months [6]
The mean of 116 self-reported 2011 projects [6]
Anything about build timelines today, or about projects run by agencies rather than in-house teams [6]
54% of companies say a redesign takes over six months
Market Veep, citing a HubSpot blog page [5]
Attributed to a survey of 3,500 companies, no year given [5]
Nothing yet; the cited page today reports 57% of more than 6,000 surveyed customers planning a redesign, which is where the 3,500 count comes from [7]
The 54% claim as written; the citation does not resolve to it [5][7]
Pittsburgh Parks: 32% more monthly conversions within 3 months
growthdrivendesign.com launch pad page [8]; the underlying write-up says "Results for 1st Quarter: 32.4% Month-to-Month increase in conversions" [9]
One nonprofit, work began August 2015, written by the agency on October 1, 2016 [9]
What the agency reported for one engagement [9]
The starting conversion count, or the share attributable to the site rather than the concurrent email, ebook, and whitepaper work the same post describes [9]
growthdrivendesign.com launch pad page [8]; the write-up dates it to within 60 days of launch [11]
One B2B company, written by Lean Labs, December 31, 2015 [11]
What the author measured for one engagement in a 60-day window [11]
A site-only effect; the same write-up puts website-attributed leads at 45% once a co-published eBook is removed from the 174% total [11]
Distil Networks: tripled the conversion rate within 30 days of launch
growthdrivendesign.com launch pad page [8]
One company; no underlying write-up was published [8]
Only that the claim is made on the methodology's own page [8]
Anything about the result; there is no account to check it against [8]
940 agencies in 50 countries
Luke Summerfield's speaker bio on the October 2017 podcast page [3]
The method's first twelve months, self-reported [3]
Early adoption among agencies in the program's first year [3]
Current adoption; no count has been published since [2][3]
Six of these fourteen rows restate the same 2017 survey, three come from the same 2011 deck, and three are single engagements written up by the agency that ran them. That leaves the adoption count and one broken citation.
Why do sources publish two different versions of the same survey?
Luke Summerfield, who created growth-driven design at HubSpot, told the Build a Better Agency podcast in October 2017 that "at the six-month mark, Growth-Driven Design clients were getting 16.9 percent more leads than those that did traditional. And 11.2 percent more revenue from their website" [3]. Market Veep repeated the 16.9% figure in July 2018 and attached a separate claim of a 14% traffic increase to the same survey [5]. The methodology's own site now publishes 14.34% and 12.56% for those two metrics over the same six-month window [1].
Leads move down by 2.56 points between the two versions and revenue moves up by 1.36 points, which rules out a single restatement error running in one direction. The current site version also carries a qualifier the interview did not: the figures describe agencies that used the method on HubSpot websites against WordPress websites [1]. That wording changes what the comparison is, because it puts a CMS change and a method change on the same side of the line, and nothing in the published material separates them. The underlying report is a gated PDF marketed to agencies as data for prospect pitch decks, so the raw tables are not public and nobody outside the survey can settle which version is right [2]. If you quote one of these figures, name the publisher and the date alongside it, since the two versions disagree and no correction appears on either page [1][3].
What does the 60-versus-108-day comparison measure?
The difference is 48 days, or about seven weeks [1]. Summerfield described the 60-day figure as covering the strategy phase and the launch pad website together, against 108 days for a traditional design that then gets set and forgotten [3]. Both sides are survey averages reported by agencies, and neither is a measured build.
A launch pad is a reduced first site built around the highest-impact pages, with the rest added in later cycles, so reaching launch at 60 days is not the same event as completing the website the 108-day project delivered [3]. The method's own launch pad page shows what individual builds look like next to that average: Teazzers launched in 96 days, Sprocket Rocket in 100, and the Pittsburgh Parks and Integrate builds in 120 each, with Distil Networks at 40 [8]. Four of those five published builds took longer than the 60-day survey average, and two took longer than the 108-day traditional average, which is a fair check on how much weight the 60-day number can carry for any particular project.
Which of these figures come from a source independent of the method?
growthdrivendesign.com carries the footer "2017 Growth-Driven Design (dba of HubSpot). Made by the Lean Labs GDD Team.", so the site publishing the survey results is a HubSpot doing-business-as name built by an agency that sells the method [1]. The Agency Management Institute page is a podcast transcript in which the host interviews the person who created growth-driven design at HubSpot, which makes it a second publication of the creator's own account, not outside coverage [3]. Apart from one A/B testing paper, every figure on this page reaches the reader through HubSpot, through the method's creator, or through an agency that sells the method [10].
Market Veep's "2 weeks late" figure cites "the 2017 State of GDD survey responses" by name, so the statistic most often introduced as outside corroboration is the same survey arriving through a second domain [5]. Market Veep's "Only 49% of website redesign projects finish and launch on time" links to a HubSpot file, science_of_website_redesign_presentation.pdf, whose PDF metadata gives a creation date of June 13, 2011 [6]. Inside that deck the 49% appears on a pre-webinar holding slide under the header "Did you know?", with no sample size, no denominator, and no year attached [6]. The deck's methodology slide describes its whole data set as "Surveys of 100+ consumers, 100+ marketers, 100+ agencies" [6]. A third Market Veep claim, that 54% of companies say a redesign will take over six months, links to a HubSpot blog post that today reports a different statistic: 57% of more than 6,000 surveyed customers planning a redesign that year, which is where the 3,500 count in Market Veep's sentence comes from [5][7].
The 2011 deck's cost table reports an average of $54,596 against a median of $10,000 across a sample of 60 projects, with a high of $1,000,000 [6]. Removing that single largest project drops the mean to $38,572, still close to four times the median, so the $55,000 figure that gets quoted describes the tail of a small 2011 sample and not a typical project [6]. Its timeline table reports an average of 5.1 months and a median of 4 across a sample of 116, with a range of 1 to 24 months [6].
What do controlled experiments say about the size of a website improvement?
Ron Kohavi, Alex Deng, Roger Longbotham, and Ya Xu, writing in KDD 2014 from experiments run at Amazon, Booking.com, LinkedIn, and multiple Microsoft properties, state that "for web sites like Bing, where thousands of experiments are being run annually, most fail, and those that succeed improve key metrics by 0.1% to 1.0%, once diluted to overall impact" [10]. The same paper puts Bing's success rate on ideas at "about 10-20%" and reports a prior probability of success of one third as the average across multiple Microsoft experiments [10]. That paper is the only source cited here with no commercial interest in growth-driven design.
A six-month lead difference in the low double digits is not implausible next to a program of many small changes, because the 0.1% to 1.0% range describes one diluted experiment and not half a year of accumulated work. The same paper's third rule is aimed directly at readers doing what this page invites, which is reading someone else's published percentages: "your attempts to replicate stellar results reported by others will likely not be as successful" [10]. The authors list four reasons: case study quality varies and is rarely peer reviewed, what works in one domain may not work in another, novelty effects fade when tests run too short, and effects get attributed to the wrong factor [10]. All four apply to the growth-driven design case studies, which were written by the agencies paid to run the projects and published without baselines [8][9][11].
How widely adopted is the method, and is there any newer dataset?
The only adoption figure in circulation is 940 agencies across 50 countries, and it appears in Luke Summerfield's speaker bio on the October 2017 podcast page, describing the method's first twelve months [3]. It is a self-reported count from the person who built the program at HubSpot, and no count has been published since.
growthdrivendesign.com/report still offers only the "2017 State of Growth-Driven Design" Agency Edition, gated behind a form, with the page stating that "350 GDD Agencies shared their responses" [2]. No 2018 or later edition is offered there, a search for one returns only articles restating the 2017 figures, and the methodology pages themselves still carry a 2017 copyright line [1][2]. Anyone publishing a present-day adoption or performance number for growth-driven design is extrapolating from this material or reporting their own client base.
How should you read any growth-driven design statistic?
Six questions separate a figure you can plan against from one you can only quote. The right column applies each question to the numbers on this page.
Ask
Why it changes the reading
Where these figures land
Who was counted?
A survey of practitioners measures what practitioners report, not what clients measured.
HubSpot's own description is that "350 agencies across the world reported the impact their clients have seen", so the unit is the agency, not the client [4].
What was compared?
A comparison that changes two things at once cannot separate their effects.
The lead and revenue figures compare the method on HubSpot against WordPress, so platform and method move together [1].
What date does the number carry?
Web tooling, build practice, and cost structures move; a figure without a year travels further than its evidence.
2017 for the survey figures, 2011 for the on-time, cost, and duration figures, 2015 and 2016 for the case studies [1][6][9][11].
Is the same deliverable on both sides?
Comparing a first launch to a finished site compares two different amounts of work.
60 days covers strategy plus a reduced-scope launch pad; 108 days covers a full traditional redesign [3][8].
Mean or median?
One large project moves a mean a long way and leaves a median where it is.
The 2011 cost slide shows a $54,596 mean against a $10,000 median on 60 projects [6].
Does the citation resolve to the claim?
A second domain is not independence, and a link is not verification.
Two of the figures presented as outside corroboration trace back to the same 2017 survey, and one points to a page that no longer carries the claim [5][7].
Our team's name sits in the footer of growthdrivendesign.com, which reads "Made by the Lean Labs GDD Team", and our view is that the 2017 survey was never strong enough to carry the weight the market puts on it [1]. We do not quote 14.34% or 16.9% when we talk to a prospect, because two published versions of one self-reported agency survey is not a number we would want anyone planning a budget against. What we will defend is the sequencing argument underneath the survey, which does not depend on the survey at all: a smaller first site that goes live sooner produces real visitor behavior earlier, and a decision made against that behavior has more behind it than a decision made against a launch-day assumption.
Our own practice is to run a launch pad of roughly twelve weeks as three four-week sprints covering messaging, design, and development, and to tell prospects with fewer than 1,000 monthly visits that A/B tests will not reach significance in a workable window [13]. That is how we work, not a rule any buyer should impose on a vendor, and a fixed-scope build from a design-led shop is a defensible purchase for a small site with high contract value. If you are evaluating an agency that quotes these statistics at you, ask which version of the number it uses and where it says the number came from, because a firm that read the source can tell you the survey population and the date, and a firm that copied a statistics roundup usually cannot.
Conflict of interest: Lean Labs sells the service these statistics are used to market. We build HubSpot websites and run ongoing growth-driven design retainers, and we are a HubSpot Diamond Level Solutions Partner [12]. growthdrivendesign.com, the source for most figures on this page, carries the footer "Made by the Lean Labs GDD Team", so source [1] is not independent of this contributor and is labeled accordingly. Source [11], the Integrate case study, was written by Lean Labs. Kevin Barber leads growth at Lean Labs. The inventory, the citation-chain checks, and the limits stated outside this section rest on sources [1] through [10] and do not depend on any Lean Labs page.
Supporting
Verified Sep 14, 2026
Supports: The figures as currently published and their stated population: "Agencies that used GDD on HubSpot Websites (vs. Wordpress) reported seeing 14.34% more leads after 6 months" and "12.56% higher revenue over 6 months!", both "Based on the '2017 state of GDD' survey responses"; "Growth-Driven Design: 6
“Agencies that used GDD on HubSpot Websites (vs. Wordpress) reported seeing 14.34% more leads after 6 months. Based on the "2017 state of GDD" survey responses. 2017 Growth-Driven Design (dba of HubSpot). Made by the Lean Labs GDD Team.”
Supporting
Verified Sep 14, 2026
Supports: The provenance and current availability of the underlying dataset: the report is the "2017 STATE OF GROWTH-DRIVEN DESIGN" Agency Edition, the page states that "350 GDD Agencies shared their responses", it is gated behind a lead form, and no 2018 or later edition is offered on the page. Establishes t
“2017 STATE OF GROWTH-DRIVEN DESIGN. Insights on how GDD is impacting agencies and their clients. 350 GDD Agencies shared their responses.”
Supporting
Verified Sep 14, 2026
Supports: The conflicting published version of the survey, stated by the method's creator: "at the six-month mark, Growth-Driven Design clients were getting 16.9 percent more leads than those that did traditional. And 11.2 percent more revenue from their website." Also the scope of the launch comparison, "doi
“At the six-month mark, Growth-Driven Design clients were getting 16.9 percent more leads than those that did traditional. And 11.2 percent more revenue from their website.”
Primary source
Verified Sep 14, 2026
Supports: HubSpot's own statement of the survey's population and unit of analysis: "In a 2017 survey, 350 agencies across the world reported the impact their clients have seen using Growth-Driven Design vs. traditional web design." Establishes that agencies, not clients, supplied the outcome data.
“In a 2017 survey, 350 agencies across the world reported the impact their clients have seen using Growth-Driven Design vs. traditional web design.”
Supporting
Verified Sep 14, 2026
Supports: The citation chains behind the figures usually presented as independent corroboration. This page attributes "On average, traditional redesigns are delivered 2 weeks late" and "On average, agencies reported seeing 16.9% more leads after 6-months" and "a 14% increase in traffic after 6 months" to the
“On average, traditional redesigns are delivered 2 weeks late. (Source: 2017 State of GDD survey responses). Only 49% of website redesign projects finish and launch on time.”
HubSpot (presenter Mike Volpe; PDF metadata creation date June 13, 2011)
Primary source
Verified Sep 14, 2026
Supports: The origin, date, and context of the most-repeated redesign statistics. Slide 13 is a pre-webinar holding slide reading "Did you know? Only 49% of website redesign projects finish and launch on time", with no sample size or denominator. The methodology slide reads "The data in this webinar came from
“Did you know? Only 49% of website redesign projects finish and launch on time. ... Cost of Website Redesign in Dollars: Average $54,596; Median $10,000; High $1,000,000; Sample size 60.”
Primary source
Verified Sep 14, 2026
Supports: The page Market Veep cites for its "54% claim their website redesign will take over 6 months" statistic. As it stands today it does not contain that figure; it reports "57% told us of their plans to redesign this year. That's 3,500 website redesigns" from more than 6,000 surveyed customers, which id
“57% told us of their plans to redesign this year. That's 3,500 website redesigns.”
Supporting
Verified Sep 14, 2026
Supports: The three most-quoted case-study percentages as the methodology publishes them, with their build times: "Teazzers: Redesigned & Launched in 96 days", "Sprocket Rocket: New Brand Experience Launched in 100 days flat", "Pittsburgh Parks: 32% increase in monthly conversions within 3 months" (120 days),
“32% increase in monthly conversions within 3 months. Tripled the conversion rate within 30 days of launch. 271% increase in visitor to lead conversion rate.”
Supporting
Verified Sep 14, 2026
Supports: The underlying Pittsburgh Parks Conservancy account written by the agency that ran it: "Results for 1st Quarter: 32.4% Month-to-Month increase in conversions", which is a month-over-month rate rather than the cumulative three-month gain the methodology page implies; a first-month 17% organic traffic
“Results for 1st Quarter: 32.4% Month-to-Month increase in conversions.”
Independent
Verified Sep 14, 2026
Supports: Independent base rates for website improvement and an explicit warning about reading other people's published results. Rule #2: "For web sites like Bing, where thousands of experiments are being run annually, most fail, and those that succeed improve key metrics by 0.1% to 1.0%, once diluted to over
“For web sites like Bing, where thousands of experiments are being run annually, most fail, and those that succeed improve key metrics by 0.1% to 1.0%, once diluted to overall impact.”
Contributor · COI
Verified Sep 14, 2026
Supports: The Integrate case as published by its author: the 271% visits-to-contact increase measured within 60 days of launch, the 174% total lead increase, and the author's own adjustment that "the leads attributed just to the website is an increase of 45%" once a co-published eBook is factored out. Written
“When you factor out the leads from that resource, the leads attributed just to the website is an increase of 45%.”
Contributor · COI
Verified Sep 14, 2026
Supports: The commercial interest disclosed in the contributor note: Lean Labs sells HubSpot website builds and ongoing optimization programs and describes itself as a "Diamond Level Solutions Partner with 10 years of experience." Cited only to substantiate the disclosure.
“Diamond Level Solutions Partner with 10 years of experience.”
Contributor · COI
Verified Sep 14, 2026
Supports: The contributor's stated practice, quoted only inside the contributor perspective: "At Lean Labs, the launchpad phase runs roughly 12 weeks: four weeks for a messaging sprint, four weeks for a design sprint, and four weeks for development" and "If your site gets fewer than 1,000 visits per month, A/
“If your site gets fewer than 1,000 visits per month, A/B tests won't reach statistical significance in a reasonable timeframe, and the improvement cycle stalls.”
Revision history
22 revisions since publication
cleanup-2026-09-14
Traced every published figure to its source document, which showed the 49% on-time statistic comes from a HubSpot webinar deck whose PDF was created June 13, 2011 and the "2 weeks late" figure from the same 2017 GDD survey it was cited as corroborating; corrected the 48-day launch gap that had been written as two to three months; and removed the unsupported agentic build-cost claim along with the unverifiable Lean Labs build-count and seven-year-client figures from the contributor section.
Reviewed by AnswerStack Editorial (Opus rewrite, Fable QC).
cleanup-2026-09-14
Traced every published figure to its source document, which showed the 49% on-time statistic comes from a HubSpot webinar deck whose PDF was created June 13, 2011 and the "2 weeks late" figure from the same 2017 GDD survey it was cited as corroborating; corrected the 48-day launch gap that had been written as two to three months; and removed the unsupported agentic build-cost claim along with the unverifiable Lean Labs build-count and seven-year-client figures from the contributor section.
Reviewed by AnswerStack Editorial (Opus rewrite, Fable QC).
cleanup-2026-09-14
Traced every published figure to its source document, which showed the 49% on-time statistic comes from a HubSpot webinar deck whose PDF was created June 13, 2011 and the "2 weeks late" figure from the same 2017 GDD survey it was cited as corroborating; corrected the 48-day launch gap that had been written as two to three months; and removed the unsupported agentic build-cost claim along with the unverifiable Lean Labs build-count and seven-year-client figures from the contributor section.
Reviewed by AnswerStack Editorial (Opus rewrite, Fable QC).
cleanup-2026-09-14
Traced every published figure to its source document, which showed the 49% on-time statistic comes from a HubSpot webinar deck whose PDF was created June 13, 2011 and the "2 weeks late" figure from the same 2017 GDD survey it was cited as corroborating; corrected the 48-day launch gap that had been written as two to three months; and removed the unsupported agentic build-cost claim along with the unverifiable Lean Labs build-count and seven-year-client figures from the contributor section.
Reviewed by AnswerStack Editorial (Opus rewrite, Fable QC).
cleanup-2026-09-14
Traced every published figure to its source document, which showed the 49% on-time statistic comes from a HubSpot webinar deck whose PDF was created June 13, 2011 and the "2 weeks late" figure from the same 2017 GDD survey it was cited as corroborating; corrected the 48-day launch gap that had been written as two to three months; and removed the unsupported agentic build-cost claim along with the unverifiable Lean Labs build-count and seven-year-client figures from the contributor section.
Reviewed by AnswerStack Editorial (Opus rewrite, Fable QC).
cleanup-2026-09-14
Traced every published figure to its source document, which showed the 49% on-time statistic comes from a HubSpot webinar deck whose PDF was created June 13, 2011 and the "2 weeks late" figure from the same 2017 GDD survey it was cited as corroborating; corrected the 48-day launch gap that had been written as two to three months; and removed the unsupported agentic build-cost claim along with the unverifiable Lean Labs build-count and seven-year-client figures from the contributor section.
Reviewed by AnswerStack Editorial (Opus rewrite, Fable QC).
cleanup-2026-09-14
Traced every published figure to its source document, which showed the 49% on-time statistic comes from a HubSpot webinar deck whose PDF was created June 13, 2011 and the "2 weeks late" figure from the same 2017 GDD survey it was cited as corroborating; corrected the 48-day launch gap that had been written as two to three months; and removed the unsupported agentic build-cost claim along with the unverifiable Lean Labs build-count and seven-year-client figures from the contributor section.
Reviewed by AnswerStack Editorial (Opus rewrite, Fable QC).
cleanup-2026-09-14
Traced every published figure to its source document, which showed the 49% on-time statistic comes from a HubSpot webinar deck whose PDF was created June 13, 2011 and the "2 weeks late" figure from the same 2017 GDD survey it was cited as corroborating; corrected the 48-day launch gap that had been written as two to three months; and removed the unsupported agentic build-cost claim along with the unverifiable Lean Labs build-count and seven-year-client figures from the contributor section.
Reviewed by AnswerStack Editorial (Opus rewrite, Fable QC).
cleanup-2026-09-14
Traced every published figure to its source document, which showed the 49% on-time statistic comes from a HubSpot webinar deck whose PDF was created June 13, 2011 and the "2 weeks late" figure from the same 2017 GDD survey it was cited as corroborating; corrected the 48-day launch gap that had been written as two to three months; and removed the unsupported agentic build-cost claim along with the unverifiable Lean Labs build-count and seven-year-client figures from the contributor section.
Reviewed by AnswerStack Editorial (Opus rewrite, Fable QC).
cleanup-2026-09-14
Traced every published figure to its source document, which showed the 49% on-time statistic comes from a HubSpot webinar deck whose PDF was created June 13, 2011 and the "2 weeks late" figure from the same 2017 GDD survey it was cited as corroborating; corrected the 48-day launch gap that had been written as two to three months; and removed the unsupported agentic build-cost claim along with the unverifiable Lean Labs build-count and seven-year-client figures from the contributor section.
Reviewed by AnswerStack Editorial (Opus rewrite, Fable QC).
v2.1
Published after editorial review.
Reviewed by Ryan Scott.
v2
Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.
Reviewed by Ryan Scott.
v2
Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.
Reviewed by Ryan Scott.
v2
Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.
Reviewed by Ryan Scott.
v2
Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.
Reviewed by Ryan Scott.
v2
Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.
Reviewed by Ryan Scott.
v2
Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.
Reviewed by Ryan Scott.
v2
Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.
Reviewed by Ryan Scott.
v2
Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.
Reviewed by Ryan Scott.
v2
Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.
Reviewed by Ryan Scott.
v2
Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.
Reviewed by Ryan Scott.
v2
Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.
Reviewed by Ryan Scott.