← All founder workflows

How to validate a Chrome extension idea in a single weekend

Validate a Chrome extension idea by testing distribution before you build, because extensions are cheap to write and almost impossible to get discovered. Search the Chrome Web Store for the problem, read the one-star reviews of the top three results, then post a single honest thread describing your version in the community that has the problem. Fifty clicks and ten install-intent replies in a weekend means distribution exists. Silence means you would have shipped into a store where nobody browses.

2 days $0 to run6 stepsUpdated 2026

The workflow

0/6 done

  1. Type the problem the way a frustrated user would, then sort by review count. You are looking for one of three outcomes: nothing exists (usually means no demand), five decent extensions exist (means demand, hard entry), or three exist with thousands of installs and angry reviews about one specific failure. The third is the only genuinely good news, and it takes twenty minutes to find out which one you are in.

  2. Extension reviews are unusually blunt: broken after the last Chrome update, stopped working on the new site layout, went subscription-only, started collecting data. Collect twenty complaints across the top three competitors and count the repeats. The most repeated complaint is your positioning sentence, and it is written in the user's own words — which is worth more than any brainstorm.

    Competitor research
    Input
    Chrome extensions for saving and organising LinkedIn profiles
    What comes back
    4 extensions with 10k–200k users. Recurring one-star themes: 61 reviews mention breakage after LinkedIn layout changes, 34 mention a surprise switch to a paid plan, 22 mention data-sharing concerns. Reliability and a transparent price, not features, is the gap.

    What this step looks like when it is done properly — the free Idea Validator covers the same ground as part of its research.

  3. Some ideas die on permissions rather than demand. An extension that needs to read every page you visit shows a scary install warning and faces slower store review, and users decline it in numbers that make the maths impossible. Write down the narrowest permission set that could work, and if the idea requires broad host access to be useful, factor a 30–50% install drop-off into every number below.

  4. One page: the complaint you are fixing in the headline, three screenshots or a fifteen-second GIF, and an "Add to Chrome" button that collects an email instead. This is the whole test — a button that measures intent rather than interest. Build it in two hours with any static host; the domain is the only cost.

    Landing Page RoastFull tool
    Input
    Landing page for a LinkedIn profile-saver extension — headline: "Never lose a profile to a layout update again."
    What comes back
    Headline names the actual complaint — keep it. Missing the one thing extension buyers scan for: what permissions you request, stated plainly near the button. Add "Reads only linkedin.com pages. No data leaves your browser." Expect click-to-intent around 20–30% on on-topic traffic without it, higher with it.

    Run it yourself — free, no signup:

  5. The subreddit, the Discord, the forum thread where people complain about the incumbent. One post: here is the problem, here is what I would build, would you use it? Not a launch — a question. Fifty clicks and ten replies saying "tell me when it's out" is a real weekend signal. Zero replies is the most useful outcome available, because it costs you two days instead of two months.

  6. You already know you can build it — extensions are a weekend of work. The decision is whether you can reach users repeatedly, because store search alone delivers almost nothing to a new listing. If the weekend produced one channel that sent traffic, build. If it produced only encouragement, you have a project rather than a business.

Questions founders ask about this

Can you make money from a Chrome extension?
Yes, though distribution rather than development is the constraint. Store search sends very little traffic to new listings, so extensions that earn tend to have an outside channel — a community, a content niche, or a companion product.
How do I know if a Chrome extension idea has demand?
Look for existing extensions with large install counts and repeated one-star complaints about a specific failure. Angry users of a working product are far better evidence than an empty category, which usually means nobody wanted it.
Do permissions affect whether people install an extension?
Significantly. Broad host access triggers a warning at install time and measurably reduces conversion, so design for the narrowest permission set and state it plainly on your landing page.
Should I build the extension first since it's only a weekend?
Building is the cheap half; getting it in front of users is the expensive half. Spend the weekend testing whether you have a channel — if you do, the build is still only a weekend away.
How many installs does a Chrome extension need to be viable?
It depends entirely on the model: a $5/month extension needs a few hundred paying users, while an ad-free free extension needs tens of thousands to matter. Decide the model before the build, because it changes which validation number counts.

Next, founders usually do this

The tools used above have their own pages — Landing Page Roast — and the SOP SOP: Write landing page copy that converts runs the same ground in more depth. Also worth reading: the Nine Lives Doctrine, and real verdicts from ideas kitty has run this workflow on.

kitty.build runs this entire workflow for you

Every step above — the research, the competitor read, the numbers, the honest verdict — is what nine specialist AI boards do automatically when you feed her an idea. She will tell you to kill it if it deserves killing. First idea is free.

Feed her an idea — free

No card · Failed tasks are free · Your repo, your domain, your revenue