Agent Skills · ZIP download

SaaS Opportunity & Pricing

Compare customer problems, existing alternatives and willingness to pay before committing to a SaaS build.

$9One-time purchase · USD

You’ll review the offer on Whop before paying.

Cover of SaaS Opportunity & Pricing

What’s included

In the download

  • 16 task Skills and one router
  • Customer jobs and alternative solutions
  • Pricing scenarios and willingness-to-pay tests

What you can produce

  • A customer and alternatives record with sources, assumptions and gaps.
  • A price and cost scenario comparison with contribution and break-even calculations.
  • A CTA and demand-test record that separates test submissions, qualified responses and duplicates.
What’s included
Use cases and outputs

How to use it

  1. Choose the next decision

    Open README.md in the ZIP. Run node src/cli.mjs list --route discover or list --route validate to find the checks that match your stage.

  2. Check the offer path

    Use node src/cli.mjs example S14 to see the CTA input format. Record where a click leads and attach a separate storage receipt if the test submits a form.

  3. Review the evidence

    Apply your price assumptions and observed responses to the relevant checks. Use --out artifacts/project to save JSON and read the demand gate for the next build decision.

Before you buy

Pick this edition if

  • Founders deciding which customer problem is worth testing before they commit development time.
  • Teams with an early offer that need to compare pricing scenarios and verify where the call to action leads.

What you’ll need

  • A proposed customer segment and problem, existing alternatives, interview notes or other evidence of demand.
  • A price and cost assumptions. For an offer test, bring the page URL, test window, qualifying event and decision thresholds.

Demand conclusions depend on your own interview or experiment evidence. A synthetic form response only validates the supplied example.

Questions

Can I start before I have a landing page?

Yes. Start with customer problems, alternatives and price assumptions. Use the CTA check when you have a page you can inspect.

What helps me decide whether to build?

The validation gate compares observed qualifying events, spend and exposure with thresholds you set before the experiment.