Adrian's first customer came entirely by accident: he scraped a company's website and posted about it on Twitter, and that company's CTO commented on the post and became a paying customer. No deliberate outbound or launch campaign — just being visible on Twitter doing the work publicly. Beyond that accidental first customer, Adrian used a proactive Twitter engagement tactic: whenever someone posted a launch video related to scraping or social media analytics, he would comment offering 10,000 free credits to try the API. This kept his customer acquisition cost near zero in the early days and leveraged his existing Twitter presence and content history in the scraping/social media niche to build credibility and warm leads.
Scrape Creators
Pay-as-you-go API that scrapes public social media data and ad libraries
7 moves, in order
- Idea Validation (Pre build)Acquire com marketplace
A Twitter follower DM'd Adrian a listing on Acquire.com (MicroAcquire) for a scraping API doing $30K MRR with fewer than 100 customers acquired entirely via SEO. Instead of buying it, Adrian used the listing to validate the market and decided to rebuild it himself.
Confirmed a proven revenue model before writing a line of product code - Pre launch BuildSelf built
Deployed existing scrapers (built over 3 prior years) onto a Node.js server on Render.com. Created API documentation in a Notion doc and built a basic website. Total build time was a few weeks due to pre-existing scraper codebase.
Shipped a working MVP in weeks, not months - First CustomerTwitter — organic
Posted on Twitter about scraping a specific company's website as a demo/showcase. The CTO of that company saw the post, commented, and became Adrian's first paying customer — entirely unplanned.
First paying customer acquired at $0 costUsers 1 users - Early TractionTwitter comments
Monitored Twitter for any launch posts or videos related to scraping or social media analytics. Commented on those posts offering 10,000 free credits to try the API, converting interested developers into trial users.
Consistent low-cost customer acquisition pipeline; exact numbers not stated - ScalingSEO — organic
Replicated the SEO-driven customer acquisition strategy of the original app he had studied on Acquire.com. The original app had grown to $30K MRR with fewer than 100 customers purely through SEO, validating the channel for this niche.
Primary driver of growth to $20K MRR; exact timeline not statedMRR $20k Users 600 users - Ongoing / RetentionDirect founder support
Made himself personally reachable to customers — shared his email and communicated proactively about API outages or reliability issues. Positioned this as a differentiator vs. competitors where developers are anonymous and uncontactable.
Higher retention and trust; cited as a key reason customers stayMRR $20k - Ongoing / OperationsOperational reliability
Hired a developer in the Philippines (~$500/month) to monitor the API for outages at night, ensuring reliability around the clock. Reliability is explicitly cited as the product's top competitive advantage over other scraping APIs.
Maintained 80% profit margin while improving uptime and customer satisfactionMRR $20k
Adrian had 3 years of hands-on experience building scrapers and scraping APIs before starting this product, so the technical build was largely already done. He also had an existing Twitter audience in the social media/scraping niche, which gave him an organic launch channel and warm inbound interest from day one.
seo_organic
Adrian explicitly mentioned bouncing between multiple projects and ideas before this — he built a course and other products without success. Lack of focus and consistency is what he identifies as his prior failure mode. He does not call out any specific acquisition channel as having failed for Scrape Creators specifically.