Clera

The Clera beta has been out for a month. Before I start spending more time on distribution, I wanted to know whether I was building for the right person.

I ran 8 async voice interviews through UserCall. Cold recruits, not existing beta users. Five questions, each answered with a short voice clip. All 8 completed in a single day.

Here is what I found.

The saved-reel graveyard: confirmed, 8 of 8

Every respondent described the same pattern. They save reels with genuine intent and never go back. The mechanism is consistent: not friction at save time, but zero resurfacing at the moment they actually need the thing. "Out of sight, out of mind" came up in multiple interviews without prompting.

All 8 saved instructional content. Recipes appeared in 7 of 8. Also travel itineraries, hair care tutorials, language learning, home organization. Nobody was saving comedy for later. Instructional content is the job.

All 8 have a workaround. Screenshots in the camera roll. A dedicated Notes folder with recipes and tutorials. WhatsApp links forwarded to a spouse as an external memory. Phone reminders set at save time. These are the people who felt the problem enough to build something around it. That is a good sign for problem-solution fit.

The finding I was not expecting

The feature they asked for was not summaries. It was resurfacing.

Three or four of the eight, independently, described wanting something that shows up at the right moment. A notification on shopping day. A reminder before a trip. Not "extract the ingredients from this reel." More like: "remind me about this reel when it is relevant."

One participant put it plainly: if they have a reminder in their phone, there is a ninety-five percent chance they will act on it.

I built readability. They described resurfacing. These are related but they are not the same thing. Readability solves "I cannot get the information out of a video." Resurfacing solves "I forget the video exists when I need it." The first gets someone from zero to structured notes. The second is what actually closes the loop.

This will shape the roadmap conversation before I finalize the paywall scope.

The uncomfortable finding

Zero of 8 pay for any save-or-organize tool today. None. One capped willingness to pay at under $3 as a one-off purchase. One said free only. Most gave vague answers.

I am not ready to treat this as a death sentence. These are cold recruits who took a $20 incentive to participate, which selects against the time-poor professional I think is my actual user. Stated willingness to pay is also notoriously unreliable in both directions. The real test is behavioral: do heavy users convert at a higher rate than light users at Day 90? That read is still four months away.

But I am flagging it for the pricing analysis. A low-entry or one-time option belongs on the table alongside the subscription model.

Where the numbers stand

Active beta testers: [INSTALL_COUNT]. Week-2 retention: [WEEK2_RETENTION]%.

Interview completion rate: 8 confirmed interviews from the cold panel cohort. The denominator (10 to 15 recruited) needs confirmation from the UserCall dashboard before I publish a rate. I will update this before the post goes live.

The quantitative ICP check (Signal 1: is at least 60% of summarized content instructional?) runs June 21, not June 12. The backend fix that enables clean measurement deployed May 31. I want 14 clean days of data before I trust the number. Running it on June 12 would give me 11 days and a confidence interval I cannot defend. So I am pushing the read by one week.

What comes next

Full synthesis of interviews, including beta tester responses, lands June 16. The Day 60 free launch is still on track for July 12. Product Hunt the same week.

The thing that keeps me building: the workarounds. When 8 out of 8 strangers built their own systems around the same missing feature, that is not a polite answer to a survey. That is the job.

The honest number from week 1 is 1.

One iOS tester joined the Clera beta. The week-2 target from my 90-day plan was 30 active testers. I am not close to that.

This is post two of a series. Post one set up the plan: 300 weekly active users by August 1, paywall ships the same day, three channels, no ad budget.

What actually shipped

The beta is live on TestFlight and now on Google Play open testing (went live May 11). Both links work. The app does what it says: share a reel from Instagram, get structured notes back. Recipes come back as ingredients and method. Travel reels come back as places and tips. Tutorials come back as numbered steps.

Hook performance

What I can read from the IH post so far: engagement tells me the graveyard-of-intentions framing lands with people who recognize the pattern. The line that got the most traction in the comments was the one about the saved folder: "Instagram's saved tab is a graveyard of intentions." That matches the ICP hypothesis and I am going to use it as the opening hook for the first Reddit value post this week.

What I cannot read yet: which specific hook drives TestFlight installs, because I did not run the beta subreddit posts. I am treating that as week 2 data.

Retention: too early

With 1 iOS tester in the cohort I have no retention signal worth reporting. I am watching three specific things:

1. Do they open the summary library after creating their first summary? (14-day re-open rate)

2. What categories are they summarizing? (recipe/travel/how-to vs comedy/news/other -- below 60% instructional is a signal the ICP is wrong)

