PatchNote Reel
Turns a Steam patch-notes changelog into a 20-second captioned vertical video for TikTok and Shorts, aimed at solo indie devs.
One product, one founder, thirty days. Everything below is built to be executed inside the contest window — the official rules still decide what counts.
Decide in 20 seconds
The facts that decide whether this is worth thirty days of yours.
Solo indie game developers with a live or Early Access Steam page who ship regular patches and post their own social media.
Market demand 3.9/10
Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.
Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 9; 26 sales at $39 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.6/10.
Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.
Your first 24 hours
15 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Solo indie game developers with a live or Early Access Steam page who ship regular patches and post their own social media.
Why now
Short-form video is the only free discovery channel left for solo devs, and AI rendering is cheap enough to sell a finished MP4 for $39 at a profit.
Problem
Patch notes die in Steam's news feed; the dev has no time or editing skill to cut them into short-form video that reaches new players.
Solution
The tool scrapes the patch-notes URL, extracts 3-5 highlight beats, renders a captioned vertical MP4 with store screenshots and a wishlist end card, then delivers a download link after Stripe checkout.
1. Product opportunity and positioning
PatchNote Reel takes text a solo indie developer has already written — a Steam patch-notes changelog — and returns a finished 20-second captioned vertical video for TikTok, Shorts and Reels. Nothing else changes hands: no editor to learn, no timeline, no asset pack.
The buyer is narrow on purpose. It is a solo indie developer with a live or Early Access Steam page who ships patches on a visible cadence and runs their own social accounts. No marketing hire, no publisher, no agency. JEV scored this concept 61.6/100 (band C), with speed to first revenue at 8.59 as its strongest criterion and market demand at 3.92 as its weakest. The weakness is not the customer; it is the absence of a stated trigger. So the whole positioning hangs on one trigger event: the day a patch goes live. That is the moment the dev has fresh text, a reason to post, and no time. Every outreach message, every landing-page headline and every sales conversation should reference that patch, not "your game" in general.
The alternative the dev uses today is CapCut on a phone, or nothing. CapCut is free, so the pitch cannot be "editing software." The pitch is "you already wrote the changelog; here is the post." That reframing is what makes a $39 one-time charge feel like a rounding error against the hours it replaces.
Positioning statement: for solo devs who just shipped a patch and have nothing to post, PatchNote Reel is the fastest path from changelog text to a vertical video that ends in a wishlist call-to-action.
The wedge is commercially viable because the input is free and public (Steam news pages), the output is a single file, and delivery cost per order is a few cents of API and render time. There is no marketplace cold-start, no procurement cycle and no approval gate: a dev can see a sample of their own game, pay, and download inside one sitting.
What this is not: it is not a playable teaser generator, not a game engine, not a scheduling tool. The concept deliberately stays on the smallest unit of work that can be judged in under five minutes.
2. Smallest sellable MVP
The MVP is one page with one input box. Paste a Steam news URL or raw changelog text, pick a template, and after a short render the founder (or the system) returns an MP4. The sellable unit is the Patch Pack: three rendered vertical videos plus caption text files and one revision, for $39 one-time.
Everything that does not move a dev from changelog to MP4 is cut: no accounts, no dashboard, no teams, no scheduling, no analytics, no asset library. In v1 the founder can even run the first renders semi-manually behind a Stripe payment link — the customer experience is what matters, not the automation.
3. Technical implementation plan
Stack: Next.js on Vercel, OpenAI API for highlight extraction, Remotion (React) or FFmpeg for rendering, Supabase for job state and file storage, Stripe Checkout for payment. Rendering runs in a serverless function or a single small worker container; files live in Supabase Storage with signed URLs.
Flow: POST a URL → fetch and strip the Steam news HTML → send the cleaned text to an LLM with a strict JSON schema asking for 3-5 beats (headline, one supporting line, suggested screenshot) → load a fixed vertical template (1080x1920) → render beats as timed caption cards over the fetched store screenshots → append a wishlist end card → write MP4 to storage → email or display the signed download link.
Hardest risk: render time and codec compatibility. Serverless function limits will bite on a 20-second 1080p encode, so plan for a fallback: queue the job, render on a small always-on worker or a render API, and cap the first version at 720x1280 if needed. Second risk: Steam page structure changes; keep the parser behind a single module with a raw-text paste fallback so a scrape failure never blocks a paying order.
4. Pricing and monetization
Two tiers. Patch Pack — $39 one-time, three videos, caption files, one revision: aimed at the dev who ships this month and wants to try it once. Studio Monthly — $99/month, ten videos and priority queue: aimed at the dev or micro-studio shipping weekly.
$39 is chosen so a solo dev can approve it without a conversation. The one-time tier exists to remove subscription fear in a first purchase; the monthly tier exists to convert repeat buyers after the second patch. Upsell path: after a Patch Pack is delivered, offer the monthly plan at the moment the next patch lands.
Payment processing assumed at ~6% (Stripe standard plus international card mix). Delivery cost per order is small but real (LLM tokens, render compute, storage), so the floor is roughly $1-3 per video — well under price, which keeps the contest's below-cost rule satisfied.
5. First-customer acquisition
One channel only: direct replies to indie devs posting patch notes on X and r/IndieDev. The motion is sample-first. Find a dev who posted a changelog in the last 72 hours, render one free 20-second clip from their public notes, and reply or DM with the clip and a $39 offer for three. Follow up once after 48 hours with a second free clip.
Volume target: 20 free samples per day from day 6 onward. Conversion assumption is deliberately conservative — a few percent — because cold replies are cold replies.
6. 30-day execution roadmap
Days 1-5 are build: parser, LLM beats, renderer, checkout, delivery, QA on five real changelogs. MVP ships day 5. Days 6-9 are first-sample outreach and the first sale target on day 9. Days 10-21 alternate between rendering-quality improvements driven by buyer feedback and outreach volume increases. Days 22-30 push collected revenue before the December 16 close, add a $79 six-video bundle, and reconcile every payment in TrustMRR. No paid ads before day 20; organic outreach spend is $0.
7. Revenue and profit scenarios
Three projections, all labelled as projections and none verified. Conservative: 4 customers at $39 → $156 gross. Base: 14 customers at an average $43 (mostly Patch Packs, one monthly) → $602. Upside: 40 customers at an average $47, including a $100 ad test → $1,880. Contest profit deducts refunds, chargebacks, processing fees and paid marketing only; hosting and API delivery sit in operating costs and are not deducted for ranking. Every scenario nets positive.
8. Main risks and validation experiments
Render quality (kill test: if fewer than 1 in 15 free-sample recipients replies, the output is not good enough). Devs preferring to self-edit (kill test: if 20 recipients say "I'd rather do it myself" and zero pay, re-cut the offer around speed, not quality). Steam scraping breaks (mitigation: raw-text paste fallback). Outreach volume too low (mitigation: 20 samples/day floor, tracked in a sheet).
9. First 24 hours
Reserve the domain, scaffold the Next.js repo, wire Stripe test mode, build the parser against three real Steam changelogs, and produce one hand-made sample video end to end. By hour 24 the goal is a working render of a real dev's patch notes — not a landing page.
All figures above are projections from stated assumptions, not verified revenue, customers or traction.
Smallest sellable MVP
One page: paste a Steam patch-notes URL or text, receive a rendered 20-second captioned vertical MP4 with a wishlist end card, paid via Stripe Checkout at $39 for three videos.
Must-have features
- Steam news URL parser with raw-text paste fallback
- LLM extraction of 3-5 highlight beats as strict JSON
- Vertical 1080x1920 template renderer with burned-in captions
- Screenshot and header image pull from the Steam store page
- Optional wishlist end card
- MP4 export and signed download link delivery
- Stripe Checkout with automatic post-payment delivery
- Manual render trigger for the first orders
Explicitly out of scope
- No playable demos or game engine
- No social scheduling or auto-posting
- No team accounts or collaboration
- No analytics dashboard
- No asset library
- No subscriptions billing portal in v1
- No mobile app
Demo flow (what the buyer sees)
- Dev pastes a Steam news URL
- Parser fetches and cleans the changelog text
- LLM returns 3-5 beats with captions
- Renderer pulls store screenshots and builds the vertical timeline
- MP4 is encoded with burned-in captions
- Wishlist end card is appended
- Signed download link is issued
- Dev posts the file to TikTok or Shorts
Technical implementation plan
Stack
Architecture
A single Next.js app handles the form, the parse call and the checkout. Parsing and LLM beat extraction run as one API route. Rendering is dispatched as a background job that a small worker picks up, encodes the MP4 and writes it to Supabase Storage. Stripe webhook marks the order paid and issues a signed download URL. No long-running state beyond a jobs table.
Build steps
- Scaffold Next.js app and deploy to Vercel
- Build Steam news fetcher and HTML-to-text cleaner
- Add raw-text paste fallback path
- Prompt OpenAI with a strict JSON schema for 3-5 beats
- Build Remotion composition: caption card, screenshot slot, end card
- Add MP4 encode and Supabase Storage upload
- Wire Stripe Checkout and webhook to release the download link
- Add job queue table and retry on render failure
- QA against five real patch notes from different studios
- Add simple request logging for follow-up outreach
AI components
- OpenAI LLM converts changelog text into 3-5 ordered caption beats with a headline per beat
- Optional LLM pass to shorten captions to under 60 characters for vertical readability
Pricing and monetization
Patch Pack
Entry offerFor Solo dev shipping a patch this month
- Three rendered vertical videos
- Caption text files
- One revision
Studio Monthly
For Dev or micro-studio shipping weekly
- Ten videos per month
- Priority render queue
Model: One-time $39 Patch Pack for first purchase, $99/month Studio plan for devs shipping weekly.
First revenue offer: A free 20-second clip rendered from your latest public patch notes, plus $39 for two more videos and caption files if you want the set.
Expected ACV: $43
Upsell path: Offer Studio Monthly when the buyer's next patch ships; bundle six videos for $79 to raise order value before the deadline.
First-customer acquisition
Direct replies and DMs to solo indie devs posting patch notes on X and r/IndieDev, sample-first.
Where to find them
- X search for 'patch notes' plus 'Steam' filtered to the last 72 hours
- r/IndieDev and r/gamedev weekly update threads
- Steam 'Recently Updated' and 'Coming Soon' lists for solo-looking pages
- Devlogs on itch.io linking to a Steam page
- Discord servers for indie dev communities with a show-your-update channel
Exact outreach motions
- Reply to a patch-notes post with the rendered clip attached and no pitch in the first line
- DM the same dev with the clip plus the $39 Patch Pack offer
- Follow up after 48 hours with a second free clip from a different section of the notes
- Quote-tweet three public samples per week with the dev tagged
- DM devs from the Steam 'Recently Updated' list who posted notes but no video
Message template
Hey [name] — I turned your 1.4 patch notes into a 20-second vertical clip (attached, made from your public changelog, nothing else). If it's useful I'll do three more plus caption files for $39. If not, keep this one, no strings.
30-day execution roadmap
Week 1 · Build & validate · 7 days
Repo and landing page
- Scaffold Next.js repo and deploy to Vercel
- Write the single-input landing page with the $39 offer
- Reserve domain and connect Stripe test keys
Deliverable: Live landing page collecting emails
Steam news ingestion
- Build Steam news fetcher and HTML-to-text cleaner
- Add raw-text paste fallback
- Test against five real changelogs
Deliverable: Parser module passing on five real pages
Highlight extraction
- Prompt the LLM for 3-5 caption beats with strict JSON
- Cap caption length at 60 characters
- Cache results per changelog URL
Deliverable: Beat JSON for ten real changelogs
Vertical video output
- Build the Remotion vertical composition
- Add screenshot pull and end card
- Encode MP4 and upload to Supabase Storage
Deliverable: First end-to-end MP4 from a real URL
Checkout and delivery
- Wire Stripe Checkout and webhook
- Issue signed download link on payment
- Run five full orders in test mode
Deliverable: MVP live and purchasable (MVP deadline)
Build the outreach list
- Collect 100 devs who posted patch notes in 72 hours
- Log each in a sheet with game, patch date, handle
- Render ten free samples
Deliverable: 100-row prospect sheet, ten samples rendered
First sample wave
- Send 30 free samples with the $39 offer
- Reply to any thread responses within an hour
- Log every send and outcome
Deliverable: 30 samples delivered
Week 2 · Launch & first sale · 7 days
Convert replies
- Follow up all day-7 sends with a second clip
- Send 20 new samples
- Fix any render failure reported by a recipient
Deliverable: First paid order or documented objection list
Close
- Send 20 more samples
- Offer the $39 Patch Pack directly in every open DM
- Trigger delivery manually for the first buyer if needed
Deliverable: First verified payment (first sale target)
Render polish from feedback
- Fix the top three visual complaints
- Add a second caption style
- Re-render any underwhelming samples
Deliverable: v1.1 templates shipped
Outreach scale
- Send 25 samples to new prospects
- Post one public sample on X
- Reply to every comment
Deliverable: 25 sends, one public post
Publish the workflow
- Post a thread showing changelog to clip in three steps
- Ask the first buyer for a one-line quote
- Add the quote to the landing page
Deliverable: Live thread plus landing page proof block
- Post a sample in r/IndieDev following subreddit rules
- Answer questions in comments
- Capture new prospects from replies
Deliverable: One Reddit post, ten new prospects
Conversion math
- Compute samples sent, replies, paid orders
- Kill the message angle under 2% reply rate
- Rewrite the winner
Deliverable: Channel scorecard and revised message
Week 3 · Repeat & systematize · 7 days
Launch monthly tier
- Enable Studio Monthly at $99 on the site
- Email past buyers with the monthly option
- Add priority queue flag
Deliverable: Second tier live
Steam list prospecting
- Pull 50 recently updated solo-looking Steam pages
- Render 15 samples
- Send 30 DMs
Deliverable: 50 new prospects, 30 sends
Dev Discords
- Join three indie dev Discords
- Share two samples where allowed
- Collect ten warm handles
Deliverable: Three joined communities, ten warm leads
Template presets
- Ship three caption style presets
- Add a font size control
- Test render time at 1080p
Deliverable: Three presets live
Recover cold threads
- Follow up every non-reply from days 11-16
- Send one new clip per follow-up
- Report reply rate
Deliverable: Full follow-up sweep logged
End card customization
- Let devs set the wishlist URL on the end card
- Add a logo slot
- Upload a sample to show it
Deliverable: Custom end card live
Midpoint numbers
- Tally collected revenue and pending invoices
- Cut the weakest outreach message
- Set the day 22-30 send target
Deliverable: Midpoint dashboard snapshot
Week 4 · Scale what works · 9 days
Batch rendering
- Add batch submit for multiple changelogs
- Queue jobs with visible status
- Test a five-video batch
Deliverable: Batch queue working
Past buyers
- Offer Studio Monthly to every Patch Pack buyer
- Offer a second pack at a $29 add-on
- Log acceptances
Deliverable: Upsell round completed
Public samples
- Post three public clips from opted-in devs
- Ask each dev to quote-tweet
- Link the landing page in every post
Deliverable: Three public posts live
Push sends
- Send 40 samples
- Target devs who shipped in the last 48 hours
- Track hourly reply rate
Deliverable: 40 sends, reply count logged
Bundle test
- Add a $79 six-video bundle
- A/B the bundle against the $39 pack
- Record which converts better
Deliverable: Bundle live with split data
Testimonials
- Collect three buyer quotes
- Publish them on the landing page
- Add view counts where buyers shared results
Deliverable: Three testimonials published
Deadline urgency
- DM all warm leads with the December 16 cutoff
- Offer same-day render for orders placed today
- Clear the render queue
Deliverable: All warm leads contacted once more
Last call
- Send a final-call message to non-openers
- Deliver every outstanding order
- Stop taking orders 12 hours before close
Deliverable: Zero undelivered orders
Books and reconciliation
- Reconcile Stripe payouts against TrustMRR
- Process any refunds
- Record final collected revenue and write the post-mortem
Deliverable: Reconciled revenue record and post-mortem
Revenue and profit scenarios
How the numbers are defined
Hackathon profit — Collected revenue − refunds − chargebacks − payment processing fees − paid marketing spend.
Business profit — Hackathon profit − operating costs (hosting, domains, tooling, AI/API delivery costs).
The contest ranks entrants on hackathon profit only. Hosting, tooling and AI/API delivery costs are not deducted by the organisers, but each sale still has to cover them — so we show both. Definitions verified on 2026-11-15 against the official rules.
Stated assumptions
- Conservative/Base/Upside: ARPU blends the $39 Patch Pack with occasional $99 monthly plans.
- Conservative: 4 buyers from roughly 300 samples sent, no paid marketing.
- Base: 14 buyers, one of them on Studio Monthly, outreach at 20 samples/day.
- Upside: 40 buyers helped by a $100 paid boost on X and one bundle promotion.
- Payment processing assumed at ~6% of collected revenue (Stripe standard plus international card mix).
- Refunds assumed at one order in Base and two in Upside; chargebacks assumed zero.
- Operating costs cover Vercel, Supabase storage, LLM tokens and render compute at roughly $1-3 per delivered video.
- All three scenarios are projections from stated assumptions, not verified revenue.
Conservative
4 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $9
- Paid marketing
- $0
- Hackathon profit
- $147
- Operating costs
- $20
- Business profit
- $127
Base case
14 customers- Refunds
- $39
- Chargebacks
- $0
- Payment fees
- $36
- Paid marketing
- $0
- Hackathon profit
- $527
- Operating costs
- $45
- Business profit
- $482
Optimistic
40 customers- Refunds
- $78
- Chargebacks
- $0
- Payment fees
- $113
- Paid marketing
- $100
- Hackathon profit
- $1,589
- Operating costs
- $90
- Business profit
- $1,499
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $546
- Payment fees (3.9%)
- $21
- Paid marketing
- $0
- Hackathon profit
- $525
- Business profit
- $480
Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.
Scenario models from stated assumptions, not verified revenue.
Main risks and validation experiments
Risk 1Rendered videos look amateur and devs will not post them.
Ship three polished caption presets, fix the top three visual complaints within 24 hours of each buyer, and hand-check the first 20 renders before sending.
Send 15 free samples on day 7 and count replies within 72 hours.
If fewer than 1 in 15 recipients replies and zero pay after 60 samples, the output quality is not sellable and the template work is the blocker.
Risk 2Devs prefer editing clips themselves in CapCut for free.
Pitch speed and the finished file, not editing capability; show a side-by-side of time spent.
Ask every non-buyer one question: how long would this have taken you to make?
If 20 prospects state they would rather self-edit and none convert, reposition to a done-for-you batch service or abandon.
Risk 3Steam news pages change structure or block scraping, breaking orders.
Raw-text paste fallback on the input page plus a single parser module that can be patched without touching the render pipeline.
Run the parser daily against 20 saved URLs and log failures.
If parser success drops below 70% and the fallback is used in more than half of orders, stop selling URL-only entry.
Risk 4Outreach volume too low to reach even the conservative scenario.
A hard floor of 20 free samples per day from day 6, tracked in one sheet with sends, replies and payments.
Measure sends per hour on day 7 and day 11 to set a realistic daily cap.
If fewer than 200 samples can be sent in 14 days, the channel does not support this price and the acquisition motion must change.
Hour-by-hour: the first 24 hours
Hours 1-2
- Reserve domain and create the Next.js repo
- Set up Vercel project and Stripe test account
- Draft the single-input landing page copy
Output: Deployed skeleton page with the $39 offer
Hours 3-5
- Build the Steam news fetcher and HTML cleaner
- Test on three real changelogs and save raw text fixtures
- Add the raw-text paste fallback
Output: Working parser plus three saved fixtures
Hours 6-8
- Write the LLM prompt for 3-5 caption beats
- Run it on the three fixtures
- Inspect output for caption length and ordering
Output: Beat JSON for three real patch notes
Hours 9-12
- Build one Remotion vertical composition by hand
- Pull screenshots from one store page
- Render a single MP4 at 720x1280
Output: One finished sample video from a real game
Hours 13-16
- Build the 50-handle prospect list from recent patch notes
- Send the first five free samples with the offer
- Log sends in a sheet with timestamps
Output: Five samples sent and a prospect sheet started
Full 30-day launch report
Read the full generated report
PatchNote Reel — 30-Day Public Report
Concept PatchNote Reel v1, scored 61.6/100 (band C) by JEV. All revenue figures in this report are projections from stated assumptions. No customers, revenue, partnerships or traction exist yet.
1. Product opportunity and positioning
PatchNote Reel takes text a solo indie developer has already written — a Steam patch-notes changelog — and returns a finished 20-second captioned vertical video for TikTok, Shorts and Reels. Nothing else changes hands: no editor to learn, no timeline, no asset pack.
The buyer is deliberately narrow: a solo indie developer with a live or Early Access Steam page who ships patches on a visible cadence and runs their own social accounts. No marketing hire, no publisher, no agency. JEV's weakest criterion for this concept is market demand (3.92), and the hint attached to it is to name the trigger event that creates willingness to pay. That trigger is the day a patch goes live. At that moment the dev has fresh text, a reason to post, and no time. Every landing-page headline, outreach message and sales conversation should reference that specific patch, not "your game" generically.
The alternative today is CapCut on a phone, or nothing at all. CapCut is free, so the pitch cannot be editing software. The pitch is: you already wrote the changelog, here is the post. That reframing makes $39 feel like a rounding error against the hours it replaces.
Positioning statement: for solo devs who just shipped a patch and have nothing to post, PatchNote Reel is the fastest path from changelog text to a vertical video ending in a wishlist call-to-action.
The wedge is commercially viable because the input is public (Steam news pages), the output is a single file, and delivery cost per order is a few cents of API and render time. There is no marketplace cold-start, no procurement cycle and no approval gate: a dev can see a sample of their own game, pay and download in one sitting.
What this is not: not a playable teaser generator, not a game engine, not a scheduling tool. The concept stays on the smallest unit of work that can be judged in under five minutes.
2. Smallest sellable MVP
One page with one input box. Paste a Steam news URL or raw changelog text, pick a template, receive an MP4. The sellable unit is the Patch Pack: three rendered vertical videos, caption text files and one revision for $39 one-time.
Everything that does not move a dev from changelog to MP4 is cut: no accounts, no dashboard, no teams, no scheduling, no analytics, no asset library. For the first orders the founder can render semi-manually behind a Stripe payment link. The customer experience is what matters, not the automation.
3. Technical implementation plan
Stack: Next.js on Vercel, OpenAI API for highlight extraction, Remotion or FFmpeg for rendering, Supabase for job state and file storage, Stripe Checkout, Resend for delivery.
Flow: submit a URL, fetch and strip the Steam news HTML, send cleaned text to an LLM with a strict JSON schema requesting 3-5 beats (headline, one supporting line, suggested screenshot), load a fixed 1080x1920 template, render timed caption cards over fetched store screenshots, append a wishlist end card, write the MP4 to storage, and issue a signed download link.
Hardest risk: render time and codec compatibility. Serverless limits will bite on a 20-second 1080p encode, so plan a fallback — queue the job to a small always-on worker or a hosted render API, and cap v1 at 720x1280 if needed. Second risk: Steam page structure changes. Keep parsing behind one module with a raw-text paste fallback so a scrape failure never blocks a paying order.
4. Pricing and monetization
Two tiers. Patch Pack at $39 one-time — three videos, caption files, one revision — for the dev shipping this month who wants to try once. Studio Monthly at $99/month — ten videos and priority queue — for the dev or micro-studio shipping weekly.
$39 is set so a solo dev approves without a conversation; the one-time option removes subscription fear on a first purchase. Upsell happens when the next patch lands: offer the monthly plan at the moment the dev has new text in hand. Payment processing is assumed at roughly 6% of collected revenue. Delivery cost is real but small, roughly $1-3 per video, comfortably under price, which keeps the contest's below-cost rule satisfied.
5. First-customer acquisition
One channel only: direct replies and DMs to indie devs posting patch notes on X and r/IndieDev. Sample-first. Find a dev who posted a changelog in the last 72 hours, render one free 20-second clip from their public notes, reply or DM with the clip and a $39 offer for three more. Follow up once after 48 hours with a second free clip.
Volume target is a hard floor of 20 free samples per day from day 6, tracked in one sheet with sends, replies and payments. Conversion expectations stay deliberately conservative, because cold replies are cold replies.
6. 30-day execution roadmap
Days 1-5 are build: parser, LLM beats, renderer, checkout, delivery, QA on five real changelogs. MVP ships day 5. Days 6-9 are sample outreach with a first-sale target on day 9. Days 10-21 alternate between render-quality fixes driven by buyer feedback and rising outreach volume, plus the launch of the $99 monthly tier on day 15. Days 22-30 push collected revenue before the December 16 close, test a $79 six-video bundle, and reconcile every payment in TrustMRR. No paid ads before day 20; organic outreach spend is $0.
7. Revenue and profit scenarios
Three projections, all labelled projections and none verified. Conservative: 4 customers at $39, $156 gross. Base: 14 customers at an average $43 (mostly packs, one monthly), $602 gross. Upside: 40 customers at an average $47 with a $100 paid boost, $1,880 gross.
Contest profit deducts refunds, chargebacks, processing fees and paid marketing only. Hosting, domains and AI delivery sit in operating costs and are not deducted for ranking. Base case after fees, one refund and operating costs leaves roughly $482 of business profit; the conservative case leaves roughly $127. Every scenario is positive, and each delivered video costs far less than its price.
8. Main risks and validation experiments
Render quality. If fewer than 1 in 15 free-sample recipients replies and zero pay after 60 samples, the output is not sellable and template work is the blocker.
Self-editing preference. Ask every non-buyer how long this would have taken them in CapCut. If 20 prospects say they would rather self-edit and none convert, reposition around batch done-for-you or abandon.
Steam scraping. Run the parser daily against 20 saved URLs. If success drops below 70% and the fallback carries more than half of orders, stop selling URL-only entry.
Outreach volume. If fewer than 200 samples can be sent in 14 days, the channel cannot support this price and the acquisition motion must change.
9. First 24 hours
Reserve the domain, scaffold the Next.js repo, wire Stripe test mode, build the parser against three real Steam changelogs, prompt the LLM for beats, hand-build one Remotion template and render a single MP4 from a real game, then send five free samples. By hour 24 the goal is a working render of a real dev's patch notes and five live outreach messages — not a landing page.
All figures above are projections from stated assumptions, not verified revenue, customers or traction.
This brief was generated from public data about established startups, then narrowed and scored for a solo 30-day launch. Revenue and profit figures are scenario models, not verified results, guarantees or evidence of existing customers. Validate demand yourself before you spend a month on it — and check the contest rules for what counts toward your score.
Related ideas
All ideas →Hookframe
Hookframe turns an app icon, a few screenshots and one chosen mechanic into a single-file, MRAID-safe playable ad under 5MB that an indie mobile studio can upload to Meta or AppLovin the same day.
CoachScribe
CoachScribe turns a 2-minute voice memo from a gaming coach into a branded, structured PDF feedback report for their student, automating the post-session follow-up.
Pitch Rehearsal Scorecard
A voice rehearsal tool that turns a non-native founder's investor pitch into a scored, annotated audio scorecard they can fix before the real meeting.