micro-saas-scoper

What problem does it solve?

Decides whether a validated wedge should become software, defines the narrow product wedge, and separates what stays manual versus automated. Use when a service, workflow, or audience-driven opportunity may be ready for micro-SaaS scoping or when a user is tempted to build software too early.

Core Features & Use Cases

• Decide readiness: output one of build_now, stay_manual_for_now, or conditional_build with justification and evidence.
• Define the product wedge: select one narrow job, one primary user, one core workflow, and one productization trigger.
• Separate manual from automated work: specify what remains manual, what gets automated first, and what not to build yet.
• Produce the scope: return a readable product scope and a JSON block using assets/micro-saas-scope-template.json.

Quick Start

Run the four-phase workflow to decide readiness, define the product wedge, separate manual from automated work, and generate a scoped MVP boundary.