You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Short answer: the reach figures are enormous, the organic-share figures are suspiciously high, and the number that decides whether any of it is worth doing is the weekly hour count nobody puts in the headline. What follows is every figure this repo has collected on that, each kept with the sentence it was published in and the date it was read.
The figures that exist, and where each came from
95 percent — "The developer posts 3 to 5 a week across several platforms, mostly product demos and short tutorials, and 95 percent of signups arrive organically." (2026-08-11)
12 hours — "The overall commitment is roughly 12 hours a week on video creation and platform management." (2026-08-11)
2 hours — "Editing takes about 2 hours per 60-second video, including AI-assisted effects and transitions." (2026-08-11)
20 percent — "AI tooling produced about a 20 percent increase in content output with no corresponding increase in monetization." (2026-08-11)
60 percent / 40 percent — "Roughly 60 percent of the video content gets reused across platforms, cutting production time by about 40 percent." (2026-08-11)
9.1% → 55.1% — "One reported case moved entry-group conversion from 9.1% to 55.1% by rebuilding an automated onboarding flow." (2026-08-19)
$3–$4 — "With a budget as low as $30 per day, developers have reached an effective lead cost of $3 to $4." (2026-08-20)
3 months — "StoryShort matched, in 3 months, the revenue that an established B2B tool took 2 years to build." (2026-08-12)
The one that does not survive contact. "A product with 200 users and a product with 200,000 can both report 95 percent organic, and the strategy that produced them has nothing in common." A percentage with no denominator is not a result.
The arithmetic the headline leaves out. Four videos a week at two hours of editing each is eight hours before anyone has written a script, answered a comment, or looked at analytics. The 20 percent more output that AI tooling bought moved no money at all in the case it came from — twenty percent more of a demo that does not land is twenty percent more of nothing.
The one thing worth replying with: if you post short video for a product you built, how many hours a week does it actually take you — and how many signups came from it last month? A one-line reply with hours and a raw count (not a percentage) is worth more than any row above, and it goes into the table with your wording kept.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Short answer: the reach figures are enormous, the organic-share figures are suspiciously high, and the number that decides whether any of it is worth doing is the weekly hour count nobody puts in the headline. What follows is every figure this repo has collected on that, each kept with the sentence it was published in and the date it was read.
The figures that exist, and where each came from
95 percent— "The developer posts 3 to 5 a week across several platforms, mostly product demos and short tutorials, and 95 percent of signups arrive organically." (2026-08-11)12 hours— "The overall commitment is roughly 12 hours a week on video creation and platform management." (2026-08-11)2 hours— "Editing takes about 2 hours per 60-second video, including AI-assisted effects and transitions." (2026-08-11)20 percent— "AI tooling produced about a 20 percent increase in content output with no corresponding increase in monetization." (2026-08-11)60 percent/40 percent— "Roughly 60 percent of the video content gets reused across platforms, cutting production time by about 40 percent." (2026-08-11)9.1%→55.1%— "One reported case moved entry-group conversion from 9.1% to 55.1% by rebuilding an automated onboarding flow." (2026-08-19)$3–$4— "With a budget as low as $30 per day, developers have reached an effective lead cost of $3 to $4." (2026-08-20)3 months— "StoryShort matched, in 3 months, the revenue that an established B2B tool took 2 years to build." (2026-08-12)The one that does not survive contact. "A product with 200 users and a product with 200,000 can both report 95 percent organic, and the strategy that produced them has nothing in common." A percentage with no denominator is not a result.
The arithmetic the headline leaves out. Four videos a week at two hours of editing each is eight hours before anyone has written a script, answered a comment, or looked at analytics. The
20 percentmore output that AI tooling bought moved no money at all in the case it came from — twenty percent more of a demo that does not land is twenty percent more of nothing.All 335 figures as JSON/CSV: https://xyzs996.github.io/llm-api-pricing/figures.html
Write-ups with the full context:
The one thing worth replying with: if you post short video for a product you built, how many hours a week does it actually take you — and how many signups came from it last month? A one-line reply with hours and a raw count (not a percentage) is worth more than any row above, and it goes into the table with your wording kept.
All reactions