Day 30 — I ran 8 customer interviews. The problem is real. The willingness to pay is not (yet).

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.