GROWTH CASE 13 · ONE PERSON AT A TIME
How firsteyes AI Reportedly Reached 40 Paying Customers in Four Months
The firsteyes AI founder shared a manual problem-first DM. Paperflite spent two years answering questions on Quora and Reddit before continuing conversations on LinkedIn.
9 min read
Written after the drafts failed, not before.
Joey Zhao · Founder of Finfold
Updated ·
Public-handle and named interview cases · the 40 paying customers and Paperflite acquisition path are reported by participants or interviewers, without an independent revenue audit.
The public account Illustrious_Cake0018 says firsteyes AI crossed 40 paying customers four months after launch. The founder did not post a generic feedback request and wait. He found people already describing a conversion problem, sent a manual DM that referenced the exact issue, described the tool briefly without leading with its name, and asked whether they wanted to try it.
Paperflite took a slower route. A SaaS Club playbook based on an interview with cofounder Yega Kumarappan says the team spent about two years in Quora and Reddit, answered relevant questions, mentioned Paperflite when it fit, and followed up on LinkedIn. Neither case supplies a guaranteed conversion rate.
CASE FILES
Who did what, when, and what can be verified
Illustrious_Cake0018
u/Illustrious_Cake0018 · firsteyes AI
- Time and objective
- Four months after launch · Find an early group of paying users
- Reported result
- Self-reported more than 40 paying customers
- 01Found problem posts
- 02Restated the exact issue
- 03Briefly described the tool
- 04Followed up manually
Failure or limit · Commenters questioned site traffic and the figure is not independently audited
Open the original caseYega Kumarappan
Paperflite
- Time and objective
- Roughly two years after a 2018 launch · Build early pipeline from high-intent questions
- Reported result
- Case says a small pool of qualified leads produced early customers, while the first payer did not convert directly from a forum
- 01Answered forum questions
- 02Mentioned the product when relevant
- 03Followed up on LinkedIn
- 04Responded quickly to inbound chat
Failure or limit · Source is a secondary playbook based on a podcast and direct forum attribution cannot be isolated
Open the original casefirsteyes started with people already naming the problem
The founder called Reddit the strongest channel and named micro_saas, saasbuild, SaaS, and buildinpublic. Feedback and paid users reportedly came from contacting people who had already described website friction.
Find a person already seeking an answer before deciding whether the product belongs.
The opening referenced one exact problem
The public reply gives a clear order. Mention the post, restate a specific problem, describe the tool in one or two lines without leading with its name, and ask whether the person wants to try it. The founder says every message was manual.
A useful DM proves that the sender read the original post.
The comment thread preserved challenges
One commenter questioned the site's traffic and another said Reddit had completely failed for their product. The founder agreed that channel fit depends on the category. Those comments do not disprove 40 customers, but they prevent treating the claim as a normal outcome.
A case remains useful when the objections stay visible.
Paperflite treated forums as a long-term responsibility
The secondary playbook says the team spent two years answering sales-content and knowledge-management questions. The sequence was answer, mention Paperflite when relevant, and follow up on LinkedIn. The first paying customer did not arrive directly from a forum.
The forum answer gave the later conversation a legitimate beginning.
Both motions resisted bulk automation
firsteyes explicitly says DMs were not automated. Paperflite's approach required deciding whether a question matched and writing an answer that helped on its own. Copying at scale would remove both conditions and risk Reddit's rule against large unsolicited messaging.
Manual outreach is slow because relevance must be judged each time.
Run a seven-day test with ten questions
Find two relevant questions each day and contact only the strongest match. Reference one detail, omit the link, and ask permission to explain. Share the product and commercial relationship only after the person agrees. Cap the week at seven contacts.
A small sample reveals which sentence actually opens a conversation.
Review reply quality and stop signals
Track reads, substantive replies, trial consent, completed trials, and payment. Rewrite after two people call the message intrusive. Recheck targeting after seven non-responses. Stop immediately after a community warning.
Before payment, willingness to continue is already a useful signal.
SOURCES
What each link actually supports
- Public-handle firsthandAccessed 2026-08-19firsteyes AI founder's public retrospective
Supports the reported four months, 40 customers, DM wording, communities, and manual execution.
- Secondary analysisAccessed 2026-08-19Paperflite early forum acquisition playbook
Supports the two-year forum effort, three-step motion, and first-customer source.
- Official sourceAccessed 2026-08-19Reddit spam policy
Restricts large unsolicited messaging and repetitive promotion.
SMALL BET, REAL SIGNAL
Validate problem fit with seven manual messages
01 / FIND TEN PROBLEMS
Save only posts that describe a problem the product can actually address.
02 / CONTACT SEVEN
Reference one source detail and ask permission before explaining the product.
03 / RECORD OUTCOMES
Separate replies, trials, completed use, and payment.
CONTINUE THE WORKFLOW
NOW MAKE A DRAFT
Let Finfold handle the Reddit structure. Keep your own point of view.
A generator can get you off the blank page. It should never erase the person who lived the story.
Try the free generator