6. Fundability
6.1 Would I invest at pre-seed or seed?
Pre-seed: No. Not as described and not as narrowed. A browser extension that lives inside one Amazon dashboard has three problems no team can fix:
- a ceiling set by the number of prolific KDP publishers (tens of thousands, estimated);
- a landlord who can end the product with a page update, a native feature or a policy line;
- no moat beyond speed and trust. The code is easy to clone.
Seed: No. There's no path from here to venture scale that an investor could underwrite. The honest outcome is a profitable, sellable asset. That's a good outcome for a founder and a bad one for a fund.
6.2 What a skeptical investor says in the first five minutes
- "Which dashboard? You listed seven." If the answer isn't one platform and one job, the meeting ends.
- "What stops Amazon shipping bulk pricing next quarter?" Nothing. The only answer is cross-store pricing, which Amazon won't build.
- "Isn't this automation against Amazon's terms?" Seller Central's Agent Policy (March 2026) says browser automation is out. KDP's terms don't say it, but Amazon can terminate for "concerns". You need a crisp, user-driven design answer.
- "How many publishers have 20+ titles, and how many pay for tools?" Unknown. Publisher Champ's "25,000 authors" is the nearest anchor.
- "What's your churn once the July 2026 repricing is done?" Unknown until month 3.
- "How do you know when you're broken?" If the answer is "customers email me", that's a no.
- "Why won't a free clone in a Facebook group take your market?" Trust, support speed and brand in a small community. It's real, but it isn't a moat.
- "Merch Wizard sold for how much?" The price wasn't published. Only "full asking price within 5 hours".
If you can't answer 1, 3 and 6 crisply, the rest doesn't matter.
6.3 Three proof points that would change the answer (to "fund a small acquisition", not "venture")
| # | Proof point | Threshold | Why it matters |
|---|---|---|---|
| 1 | Retention past the event | ≥70% of payers still paying at month 3, with ≥40% on annual | Proves it's a monthly workflow, not a one-time fix. |
| 2 | A recurring job in use | ≥40% of Pro and Press accounts schedule a promo every month | The promo scheduler is what separates a subscription from a utility. |
| 3 | Breakage record | Every breakage fixed within 24 hours for 12 months, with public status updates | For a buyer of the business, this is the risk they're pricing. |
A strong fourth: ≥30% of payers publish wide and ask for Kobo, Apple and Google Play. That opens the one feature Amazon won't copy.
6.4 Bootstrap or raise?
Bootstrap. Don't raise.
- The build is small. A focused MV3 extension with a licence check is weeks of work for one developer. Hosting is under ~$100 a month.
- Revenue arrives early. Done-for-you repricing pays in month 1. Subscriptions start when the extension ships.
- Outside money makes it worse. Pressure to grow pushes you towards more platforms (Etsy, Merch, Seller Central), which is exactly where the terms and competition problems are.
- The exit is a sale, not a round. Small profitable software businesses change hands on Acquire.com at a median of 3.9× profit (2024 and 2025, from the catalog). Merch Wizard sold in 5 hours. Build it to be sellable: clean code, documented selectors, a support playbook, a stable customer base, and no personal dependencies.
Honest bottom line: the version described can't be built, because it's seven products. The narrowed version doesn't need money, and money wouldn't make it bigger. Build it cheaply, run it well, and treat a sale as a valid finish line.