Twelve hours to build — and fifteen failures before it
Open the real page ↗audiopen.ai · alive as of 2026-08-31
It turns what you said into something worth reading. The takeaway is not "ship fast"; it is the opposite — the product that worked took twelve hours, and the founder says fifteen to twenty attempts failed before it. A textbook one-person product, kept deliberately small. ⚠️ Revenue is an interview statement, so we do not print it (grade B).
In plain words
Speak, and it returns clean readable text. It does very little else. The founder failed repeatedly before this one worked.
The whole thing at a glance
To whom
People capturing thoughts on…
What
Micro-SaaS
Found how
X — building in public
Paid how
Subscription SaaS with a fre…
Flow: To whom, then What, then Found how, then Paid how
- Founder
- Louis Pereira
- Country
- IN
- Team
- —
- Startup cost
- —
- To first revenue
- —
- Automation
- high
- Reported revenue
- Revenue not disclosed
What is sold
Subscription SaaS with a free allowance before payment
Pricing is published on the official site (liveness confirmed 2026-08-31). ⚠️ We do not copy the amounts across.
Who buys
People capturing thoughts on the move; people for whom writing is friction
What arrives is not what you keep
- What the customer paidThe number on the invoice
- AI toolsA share of the monthly subscription
- Platform feeDiffers by platform
- TaxDiffers by country and business form
- What is leftAt or below zero, it is not a price
This case does not publish its own tool costs, fees or tax. So we show the order and the items only — put your own numbers into the calculator.
AI's part and the person's part
Already had
Someone who had built products repeatedly. ⚠️ And most of those attempts failed. Quote only "built in twelve hours and it worked" and the failures disappear — at which point the case stops being evidence and becomes an advertisement.
If this is large, the AI is not the reason
What the AI did
Speech becomes text, then the text is rewritten to read well. Transcription alone is commodity; the sellable step is turning "what was said" into "worth reading."
the part a tool replaced
What the person did
Deciding not to add features. The problem of one person drowning in building, selling and support was solved here by making the scope extremely narrow. Less to do is what makes it operable alone.
stories that omit this do not replicate
How customers were found
X — building in public
Word of mouth
Conversion after a free allowance
Paying customers
Pricing is published on the official sit…
Flow: X — building in public, then Word of mouth, then Conversion after a free allowance, then Paying customers
How we verified this
Public dashboard or platform figure. May be self-reported
Confirmed — the service is live (official site HTTP 200, 2026-08-31), the founder is named, and the interview is live (HTTP 200). Not confirmed — revenue. The monthly figure and the "solo, no employees" description are founder statements in an interview, which CLAUDE.md §2.1 treats as supporting evidence. ✅ The number is not the valuable part of this case anyway. "MVP in twelve hours, after fifteen to twenty failures" is far more useful, and it is not the kind of claim that needs financial verification.
- Official site — liveness confirmed (HTTP 200) (official_site · checked 2026-08-31)
- Founder interview — origin of both the revenue and the failure-count statements. Supporting evidence (founder_interview · checked 2026-08-31)
What made it work
"Built it fast" is a result, not a cause. Twelve hours was possible because earlier failures had already narrowed what to build. The answer to solo overload is subtraction, not automation. Fewer features means fewer support requests, fewer incidents, less to explain.
Risks
- Operating systems and note apps are shipping this as a default feature. Once it is built in, the reason for a separate subscription disappears.
- Raising the price is hard — a low-priced consumer subscription is sensitive to churn.
- Both the revenue and the "no employees" claim are founder statements.
Does this work in Korea?
This transfers easily. It needs one capability, so start-up cost is low, and Korean transcription quality is practical today. The stronger local variant is narrowing who uses it — sales call notes, clinical notes, site inspection reports. Jobs where you speak it and then must submit it in writing pay better than general voice memos do.
Solo-feasible: yes · Automation: high
7-day action plan
Step 1. Count for one week how often you speak something you then have to write up
Step 2. Name three other jobs that do the same thing
Step 3. Ask someone in one of them how they capture those records today
30-day action plan
Step 1. Pick one job and shape the output to that job's submission format
Step 2. Process twenty real records in that format and note where manual work remains
Step 3. Do not add features; ask whether that one format alone is worth paying for
Run the numbers
We do not print a single projected figure here. Put your own numbers in instead.
Get the next verification result
We check the AI income stories people are talking about, grade the evidence, and send you what we found — including what we could not confirm.
Words you may not know
- Verification grade
- How far we checked this case. A means the revenue was confirmed by someone other than the founder; B means the business exists but the revenue is only the founder's word.
- Revenue
- Everything that came in. Tools, fees and tax still have to come out before it is what you keep. The two are not the same.
- MRR
- Money that arrives every month, as opposed to a one-time payment.
- Self-reported
- A number the person stated about themselves. Nobody else confirmed it, which is why we do not print those numbers.
- Replicability
- How likely someone else is to get a similar result. The more the founder already knew the field, the harder it is to copy.