0 to 10M users: The Quicktools playbook

When I joined Picsart in October 2021, I had one mandate: figure out how to acquire relevant organic traffic that could convert into product users. The main domain lacked SEO presence for utility searches like "background remover" or "resize image."

I started with zero roadmap, zero team, and a lot of questions.

Eighteen months later, we had 10 million monthly active users, $1M ARR, and 50+ tools—built by two engineers. Here's the entire playbook.

The Challenge

Picsart had 150M+ monthly active users on mobile, but the web story was thin. The main site had strong brand searches, but for high-intent utility keywords—the queries where someone actually needs a tool right now—we were invisible.

Think about it: millions of people search "remove background from image" every month. They're not browsing. They have a photo and they need the background gone in the next 30 seconds. If you don't show up for that search, you don't exist for that user.

We had:

• No SEO presence for high-intent utility keywords
• Long development cycles (8-12 weeks per feature in the main product)
• Limited engineering resources—I eventually got 2 engineers, not 20
• Established competitors (Canva, Adobe, Remove.bg) already ranking for everything

The traditional approach would be: write a PRD, get design approval, build for 3 months, launch, measure, iterate. By the time you've shipped one tool, a competitor has shipped ten.

We needed a different playbook.

The Insight

The breakthrough was understanding that each tool was essentially the same product wearing a different costume. A background remover and an image resizer both follow the same flow: upload → process → download. The AI model in the middle changes, but the wrapper is identical.

If we could standardize the wrapper, we could ship tools as fast as we could connect new processing endpoints. That's exactly what we did.

The Technical Framework

This is the part most case studies skip. The framework was the entire strategy.

The Reusable Shell

We built one React component architecture that every tool shared:

• Upload zone: Drag-and-drop or click to upload. Same component everywhere.
• Processing view: Progress indicator while the API works. Same component.
• Result view: Before/after comparison, download button, share options. Same component.
• SEO layer: Dynamic meta tags, structured data, breadcrumbs. Templated per tool.

The only thing that changed between tools was the API endpoint for processing and the copy on the page. That meant shipping a new tool was really just: pick a keyword, connect an API, write the landing page copy.

The Component Library

We built about 15 core components that covered every tool flow:

• Image upload with client-side validation
• Processing queue with status polling
• Before/after slider
• Download with format options
• Related tools sidebar
• FAQ section (auto-generated from keyword research)
• Trust signals (usage counter, ratings)

An engineer could assemble a new tool from these components in 2-3 hours. The other 5-6 hours went to API integration, testing, and copy. One full tool per day per engineer. Two engineers meant two tools per day at peak velocity, though we averaged about two per week to maintain quality.

Deployment Pipeline

Every tool followed the same CI/CD path:

1. Feature branch with the tool slug as the branch name
2. Automated tests (component rendering, API integration, SEO checks)
3. Preview deployment for QA
4. Merge to main, auto-deploy to production
5. Automated sitemap update and Google indexing ping

From "merge PR" to "live and indexed" was under 10 minutes.

The SEO Strategy

Building tools is only half the equation. You need people to find them. Our SEO approach was methodical.

Keyword Selection

I used a simple scoring model:

• Search volume: Minimum 10K monthly searches globally
• Intent: Must be transactional ("remove background" not "what is image editing")
• Feasibility: Can we build a tool that actually solves this in under a week?
• Competition: Prefer keywords where existing results are weak (slow pages, bad UX, gated tools)

The sweet spot was high-volume keywords where the existing tools were either slow, required sign-up, or didn't work well on mobile. That described most of the market in 2021.

The Tools That Worked Best

Not all tools performed equally. The top performers shared specific traits:

Tier 1 — Breakout hits (1M+ monthly users each):

• Background Remover: The flagship. "Remove background" has massive search volume and our AI quality was genuinely best-in-class.
• Image Resizer: Dead simple tool, enormous search volume. People need this constantly for social media.
• Photo Enhancer: AI upscaling hit a nerve. People had old photos they wanted to improve.

Tier 2 — Strong performers (100K-1M monthly users):

• PNG to JPG converter (and reverse)
• Image compressor
• Collage maker
• Color picker from image

Tier 3 — Long tail (10K-100K monthly users):

• Passport photo maker
• Meme generator
• Watermark remover
• Crop image to circle

The pattern: the simpler and more specific the use case, the better the conversion. "Remove background" converts better than "edit photo" because the user knows exactly what they want.

On-Page SEO

Every tool page was optimized with the same template:

• Title: "[Action] [Object] Online Free — [Brand]" (e.g., "Remove Background from Image Online Free — Picsart")
• H1: Matches the primary keyword exactly
• Above-the-fold tool: No scrolling required to start using it
• FAQ section: 5-8 questions targeting related long-tail keywords
• Related tools: Internal links to similar tools (this became a full internal linking system later)
• Structured data: HowTo schema, FAQPage schema, SoftwareApplication schema

