A data flywheel is a product that improves as it is used, which brings more use. It only turns when the usage is captured, fed back into the product, and the company has the right to use it.
A short explainer video, under a minute. The two assistants and the loop diagram are an illustration.
At a glance
What a Data Flywheel Is
The video draws the loop. Better answers bring more users.
The Three Conditions
It only turns under three conditions. The usage is captured.
Why It Matters
The video turns this into one question: does our product get better each time it is used?
Two recent reports show where the learning signal comes from. In one, Ai2 says it started from real queries submitted through its ScholarQA system, filtered them to a pool of 90K research-focused queries, and, after quality filtering, had 47K usable examples for supervised fine-tuning.
In another, ServiceNow AI says its AutoSynthData pipeline turns a model’s failures into new training tasks. Both reports verified none of it independently.
The Business Engineer Lens
Where this idea sits in the Business Engineer library:
The Business Engineer framework maps where each part of the AI stack sits and who holds the leverage. These pills are short lessons from the same library.
Data Flywheel builds on Consent. The flywheel turns only if the company has the right to use the usage data; consent asks whether people knew what they agreed to.
Data Flywheel builds on Data Quality. The flywheel feeds user corrections back into the product, and the data-quality lesson says a model copies what it is shown.
Data Flywheel contrasts with Agent Memory. Agent memory keeps notes on one customer for the next chat; a flywheel feeds everyone’s corrections back to improve the product.
Gennaro Cuofano is a CRO and tech executive who has worked in AI since late 2015, starting with bringing NLP, natural-language generation, voice and chatbot products to the marketing industry. His background is in law and finance: he holds a Master's degree in Law and an International MBA with an emphasis on corporate finance (LUISS Business School and the University of San Diego, 2012), and worked as a financial analyst at a real-estate investment firm in San Diego and as an assistant controller. His work focuses on business model strategy, business engineering and, more broadly, structural analysis: how companies make money, read from their own filings. He created FourWeekMBA and leads research there and at The Business Engineer, his newsletter on AI and business strategy, with over 95,000 subscribers and more than 1,000 published analyses. His writing has also appeared on Entrepreneur (for example, How to Digitize a Family Business in Europe) and HackerNoon. Find him on LinkedIn and Substack. See how we source.
