Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    B2B SaaS Opportunity Hunter

    1

    Find evidence-backed B2B software opportunities by validating costly workflows, buyers, alternatives, and willingness to pay.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    B2B SaaS Opportunity Hunter

    B2B SaaS Opportunity Hunter

    Example session with this skill installed

    We are considering software for independent property managers who manually reconcile maintenance requests across email, spreadsheets, and vendor portals. We have interviewed four managers; two say reconciliation takes “hours each week,” but we have no time logs, pricing tests, market sizing, or verified retention data. Create an opportunity brief: clarify the job and stakeholders, identify evidence versus hypothesis, compare SaaS/API/service/process alternatives, suggest a narrow beachhead, design three low-cost validation tests with success and stop criteria, outline pricing discovery, and list data needed before making market or revenue claims. Treat this as a fictional case and invent no metrics.

    • Read your context and instructions
    • Compiled the b2b saas opportunity

    Opportunity brief — maintenance request reconciliation (fictional)

    Provisional thesis

    Independent property managers may have a recurring coordination problem when maintenance requests span email, spreadsheets, and vendor portals. The current evidence is too small and imprecise to support market size, willingness-to-pay, or product-market-fit claims. The next step is to measure workflow frequency and test whether a narrow customer segment will adopt and pay for a solution.

    Stakeholders and job

    • End user: property manager or coordinator triaging requests and tracking vendor follow-up.
    • Economic buyer: likely owner/operator or management firm principal; verify budget ownership.
    • Affected parties: tenants, maintenance vendors, owners, and support staff.

    Job hypothesis: capture a request once, route it to an appropriate vendor, track status, and keep tenant/property stakeholders informed. Confirm exceptions, urgent safety cases, and approval steps through observation.

    Evidence ledger

    StatementStatusWhat to collect next
    Four managers were interviewedUser-supplied fact for this fictional exerciseInterview dates, segment criteria, and exact questions
    Two said reconciliation takes “hours each week”Directional self-report, not measuredAsk for a two-week task diary or screen-share walkthrough; define what work is included
    Workflow spans email, sheets, and vendor portalsStated problem contextObserve one recent request end to end; record handoffs and failure modes
    Market size, pricing, retention, and ROIUnknownDo not publish estimates until sourced and tested

    Alternatives to compare

    • Process change: standard intake form and shared queue; lowest setup, may preserve manual coordination.

    Lightweight SaaS: unified request inbox, assignment, status, and audit trail; test workflow fit before building integrations.

    • API/integration layer: useful only if portal/email volume and access permissions support reliable automation.
    • Managed service: concierge coordination may reveal repeated edge cases, but carries labor and margin constraints.
    • Do nothing/current tools: benchmark honestly; switching and training costs may outweigh the pain.

    Beachhead hypothesis

    Start with small property-management firms handling enough recurring maintenance volume to feel coordination pain, but without an existing maintenance platform configured for their process. Segment by portfolio size and monthly request volume only after collecting representative data. Avoid assuming that “independent property manager” is a homogeneous market.

    Validation experiments

    Workflow diary (2 weeks): 8–12 qualified managers log each request’s intake, handoffs, time, delays, and rework. Success: repeated pain pattern with measurable task time or service impact across several firms. Stop/reframe if the task is rare, trivial, or already solved reliably.
    2.

    Concierge prototype: manually unify intake and vendor status for 3–5 willing firms using their existing tools. Success: repeated use and clear user-reported value; observe where automation is actually needed. Stop if participation requires unsustainable manual labor or disrupts critical service.
    3.

    Paid pilot offer: present a clearly scoped pilot and test several transparent price points with qualified buyers; request a real commitment or paid trial where appropriate. Success: buyers commit after understanding limits and data handling. Stop treating positive feedback alone as willingness to pay.

    Pricing discovery

    Interview the budget owner about current labor, software, vendor, and failure costs. Test a price metric (per unit, request volume, or portfolio tier) only after learning usage variability and value. Record objections, procurement constraints, and alternatives. Do not infer CAC, LTV, or ROI without measured acquisition and retention data.

    Decision gate

    Continue if diary evidence shows recurring costly coordination, a narrow buyer can approve a pilot, and the prototype demonstrates an adoptable workflow. Pivot toward process tooling or managed service if pain is real but software adoption is blocked. Stop if the process is infrequent, already adequately solved, or no buyer will commit after credible tests. All numbers and names here are illustrative; no external market research or customer evidence is asserted.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    B2B SaaS Opportunity Hunter

    Investigate business workflows to identify commercially testable B2B SaaS opportunities. This skill starts with a costly recurring problem, the people who experience and fund it, the current workaround, and evidence of business value. It does not produce generic idea lists or treat unverified market claims as facts.

    What it delivers

    • Segment, end user, champion, economic buyer, approver, and blocker map
    • Workflow and root-cause analysis covering triggers, handoffs, delays, errors, and cost
    • Existing alternatives review: software, internal tools, spreadsheets, services, and doing nothing
    • Evidence ledger separating verified facts, user evidence, estimates, hypotheses, and unknowns
    • Narrow beachhead customer and testable product thesis
    • Validation plan, interview questions, landing-page or concierge tests, and kill criteria
    • Commercial model, distribution, retention, feasibility, risk, and unit-economics hypotheses

    Method

    Map the process before proposing software. Quantify the pain only from defensible inputs; ask for source, timeframe, sample, and confidence. Determine who owns the workflow and budget, how often it occurs, and what happens when it fails. Compare product forms such as SaaS, API, automation, extension, service, or process change. Prioritize the smallest experiment that could disprove the opportunity.

    Evidence discipline

    Never invent TAM, customer counts, revenue, MRR/ARR, churn, retention, conversion, CAC, LTV, market share, competitor metrics, pricing, API access, compliance, or willingness to pay. Label sourced facts, derived estimates, scenarios, and hypotheses separately. Current market research should use accessible, relevant sources and retain citations or source notes. Treat interviews as directional evidence rather than representative market proof.

    Output

    A concise opportunity thesis, workflow map, buyer map, alternatives matrix, evidence gaps, solution and pricing hypotheses, validation experiments, risks, and a clear continue/pivot/stop recommendation. This is decision support; it does not guarantee product-market fit or investment outcomes.

    An opportunity brief does not prove market size, willingness to pay, product-market fit, or investment returns. Conclusions depend on the quality and representativeness of supplied evidence. Current competitor, pricing, or market claims require cited, current sources; interviews are directional. The skill does not access customers, analytics, or proprietary databases unless an authorized integration is present.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    Read Files
    Browser
    Network Access

    File Scopes

    User-selected
    interview
    market
    research
    and
    planning
    files
    only

    Use only files and sources authorized by the user. Research should be cited and distinguish facts, estimates, hypotheses, and unknowns. Do not treat interview self-reports as market proof, invent company metrics, or transmit confidential customer information to external services.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    No. It helps structure evidence and design tests that can validate or disprove an opportunity. Market demand, adoption, retention, unit economics, and profitability require real-world evidence.

    It can outline a method and required inputs, but it must not invent market or unit-economics numbers. Use sources, assumptions, calculations, and uncertainty labels. Validate with representative customer and acquisition data.

    Start with direct workflow observation and a narrow customer segment. Run the smallest tests that could disprove the thesis, such as a task diary, concierge pilot, or transparent paid-pilot offer. Define success and stop criteria before each test.

    New in Research & Analysis