# Decision Memo: DIY Chrome extensions

Full report: https://ideanavigatorai.com/ideas/diy-chrome-extensions/
Recorded: Not recorded

## Decision
- Team verdict: Park
- Validation verdict: Rethink (47/100)
- Confidence: 52%
- Recommendation: Keep this parked until the team has evidence for the next validation step: Run a landing page offering 'Describe a Chrome extension, we build it' and route 30-50 real prompt submissions through a manual/AI-assisted build process. Measure prompt-to-install completion rate, how many users keep the extension after a week, and willingness to pay for publishing or private team distribution via a paid preorder or $9 paywall before scaling automation.

## Team rationale
No team rationale recorded yet.

## Reviewers
- No named reviewers recorded.

## Source anchors
- Buyer: Prosumers, power users, indie hackers, marketers, ops and growth teams, and internal-tooling builders who want custom browser automations but cannot or will not write a Manifest V3 extension by hand.
- Market: Browser productivity tooling and the no-code/AI app-builder space, specifically AI-assisted Chrome extension creation for non-developers.
- Problem: Building even a trivial Chrome extension requires understanding Manifest V3, service workers, content scripts, permissions, and the Chrome Web Store review pipeline. Non-developers who have a clear 'I wish my browser could do X' idea have no realistic path to ship it, and hiring a developer for a single-purpose tool is uneconomical.
- Thesis: DIY Chrome extensions should be tested as a narrow first-win workflow for Prosumers, power users, indie hackers, marketers, ops and growth teams, and internal-tooling builders who want custom browser automations but cannot or will not write a Manifest V3 extension by hand..
- Source: https://developer.chrome.com/docs/extensions/develop/migrate/what-is-mv3
- Source: https://www.debugbear.com/blog/counting-chrome-extensions
- Source: https://www.hostinger.com/blog/ai-app-builder-statistics
- Source: https://blog.tooljet.com/low-code-statistics-2026/
- Source: https://www.kromio.ai/

## Validation rubric
Rubric version: INAV-VALIDATION-2026-06-04

### Demand signal - 5.2/10 (24% weight)
Demand looks weak because the report has 4 source-backed signal(s), an editorial confidence of 52/100, and a defined buyer in Browser productivity tooling and the no-code/AI app-builder space, specifically AI-assisted Chrome extension creation for non-developers..

- The Chrome Web Store hosts 190,000+ browser extensions (some trackers report 250,000+ items including themes/apps as of 2026), with productivity extensions the single largest category, showing a large, active distribution surface and buyer appetite for browser tooling.
- Target buyer: Prosumers, power users, indie hackers, marketers, ops and growth teams, and internal-tooling builders who want custom browser automations but cannot or will not write a Manifest V3 extension by hand.

### Problem severity - 5.3/10 (22% weight)
Problem severity is thin when the buyer pain, customer value, and dream-outcome scores are combined.

- Building even a trivial Chrome extension requires understanding Manifest V3, service workers, content scripts, permissions, and the Chrome Web Store review pipeline. Non-developers who have a clear 'I wish my browser could do X' idea have no realistic path to ship it, and hiring a developer for a single-purpose tool is uneconomical.
- The Chrome Web Store hosts 190,000+ browser extensions (some trackers report 250,000+ items including themes/apps as of 2026), with productivity extensions the single largest category, showing a large, active distribution surface and buyer appetite for browser tooling.

### Willingness to pay - 5/10 (20% weight)
Willingness to pay is weak; the model has a monetization hypothesis, but it must still be proven through paid pilots or explicit pricing objections.

- Freemium SaaS: free tier for local/private extensions with a cap, paid monthly tiers ($12-49/mo) for unlimited builds, private team distribution, advanced permissions/API calls, and assisted Chrome Web Store publishing; optional team/enterprise plan for internal-tool management.
- Run a landing page offering 'Describe a Chrome extension, we build it' and route 30-50 real prompt submissions through a manual/AI-assisted build process. Measure prompt-to-install completion rate, how many users keep the extension after a week, and willingness to pay for publishing or private team distribution via a paid preorder or $9 paywall before scaling automation.

