The product named after the search query
Open the real page ↗pdf.ai · alive as of 2026-08-31
Upload a PDF; get summaries, search and answers. The lesson is less the product than the name and domain capturing the search intent itself. The order matters: what people type was settled before what was built. ⚠️ The monthly figure circulating for it comes from a secondary write-up sourced from the founder, so we do not print it (grade B).
In plain words
Drop in a long PDF and it summarises, searches and answers questions about it. The name is the phrase people already type, so they arrive on their own.
The whole thing at a glance
To whom
Professionals
What
AI SaaS
Found how
A domain name that is the se…
Paid how
Subscription SaaS
Flow: To whom, then What, then Found how, then Paid how
- Founder
- Damon Chen
- Country
- US
- Team
- —
- Startup cost
- —
- To first revenue
- —
- Automation
- high
- Reported revenue
- Revenue not disclosed
What is sold
Subscription SaaS
Pricing is published on the official site (liveness confirmed 2026-08-31). ⚠️ We do not copy the amounts across.
Who buys
Professionals, researchers and students who read long documents often
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
A developer who had shipped products before — not a non-technical start. What proved decisive, though, was less engineering skill than the naming and distribution design.
If this is large, the AI is not the reason
What the AI did
Reading the document and answering from it is the product. Answers are grounded in located passages, and what the customer buys is reading time they no longer spend.
the part a tool replaced
What the person did
Securing the place where people search, before building the thing they search for. Name, domain, search presence, browser extension — the product was placed where people already put the problem into words.
stories that omit this do not replicate
How customers were found
A domain name that is the search intent
Organic search
Distribution through a Chrome extension
Paying customers
Pricing is published on the official sit…
Flow: A domain name that is the search intent, then Organic search, then Distribution through a Chrome extension, 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 cited analysis is live (HTTP 200). Not confirmed — revenue. The monthly range comes from a secondary write-up, and such write-ups generally source their numbers from founder interviews and public statements. No third party connected to a payment system produced this figure. ⚠️ "It appeared in a publication" and "it was independently verified" are different things. Blur that distinction and the whole grading system stops meaning anything (CLAUDE.md §2.1).
- Official site — liveness confirmed (HTTP 200) (official_site · checked 2026-08-31)
- Starter Story breakdown — origin of the revenue figure. Secondary write-up based on founder statements; supporting evidence only (press · checked 2026-08-31)
What made it work
Decide what people type before you decide what you build, and traffic arrives without an ad budget. A product name is a distribution asset, not a matter of taste. And holding a second distribution channel reduces search dependence — a browser extension meets people outside the search box.
Risks
- General assistants are absorbing file upload and document questions as standard features. A generic PDF tool sits in the first row to be squeezed.
- Accuracy is the trust — answers without located evidence do not survive professional use.
- The revenue figure is a second-hand compilation.
Does this work in Korea?
Capturing search intent through a domain name works less well in Korea, where portals carry more of the search volume and domain names influence results comparatively little. A variant does work there — narrow the document type instead of the domain. Contracts, academic papers, regulatory filings, court decisions: pick one genuinely hard-to-read document type and build only for it. That beats a general PDF tool in that market.
Solo-feasible: yes · Automation: high
7-day action plan
Step 1. Pick one document type in your field that people put off reading because it is hard
Step 2. Collect ten phrases people actually search when facing it
Step 3. Run three such documents through an AI and note precisely where the answers fail
30-day action plan
Step 1. Fix one summary format for that single document type and process twenty of them
Step 2. Turn the failure points into an explicit list of what a human must still check
Step 3. Publish that list as the product's stated limits, then open paid conversion
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.