Chrome extensions are a specific software category with their own validation rules. The build cost is low (often a weekend) but the failure modes are sharp: extensions die in the Chrome Web Store rankings, scare users away with broad permissions, or cannot find a monetization path.
This is a playbook for testing a Chrome extension idea against the four dimensions that matter most.
Dimension 1: Web Store discoverability has to be reachable
The Chrome Web Store is a ranked system. Top extensions in a category get most of the installs. New extensions either rank for narrow keywords or get nowhere.
The test: identify the specific keywords your extension would target in the Web Store. Search those keywords yourself. Are the top three results owned by well-established extensions with large install bases? If yes, the rank is unreachable. If the top three include outdated, abandoned, or under-optimized extensions, the rank is reachable.
Narrow is better than broad. "PDF tools" is unreachable. "Highlight and save PDF pages to Notion" is reachable.
Dimension 2: The permission model has to be defensible
Chrome extension permissions are visible at install. Extensions that request broad permissions ("read and change all your data on all websites you visit") scare users away even when the use case justifies them.
The test: write down the exact permission scope you need. Then ask: does the install screen for that permission scope feel acceptable to a non-technical user?
If the answer requires broad permissions, you need to plan the UX around explaining why before the install. If the permissions can be scoped narrowly (specific domains, specific user-triggered actions), the install conversion will be materially better.
Dimension 3: The upgrade path has to exist
Most Chrome extensions are free. The successful ones that monetize have a clear upgrade path: free tier for casual users, paid tier for power features or higher limits.
The test: name the free tier feature set and the paid tier feature set. The paid tier features need to be things power users actively need, not things any casual user would expect to be free. Common paid features:
- **Higher limits.** Free tier has 10 actions a day; paid has unlimited. - **Cloud sync.** Free is local; paid syncs across devices. - **Premium integrations.** Free supports basic; paid supports tools like Notion, Linear, Airtable. - **Removal of branding.** Free shows branding; paid removes it.
"Pay to remove the ad" is a fragile model that mostly does not work. "Pay for cloud sync across devices" is a reliable model.
Dimension 4: The category has to support paid users at scale
Even with a working upgrade path, the category has to have enough installs that 2% to 5% paying converts to meaningful revenue.
The math: if your extension targets 100,000 lifetime installs (achievable for a well-positioned extension in a reachable niche) and 3% convert to paid at $4.99 a month, monthly recurring revenue at peak is around $15,000.
If your category cannot realistically hit 100,000 installs in two to three years, the unit economics will not clear meaningful revenue. The fix is either a higher price point (enterprise extension at $20 a month or more) or a broader category.
A worked example: a Chrome extension that lets vibe coders save and reuse prompts across AI tools
The idea: a Chrome extension that captures and organizes prompts a user runs in ChatGPT, Claude, Cursor web, and Lovable, with reuse and search across tools.
- **Discoverability:** Web Store keywords like "save AI prompts", "prompt manager", "ChatGPT prompt library". Top three for each: a mix of established prompt managers with 100K+ installs and abandoned-looking older extensions. Niche rank reachable for "prompt manager for Cursor" and similar long-tail queries. - **Permissions:** read data on chat.openai.com, claude.ai, cursor.com, lovable.dev. Acceptable to a vibe-coder audience; would be scary to a general consumer audience. - **Upgrade path:** free tier supports 50 saved prompts and basic search. Paid tier ($5 a month) supports unlimited prompts, cloud sync across devices, and integrations with Notion and Linear for prompt libraries. - **Category scale:** vibe-coder audience is large enough (r/vibecoding 150K members, Lovable 8M users) to plausibly reach 50K+ extension installs in 12 months. Conversion at 3% to paid = ~1,500 paying users = ~$7,500 MRR.
All four dimensions clear. The extension is worth building.
How Verdikt fits this playbook
The free Verdikt tests the same four dimensions for Chrome extension ideas and returns a Verdikt Score plus the top three named risks. The Single Report ships the full memo with Web Store competitive analysis, permission-model analysis, and category sizing grounded in primary data.
The playbook above is the manual version.
A research letter for AI builders.
One letter per month. What we're shipping, what we're learning, what's actually working in the field.