Neel Seth did not start ReplyDaddy from a generic AI-agent idea. The MRR Story case and his own site both describe the same operating lens: he had left the corporate product track, had seen enterprise revenue up close at Dukaan, and cared less about polished features than products that could produce measurable revenue. When his own earlier projects needed customers, ads were expensive and Reddit conversations were useful but time-consuming. The wedge became a tool for the distribution job he already felt.

ReplyDaddy is deliberately framed as a co-pilot, not a posting bot. The live homepage says it finds relevant Reddit opportunities, analyzes the user's brand and persona, drafts authentic replies, and leaves the final post under manual human control. It also says there is no Reddit account connection and no automatic posting. That boundary matters: the product's promise is faster, rules-aware participation in relevant conversations, not spam at scale.

The early build was fast because Neel used AI as leverage. What started as a "48-hour MVP challenge" turned into a 96-hour build with AI help, Python/Flask, Supabase, and Dodo Payments, per Neel's own LinkedIn post. NeelSeth.com separately describes ReplyDaddy as solo-built with AI assistance and says it produced $6K revenue in its first 70 days. Neel's LinkedIn post states paying customers arrived within about 12 days of finishing the 96-hour build, so the structured timeline uses that founder-reported first-customer date instead of the 70-day cumulative-revenue figure.

Distribution came from the same places the product served. MRR Story says Neel got early customers through Reddit and Twitter/X, used ReplyDaddy itself to find conversations about SaaS user acquisition and Reddit marketing, and later combined founder-led public building with a RocketHub lifetime deal for early users and cash flow. The RocketHub deal page also verifies the positioning: Reddit opportunity monitoring, reply drafting, subreddit-rule checks, and manual review before posting.

The current recurring-revenue claim stays narrow. MRR Story reports ReplyDaddy at about $1,500 MRR, while Neel's own site reports $20K+ total ReplyDaddy revenue from September to December 2025 and describes the product as growing. The bigger portfolio number, including NoobBookLM, is not counted here. The useful lesson is smaller and cleaner: Neel found a painful acquisition workflow, built the minimum co-pilot around it, charged early, and kept the automation boundary explicit enough that the tool helps founders participate instead of impersonating them.