### Competitive saturation - 3.6/10 (18% weight)
Competitive room is reduced by 3 recorded alternative(s); the wedge must stay narrow and differentiated.

- Recorded alternative: Kromio — AI Chrome Extension Builder
- Competitive score rewards a narrow wedge, not absence of research.

### Feasibility - 4/10 (16% weight)
Feasibility is weak for a high build if the MVP is limited to the first measurable workflow.

- Run a landing page offering 'Describe a Chrome extension, we build it' and route 30-50 real prompt submissions through a manual/AI-assisted build process. Measure prompt-to-install completion rate, how many users keep the extension after a week, and willingness to pay for publishing or private team distribution via a paid preorder or $9 paywall before scaling automation.
- Manifest V3's ban on remotely hosted code and mandatory store review means you cannot ship arbitrary AI-generated code dynamically; every published extension must pass Google's review, creating latency and rejection risk that breaks the 'instant' promise.

## Market gap
Underserved segments:
- Prosumers, power users, indie hackers, marketers, ops and growth teams, and internal-tooling builders who want custom browser automations but cannot or will not write a Manifest V3 extension by hand. who still run the workflow in spreadsheets, generic docs, email, or chat threads.
- Small teams in Browser productivity tooling and the no-code/AI app-builder space, specifically AI-assisted Chrome extension creation for non-developers. that feel the pain weekly but are too narrow for broad incumbents.
- New adopters who need guided proof before committing to a larger platform.

Feature gaps:
- A narrow workflow that reaches value without configuration-heavy onboarding.
- A buyer-facing proof artifact that shows time saved, risk reduced, or communication improved.
- A handoff path from manual concierge service to repeatable software.

Differentiation levers:
- Use specificity as the wedge: one buyer, one workflow, one measurable result.
- Show proof earlier than broad competitors with before-and-after examples and small pilot data.
- Keep implementation lighter than incumbent suites or generic AI assistants.

## Roast and risks
Interesting hypothesis, but it needs sharper demand evidence before build time.

Blind spots:
- Manifest V3's ban on remotely hosted code and mandatory store review means you cannot ship arbitrary AI-generated code dynamically; every published extension must pass Google's review, creating latency and rejection risk that breaks the 'instant' promise.
- A broad AI assistant can flatten differentiation unless the wedge is painfully specific.
- The first release can become a generic dashboard if the job is not named tightly.

Hard questions:
- Who wakes up already trying to solve this?
- What do they stop paying for or stop doing when this works?
- What proof would make a skeptical buyer trust it in one screen?
- What is the smallest paid version of this idea?

## Kill criteria
- Fewer than five qualified buyers agree to discuss the workflow after targeted outreach.
- No buyer can name a current cost in time, money, risk, or reputation.
- The first demo does not produce a clear next step, paid pilot, or specific objection.

## Offer ladder
- **Lead magnet (Free)**: Diy Chrome Extensions checklist Goal: Capture qualified leads and learn the buyer's exact language. Value: Helps Prosumers, power users, indie hackers, marketers, ops and growth teams, and internal-tooling builders who want custom browser automations but cannot or will not write a Manifest V3 extension by hand. audit the painful workflow before buying software.
- **Frontend offer ($19-$99)**: Concierge review or paid template Goal: Validate urgency, workflow fit, and willingness to pay. Value: Delivers the first useful output manually before automation is trusted.
- **Core offer ($49-$499/month)**: DIY Chrome extensions focused SaaS Goal: Create the recurring revenue product after the narrow wedge survives tests. Value: Turns the recurring manual workflow into a repeatable product loop.
- **Continuity ($99-$1,000/year add-on)**: Monitoring, benchmarks, and monthly reporting Goal: Increase retention and make the product part of a routine. Value: Keeps the buyer engaged with ongoing proof, saved time, or reduced risk.
- **Backend offer (Custom)**: Done-with-you setup, agency, or team rollout Goal: Capture higher-value accounts once the productized wedge is proven. Value: Adds implementation help, integrations, and workflow migration.