I later built a programmatic SEO engine to handle this at scale, but in the early days it was semi-manual. Template-driven, but I wrote the copy for each page individually.

The Growth Curve

The timeline tells the story:

Months 1-3 (Oct 2021 - Jan 2022): Foundation. Built the framework, shipped the first 10 tools. Traffic was negligible—Google takes time to trust a new subdomain. We hit about 50K monthly users by January.

Months 4-6 (Feb - Apr 2022): Traction. Background Remover started ranking page 1. Traffic jumped to 500K, then 1M by April. This was the inflection point. Google saw that users were engaging with the tools (low bounce rate, high time-on-page) and started trusting the domain.

Months 7-12 (May - Oct 2022): Acceleration. We were shipping 2 tools per week consistently. Each new tool piggybacked on the domain authority we'd built. New pages ranked faster. Hit 5M monthly users by October.

Months 13-18 (Nov 2022 - Apr 2023): Scale. Crossed 10M monthly users. The growth became self-reinforcing: more tools meant more internal links, more domain authority, faster ranking for new tools. We also started seeing direct traffic—people coming back without searching.

The compounding effect was the whole game. Tool #1 took 3 months to rank. Tool #50 ranked in 2 weeks.

Conversion and Monetization

Traffic alone doesn't matter. Here's how we turned visitors into revenue.

The Conversion Funnel

1. Tool usage (100% of visitors): Free, no sign-up, full functionality
2. Quality hook (50% completion rate): User sees the result and is impressed enough to download
3. Upsell prompt (shown after download): "Want HD quality? Try Picsart Pro"
4. Activation (3% upsell rate): User signs up for the main product

The 3% upsell rate sounds small, but at 10M monthly users, that's 300,000 new Picsart signups per month from organic traffic alone. At the time, this was one of the most efficient acquisition channels in the company.

Revenue Streams

• Subscription upsells: Users who converted to Picsart Pro
• Ad revenue: Tasteful ad placements on tool pages (not before, not during—only after the tool delivered value)
• Brand building: Hard to quantify, but "Picsart" showing up for every image editing search built massive brand awareness

Combined, this hit $1M ARR within 18 months. Not a unicorn number, but remarkable for a team of 2 engineers and 1 PM with zero marketing budget.

What I'd Do Differently

If I were starting Quicktools again tomorrow:

Invest in automated testing earlier. We moved fast, but we shipped some bugs that hurt trust. A broken tool page that shows an error instead of processing your image—that user is never coming back. I'd build the test suite in month 1, not month 4.

Build the landing page generator from day one. We eventually systematized page creation, but the first 20 tools had hand-crafted landing pages. The time spent on manual page creation could have gone to shipping more tools.

Start localization sooner. We eventually expanded to 40+ languages, which was a massive scaling challenge. But the international search volume was always there—we just left it on the table for the first 6 months.

Track activation quality, not just volume. We optimized for signups but didn't differentiate between users who signed up and churned immediately vs. users who became long-term Picsart users. That distinction matters for LTV calculations.

Key Learnings

1. Small teams with sharp systems beat large teams with process overhead. We did more with 2 engineers than many teams do with 10. The framework was the force multiplier.

2. Ship velocity matters more than perfection in early stages. 50 good tools > 5 perfect ones. You learn more from 50 launches than from 5. And Google rewards freshness and breadth.

3. Free tools that actually solve problems build trust faster than gated content. Every competitor required sign-up before you could use their tool. We didn't. That single decision probably accounted for half our conversion advantage.

4. Target intent, not vanity metrics. A user searching "remove background" is infinitely more valuable than a random social media impression. They have a job to do. Help them do it.

5. Compounding is the real strategy. Each tool makes every other tool more discoverable. Each page adds domain authority. Each user adds social proof. The first tool is the hardest. The fiftieth tool basically ranks itself.

6. Standardization is a superpower. The boring work of building a reusable framework paid for itself 50 times over. Every hour spent on the component library saved 10 hours across the subsequent tools.

The Playbook, Summarized

For anyone trying to replicate this approach:

1. Find a category with high-volume, high-intent keywords
2. Build a reusable technical framework that lets you ship fast
3. Launch 10 tools quickly to establish domain authority
4. Make the tools genuinely useful—no gates, no tricks
5. Let compounding do the heavy lifting after month 6
6. Automate the SEO work so you can focus on building

The tools don't have to be revolutionary. They have to be fast, free, and exactly what the user searched for.

---

This is part of my series on building products at scale. Read about why small teams win, how I automated SEO, or check out what I'm building now at ScreenshotEdits and PeerWealthy.