Office Hours 2026 · 08 · 08 Reelly · main Startup mode

You have not been evaluating a startup. You have been evaluating a demo path.

Reelly’s market is real, its ad data is honest, and its render engine works. The shipping build takes the first 1.5 seconds of every clip, sorted by capture date. Every strategic question asked so far was asked about a product nobody has run.

One source clip · 6.0s handheld
Reelly takes this
The moment
0.0s1.5s3.0s4.5s6.0s
The first second and a half of real handheld footage is the phone coming up, the framing settling, a blurry pan. Reelly selects it every time, in every clip. The golden moment further in is what the app was built to find, and what it currently never reaches.
The finding

Read out of the source, not inferred

ios/AutoClipping/Rendering/ReelRenderer.swift:87 let srcRange = CMTimeRange(start: .zero, duration: take)
ios/AutoClipping/Studio/ReelStudio.swift:83 let orderedClips = await CaptureDate.ordered(clipURLs)

That is the whole selection logic: sort by timestamp, take the head of each clip. Meanwhile ios/AutoClipping/Indexing/ is built and benchmarked. Six VLMs evaluated, a two-model split decided, 3/3 on short-clip golden-moment ground truth and 4/4 on long, per-clip screenplay beats, roughly four cents a reel. Nothing outside that folder calls it.

the only external reference · AutoClippingApp.swift:10 return try ModelContainer(for: ClipAsset.self)

It builds the container and stops there. From the app’s perspective the entire selection layer is dead code.


Where things actually stand

The ledger

Settled · stop re-testing
Best creative CTR, Meta2.71%
Cost per signup, best creative$4.11
Landing page → email21%
Total spend · signups$276 · 26
Near-exact comp run rate$7.2M/yr
Comp’s recent 1–3★ reviews61%
Travel mentions in 120 comp reviews1
Unknown · decides everything
Reels you made for your own life0
Users who have ever opened it0
D7 second-reel rateno data
Willingness to payuntested
A named human who needs thisnone
Output quality vs free CapCutunmeasured
Times the real product has run0

The left column cost $276 and three weeks. The right column is what decides whether there is a business, and none of it can be bought with ad spend.


The market

Is there money here, and can a newcomer still reach it?

Two separate questions that get collapsed into one. The first is easy and settled. The second is the one worth checking, because a category can be enormous and closed at the same time.

Question one · does anyone pay for this

Yes, and not only at the Canva end. The revenue curve has occupied rungs all the way down, which is what makes it a market rather than a monopoly with a tail.

US App Store · monthly estimates · ✓ = re-pulled live 2026 - 08 - 08
App Released Downloads Revenue Per dl Rating Src
Canva20145.1M$33.7M$6.60doc
Meitu20113.1M$13.3M$4.33doc
Videoleap201760k$1.0M$16.67doc
Vids AI the compAug 2022200.6k$601.8k$3.004.78
Dance AI 6 months oldFeb 2026218.4k$547.9k$2.514.60
Pixi AIDec 202530.6k$305.6k$10.002.42
VixelJan 2026100.3k$200.6k$2.003.96
Sora by OpenAISep 2025358.0k$123.2k$0.344.76
Muse Cam 7 weeks oldJun 2026100.0k$116.2k$1.164.94
ReelinaDec 20257.3k$104.3k$14.303.66
Halo AIOct 202571.1k$101.6k$1.434.35
AI CutNov 202573.7k$63.2k$0.864.52

Download and revenue figures are third-party AppKittie estimates, directional rather than audited. Per-download revenue is monthly revenue over monthly downloads, so it is a monetisation-intensity ratio, not a per-user lifetime value. Canva, Meitu and Videoleap are carried from go-no-go-2026-08-05.md and were not re-checked; every row marked ✓ was pulled live and matched to the decimal.

Question two · can a newcomer still get there

Nine apps in that table launched after September 2025. All nine clear $60k a month, the youngest is seven weeks old, and none of them is a rounding error. This is a cohort, not two cherry-picked survivors. Incumbency in this category is not decisive, because distribution runs through organic TikTok rather than App Store charts.

The single sharpest data point

