9. Assumptions and Open Inputs
This idea came from row C8 of the 30 Sept 2026 micro-SaaS idea catalog. No founder brief was supplied, so there's no stated team, hours, platform, price or traction. Here's what was assumed, and how the verdict changes if each assumption is wrong.
9.1 Assumptions made
| Input | Assumption used | If actually different… |
|---|---|---|
| Target platform | None stated. KDP chosen after scoring six dashboards (02) | If you have deep access to another seller community (e.g. you run a Merch or Meesho seller group), re-score. Access can outweigh a few points. Seller Central stays out regardless, because of the Agent Policy. |
| KDP has no native bulk price update | Assumed from KDP's help pages (per-title only). Not confirmed in a live account. | If it exists, the core product is gone. Fall back to promos plus cross-store pricing, and cut every odds figure by about half. |
| Agent Policy scope | Applies to Seller Central (BSA), not KDP, as of 30 Sept 2026 | If Amazon extends it to KDP with wording that covers user-driven extensions, the kill switch applies. |
| Price | Author $15, Pro $29, Press $69 a month; blended ~$20 after annual discounts | At a blended $12 (closer to 2019 Merch Wizard prices), every "accounts needed" figure rises by ~65%. The $10k odds fall to ~4% / ~8%. |
| Buyer pool | ~20,000–60,000 publishers with 20+ titles who pay for tools (loose estimate) | Under 10,000 caps the realistic ceiling near $3k MRR. |
| Hours per week | Two scenarios: ~15 hrs/week and full-time | Under ~8 hours a week, the 24-hour fix rule can't be kept. Don't start. |
| Skills | One developer who can build and maintain an MV3 extension | Hiring the build makes every KDP change a paid emergency. Multiply odds by ~0.65. |
| KDP experience | Unknown | Being a KDP publisher with several titles is the single biggest positive. It gives you a test account, credibility and first customers. |
| Stage and traction | Idea. Nothing built, no users. | Any paying users, even 10, outweigh most of this document. |
| Funding | None, and none needed | Doesn't change the product advice. |
| Churn | 4–6% monthly after month 6 (unverified; no extension churn benchmark found) | At 8%+, the ladder above $3k is out of reach. |
9.2 Inputs that would change the verdict most (please supply)
- Does KDP have any bulk price or rights update today? Check your own Bookshelf. This decides whether there's a product.
- Your hours per week available, and whether you can keep a 24-hour fix promise.
- Do you publish on KDP? How many titles, formats and marketplaces?
- Have you shipped a Chrome extension? MV3, content scripts, store review.
- Which author or seller communities can you reach today, and how many members do they have?
- Any sign of Amazon's position on third-party KDP tools: KDP support replies, forum posts, or account warnings you've seen.
9.3 Definitions used throughout
- Success: portfolio Tier A and Tier B definitions from ../../README.md, plus the MRR ladder in WHAT-TO-DO-AND-AVOID.md.
- Prolific publisher: 20+ titles on KDP, across any formats.
- Promoter: a publisher who changes prices for a promotion at least once a month.
- User-driven: every change starts from a click by the user, in their own logged-in tab, at human pace, with a preview and a log. The opposite is background automation, which this plan rules out.
- Breakage: any KDP page change that stops a paid feature working for any customer.