Micro-SaaS Profitability Navigator

It's Wednesday. You shipped the feature three weeks ago. The one that took nine days and solved the problem cleanly — the one you'd have paid for yourself eighteen months ago. You've posted it twice. You have six trial signups, one of whom emailed a feature request, none of whom converted. You don't know if the price is wrong, the audience is wrong, or the message is missing the target entirely. You don't know which variable to change first. The damage is not a failed launch. It's the recursive loop: every new feature built on an unvalidated foundation makes the foundation harder to expose and fix. The technical debt is invisible. It compounds in the business layer, not the codebase. The standard advice — "talk to customers," "niche down," "charge more" — is not wrong. It is incomplete. It describes destinations without specifying load-bearing structures. A founder who can architect a distributed system can't navigate a vague instruction to "find product-market fit" any more than an engineer can build a bridge from "make it strong." This skill gives you the structural specification: a repeatable system for stress-testing market demand against your product, defining the exact customer whose constraints your product resolves, and constructing a pricing model with documented logic — not intuition. What you get: SKILL.md — the complete profitability navigation protocol: market validation sequences, ICP definition frameworks, and pricing architecture with decision logic at each stage. SETUP_GUIDE.md — deployment instructions for integrating this workflow into your existing research and iteration process. EXAMPLES.md — annotated walkthroughs of the system applied to real micro-SaaS scenarios, showing outputs at each structural layer. CHANGELOG.md — version history documenting evolution of the methodology and structural revisions. External dependency: None. Runs entirely within your agent's context.