Dance AI shipped in February 2026 and is at $548k a month. Vids AI took four years and 45,002 reviews to reach $602k. A six-month-old app is within nine percent of it. Whatever moat exists here, it is not time served.

The finding neither doc had

Sort that cohort by revenue per download and a pattern falls out of the two ends. The hardest monetisers are the worst-rated apps, and the best-rated apps barely monetise at all.

Monetisation intensity against sentiment
App Per dl Rating Reviews
Reelina hardest paywall$14.303.66215
Pixi AI$10.002.4255
Vids AI$3.004.7845,002
Dance AI$2.514.6014,721
Vixel$2.003.961,640
Halo AI$1.434.351,970
Muse Cam$1.164.948,262
AI Cut$0.864.52663
Sora softest paywall$0.344.76249,463

The extremes are clean and the middle is genuinely noisy, so treat it as a tendency rather than a law. But it reframes the free-tier question you were carrying as a pure cost problem. Squeezing revenue per download in this category appears to cost sentiment directly, and sentiment is what feeds the organic TikTok distribution everyone here actually grows on. The incumbent’s 4.78 lifetime rating is propped up by older reviews while 61% of its recent ones are one to three stars. That is what this trade looks like partway through.

Also worth noting

Sora sits inside this category at $0.34 per download against Vids AI’s $3.00. Generative video has not eaten the edit-my-own-footage subscription market. Different job, different wallet, at least for now. Nobody asked the three-year question in this session, and this is a partial answer to it.

What $10k a month actually needs

Per-download revenue ranges from $0.34 to $14.30 across the verified set. That is not a market constant you inherit, it is a paywall-aggression dial you set, and the table above shows what each setting costs in sentiment. So the target depends on which app you decide to be.

Correction to the target math

The go/no-go doc sizes $10k a month as roughly 3,300 downloads, using the comp’s $3.00 per download. But that ratio divides this month’s revenue by this month’s downloads, so for a four-year-old app it charges four years of accumulated subscriber revenue against new installs. A launching app does not get that.

$10k/mo ≈ 3,300 downloads/mo at the comp’s $3.00
$10k/mo ≈ 4,000–11,600 downloads/mo at a new entrant’s $0.86–$2.51

Up to three and a half times harder than the number being aimed at. Still a solo-founder number, still reachable through organic TikTok, which is how the comp itself grew. Just calibrate against the right one.

What this does and does not license

Real market is not the same as winnable market. The same dataset says 62,809 apps match this category search, revenue is power-law distributed, and Lightricks, Canva and Meitu can outbid a solo founder in paid acquisition indefinitely. The conclusion elsewhere in this document stands: the market is worth pursuing and the current positioning is not defensible.

Provenance · the market read originated in go-no-go-2026-08-05.md rather than being derived during the session, and carried its own directional caveat. Nine apps were re-pulled live on 2026-08-08 and all nine matched to the decimal, including Vids AI at $601,805 / 200,600 / 45,002 reviews / 4.78. Two claims were corrected in the process: Dance AI is six months old rather than four, and the growth fields are not identical across apps as first written — they are merely very close (Vids AI 2.65/2.65/2.65, but Halo AI 8.60/8.92/8.93, Dance AI 5.01/4.72/5.02). The weaker version holds: download and revenue growth track review growth closely enough that a revenue-growth figure carries little information the review count does not. Absolute revenue is modelled separately and is the more trustworthy of the two. One claim could not be verified and was dropped — a count of Photo & Video apps released since September 2025 above $20k a month, because the category filter rejected every slug format tried. Across all categories that cohort is 1,469.


How we got there

Four questions, four answers

Why zero was the useful answer

The kill criterion in the go/no-go doc is a 30% D7 second-reel rate. Cohort member one has infinite motivation, zero install friction, and wrote every line of the render path. His rate is zero. That reading was free, and it is worse than any number 26 strangers would have produced after a month of TestFlight review and analytics wiring.



The case for

Potential

Proven

People pay for exactly this

A near-identical incumbent runs roughly $7.2M a year on the same one-line pitch. That question is closed and does not need re-asking.

Soft target

The incumbent is vulnerable

61% of its recent reviews are one to three stars against a 4.78 lifetime average, and the top complaint is the paywall rather than the product. A generous free tier is a real wedge.

