This is a static public preview for the Price-Hike Wedge Scanner Workbook.

It is not a checkout page, payment link, waitlist, customer intake form, proof that anyone will buy, proof that anyone has paid, revenue record, or market-size report.

Who This Is For

• Indie developers comparing product opportunity signals.
• Micro-SaaS builders trying to avoid cloning full incumbents.
• AI-tool builders who need a stricter way to scope small experiments.
• Small operator-founders who want to separate public frustration from actual evidence.

The Problem

Public price changes can create a lot of visible frustration. That does not automatically mean there is a proven market, a known buyer, or a product worth building.

The useful question is narrower:

What repeated workflow pain might exist behind this public frustration, and what tiny scope could test it without cloning the incumbent?

Workbook Shape

The workbook is designed as a scoping aid:

Section	Purpose
Price-hike signal log	Capture the visible public signal without over-reading it.
Complaint-to-gap map	Separate emotion, workflow pain, switching friction, and unsupported assumptions.
Migration friction checklist	Identify what would make switching annoying or costly.
Tiny MVP scope cutter	Reduce a broad clone idea into a small testable wedge.
Do-not-clone boundary	Keep the idea away from copying brand, UI, feature set, or positioning.
Public evidence rubric	Label public signals as weak, medium, or strong context, not validation.

Synthetic Example

Raw public signal:

A generic subscription tool raises its starter plan price. Public comments complain that the new plan bundles advanced features while small teams only need one narrow workflow.

Possible worksheet output:

Possible wedge:
A lightweight checklist/export helper for the narrow workflow only.

Tiny MVP:
One manual worksheet plus one import/export template.

Boundary:
Do not copy the incumbent product, brand, UI, pricing page, or feature set.

Evidence status:
Public frustration signal only. Not proof that anyone will buy.

What This Page Is Not

This page is not:

• a SaaS idea recommendation
• a market-size report
• proof that buyers want this
• a purchase record
• a revenue record
• a checkout page
• a payment link
• a clone recommendation
• legal or investment advice
• a claim that public complaints equal buyer intent

Use Boundary

Public signals can help decide what to inspect next. They should not be used as proof that people will pay.

The safest use of this workbook is to reduce noisy public frustration into a smaller question:

Is there a concrete payer, with a concrete workflow pain, who would pay for a concrete small fix?

That question still needs separate testing.