3. Does heavy use predict willingness to pay? (can't read this yet, but I am setting up the instrumentation now)

The honest state of these three is: not enough data. I will have something readable by week 4 if the acquisition gap closes this week.

The actual week-1 tracker

Metric Target (day 30) Week 1 actual Active iOS testers 50 1 Active Android testers (ICP) Posts shipped 4 1 (IH milestone #1) 14-day library re-open rate baseline not readable Category mix (instructional %) >= 60% not readable

What week 2 looks like

The graveyard-of-intentions value post goes into r/digitalminimalism today. That is the highest-conviction channel in the plan and I have not touched it yet. I am also posting in r/TestFlight and r/iosbetatesters this week with Hook A and Hook C from the beta callout doc.

Android being in open testing on Google Play opens a second acquisition surface I did not have last week. I am treating it as an experiment: same hooks, watch whether Android or iOS drives more organic installs through subreddit posts.

The 90-day target is 300 weekly active users by August 1. Week 2 I need to exit with at least 15 real testers to keep pace. I will report the actual number in post three.

Stack: Flutter, Gemini 2.5 Flash, Whisper, FastAPI, Hetzner. Solo founder. Nights and weekends.

iOS beta via TestFlight. Android beta via Google Play open testing. Links in profile.

I shipped the Clera beta three weeks ago. No paywall. No revenue. A handful of TestFlight testers, most of them people I know.

Clera turns Instagram Reels into structured notes. Share a reel from Instagram, get back a recipe with ingredients and method. A travel reel gives you a list of places and tips. A tutorial gives you numbered steps. The problem it solves is simple: most people's Instagram saved folder is a graveyard of things they meant to come back to and never did. Clera makes those saves actually usable.

The stack is Flutter, Gemini 2.5 Flash for vision and text, Whisper for transcription. Backend is a FastAPI service on a Hetzner VPS. It works. That part is done.

The part I have not solved yet is distribution.

The commitment

I set a hard goal for myself three weeks ago: 300 weekly active users by day 90. The paywall ships the same day. Not before.

The "not before" matters. I do not want to build a paywall before I know whether anyone actually returns to the app after the first use. If the median user summarizes two reels and never opens the library again, a paywall is the wrong next move. I need to know whether people use the summaries, not just create them.

Day 90 is early August 2026. That is the deadline.

Why distribution is the actual problem right now

The app works well enough to test the retention thesis. What I do not have is a reliable way to reach the person who needs it.

The ICP I am building toward is a 25 to 40 year old who scrolls Instagram for an hour or more a day, saves reels in good faith, and almost never revisits them. They have a real job. They also have a real life outside it. They want to cook the recipe and actually take the trip. They just never remember the reel.

That person is not searching for "Instagram reel summarizer." They are not on Product Hunt. They exist in communities organized around the content they save: cooking, travel, fitness, home projects. Reaching them means showing up in those communities with something useful, not a pitch.

Three channels, 90 days

The plan I have locked is three channels, prioritized by cost and feedback speed.

1. Beta subreddit expansion. The TestFlight beta is live now. I am posting in r/alphaandbetausers, r/TestFlightBeta, and a few niche communities to grow the beta cohort. The goal here is not 300 users. It is 50 real testers who will tell me where it breaks.

2. Reddit value posts. Starting week three, I am posting in r/digitalminimalism, r/getdisciplined, and similar communities. Not links. Posts that are actually useful to the people in those threads. The app comes up only if it fits naturally.

3. Build-in-public on Indie Hackers and X, leading to a Product Hunt launch on day 60. This post is the start of that sequence. I will write one of these every two weeks: what changed, what the numbers look like, what broke, what I learned. The PH launch on day 60 is timed to hit when the free tier is stable and the first retention data is in.

What I am measuring

Three things matter in the next 30 days:

• Beta cohort size (target: 50 active testers by day 30)

• 14-day library return rate (is anyone reopening their summaries after creating them?)

• Category mix of summaries (are people summarizing instructional content, or something else entirely?)

If the library return rate is low, I will rethink before the PH launch. If the category mix is wrong, the ICP is wrong and the positioning needs to change before day 60.

What this series is

This is post one. I will write one every two weeks until the paywall ships. Each one will have real numbers, not projections. I will name what broke and what I got wrong.

If you are building a consumer iOS app as a side project and you want to trade notes, I am around. And if your saved Instagram folder looks like mine does, you can join the TestFlight beta at the link in my profile.

Stack: Flutter, Gemini 2.5 Flash, Whisper, FastAPI, Hetzner. Solo founder. Nights and weekends.