White space

Travel is unclaimed

One mention across 120 incumbent reviews. Every ad creative that delivered was travel footage, and the winner was a travel montage at $4.11 a signup.

Asset

The hard part is already built

Per-clip screenplay beats and golden-moment windows, benchmarked against ground truth at four cents a reel. CapCut does not know what is in your clips. You do.

Open door

New entrants still break in

Forty-six apps released since September 2025 are already above $20k a month, and one of them reached $548k in four months. Incumbency is not decisive here.

Reachable

The first goal is small

$10k a month needs 7,000 to 11,600 downloads a month at new-entrant monetisation. Harder than the doc’s 3,300, still a solo-founder number rather than a venture one. Aim there.

The case against

Pitfalls

Structural

Travel happens three times a year

The wedge that won on ad performance is hostile to subscription pricing. Nothing in the plan answers this yet, and it should be answered before any paywall work.

Unproven

The wedge has no human behind it

Travel came from creative click-through, not from a person. Ad data tells you which video stopped a scroll. It does not tell you whose problem you solve.

Economics

Indexing costs money per free user

Four cents a reel in a market whose loudest complaint is being charged before seeing value. The obvious wedge and the obvious unit-economics problem are the same decision.

Competitive

CapCut is the measuring stick

Users name it in reviews. Any positioning that does not answer “why not CapCut” fails, and the answer cannot be transitions or music.

Behavioural

Analysis keeps winning over shipping

The go/no-go doc says another demand test is procrastination. It was written after running one, three weeks after the 26 emails arrived. The chosen path defers contact again.

Technical

Content-chosen durations may break WYSIWYG

Preview and export share one composition. If assembly makes segment lengths content-driven, that invariant is at risk. Finding out in week five is expensive.


The plan · approach B, sequenced

Selection first, assembly second, gate between

You chose to rebuild around content understanding rather than wire what exists and re-decide. The objection stands and is resolved by ordering, not override: assembly logic sits on top of selection. If the moment oracle returns mediocre windows on real handheld footage, no narrative arc above it produces a postable reel.

Now

Run the current build on a real trip

Roughly 100 clips, not the demo set, through the head-of-clip path exactly as it ships. Export it and watch it. Half an hour, no engineering, and it is the before-shot you will want in week one.

Week 1

Wire the selection layer into the shipping path

Content-aware ordering replaces sort-by-timestamp. The golden-moment in-point replaces zero. No new UI, no new models, no new research. The renderer already accepts an arbitrary time range, so this changes an argument rather than the engine. Keep the no-API-key fallback intact.

Gate

Export one reel. Post it, or don’t.

Real account, real people who know you. Deciding not to post counts, and is equally informative. This is a gate, not a proof: a pass proves little, a fail is decisive.

PASS → proceed to assembly FAIL → selection was not the whole problem; stop and re-diagnose
Wk 2–8

Content-driven assembly

Screenplay beats drive a narrative arc. Templates become story shapes the content selects rather than fixed cuts the user picks. This is the part that answers “why not CapCut,” and it is open work rather than wiring.

Held

TestFlight to the 26

Signing, lanes, CI, and the App Store Connect record are all ready. Three sub-day blockers remain: the home screen still says AutoClipping, there is no analytics SDK, and the waitlist API only inserts a row. Hold anyway. Twenty-six first impressions do not come back, and spending them on the head-of-clip build buys a number that means nothing.


Unresolved

What this session could not close

The assignment

Put about 100 clips from one real trip on the device, run the build you have today, and watch the export all the way through.

Not the demo set. Not five samples. The real thing at real scale through the path that ships right now. You need the baseline before you change anything, and you have never actually done it — every export so far was a demo, an ad, or a bug repro. Thirty minutes, zero engineering, and it is the only item here that requires no code at all.


Design doc · ~/.gstack/projects/eugenechantk-reelly/eugenechan-main-design-20260808-001202.md
Sources · go-no-go-2026-08-05.md, format-test-readout-2026-08-06.md, proving-demand-without-building.md, ios/AutoClipping/{Rendering,Studio,Indexing}
Session 2 · prior project fiftyworkout · signals: real problem, pushback, domain expertise, taste, agency