sales-skills/sales-saasytrends

SaaSy Trends Platform Help

SaaSy Trends (saasytrends.com) is a SaaS competitor/trend database and idea-discovery tool: a searchable index of 30,000+ SaaS companies across 2,000+ categories, each ranked by the growth of its Google brand-search volume (what people search to find that company, refreshed monthly). You use it to spot rising niches, scan the competitors in a category, and find a niche worth cloning, backed by a free OpenAI-powered SaaS Idea Generator and free utility tools (Terms-of-Service / Privacy-Policy generators, Google-Docs-to-HTML). It is a discovery / market-research tool, not proof that anyone will pay for your idea, and it has no public API — it's a UI web app with a one-time lifetime plan.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

Ask only what you can't infer:

1. What do you want from SaaSy Trends?
   • A) Mine the database (companies ranked by brand-search-volume growth) to find a rising niche or competitor set
   • B) Run the free SaaS Idea Generator and interpret what it hands back
   • C) Understand the free tools vs the paid plan (what the one-time lifetime plan unlocks, the 100-product tracking cap)
   • D) Get the data out / automate it (export / API reality)
   • E) Judge whether the brand-search-volume signal is trustworthy enough to act on
2. What's the real question — "what should I build / is this idea worth building?" or "how do I use this tool?" If it's the go/no-go decision, that's /sales-idea-validation (a database browse and an AI-generated idea are not demand) — route in Step 2.

Skip-ahead: if the user wants the validate-before-building method or to compare validators across the market, that's a /sales-idea-validation question — route immediately.

Step 2 — Route or answer directly

| If the user's question is about… | Route to | |---|---| | The validate-before-building method, or the go/no-go decision itself | /sales-idea-validation {question} | | Comparing SaaSy Trends against other validators/discovery tools (IdeaBrowser, BuildOrNot, VentureVault, Ideagrape…) | /sales-idea-validation {question} | | Reddit-based real-demand discovery / scoring as its own workflow | /sales-trendseeker {question} | | Broader trend / content research (topics, keywords for content) | /sales-content {question} | | Building the smoke-test / fake-door landing page to test real demand | /sales-funnel {question} | | Growing a pre-launch waitlist / capturing real demand | /sales-audience-growth {question} |

When routing, give the exact command: "This is a {domain} question — run: /sales-idea-validation {original question}"

Otherwise, answer SaaSy Trends-specific questions using Step 3.

Step 3 — SaaSy Trends platform reference

Read references/platform-guide.md for the full reference — the database and its filters, what "brand-search-volume growth" actually measures and its blind spots, the free tools (Idea Generator + legal/utility generators), the one-time lifetime pricing and the 100-product tracking cap, and the no-public-API automation reality (no API/webhooks/Zapier/MCP).

Answer using only the relevant section — don't dump the full reference.

Step 4 — Actionable guidance

• Use SaaSy Trends for discovery, not for the decision. Its real value is the database — 30,000+ companies across 2,000+ categories ranked by brand-search-volume growth — to find a rising niche and see who already competes in it. Tell the user to treat it as a shortlist + competitor/market scan, then take the go/no-go from a real demand test (smoke test / pre-sale), not from a database browse. Route the real test to /sales-idea-validation.
• Frame "brand-search-volume growth" precisely — it's demand for existing companies, not for your idea. The metric is the monthly growth of Google searches for a company's brand terms; rising volume means that incumbent is gaining traction, which signals a hot niche and validates that a market exists — but it says nothing about whether a new entrant (yours) can win, or whether anyone wants your specific twist. Explain it as a niche/competitor signal, not idea validation.
• Treat the free Idea Generator's output as a directional prompt, not demand. It's an OpenAI wrapper that returns ideas "based on validated business problems" drawn from the database — useful for angles and differentiation, but it validates nothing. Tell the user to keep the framing (niche, differentiation, competitor list) and earn the real answer from a smoke test / pre-sale.
• Verify the numbers — the data is estimated and AI-categorized. Companies are pulled from 20+ sources, categorized by AI, and enriched with search-volume estimates; brand-search volume is a proxy (it misses companies people find without searching the brand, and can be inflated by generic-name collisions). Have the user sanity-check any volume/growth figure and category placement against a primary source (the company's own traffic, similarweb) before quoting it.
• Set pricing expectations as best-effort, and point to the live page. There's a single one-time lifetime plan (INDIVIDUAL, ~one payment) unlocking full database access, tracking of 100 SaaS products, 1 seat, and no ads; the Idea Generator, legal/utility generators, and the weekly newsletter are free. Present all pricing/limits as best-effort — confirm on saasytrends.com/pricing (a small indie tool, terms move).
• There's no public API — don't plan an integration around it. If asked to export or automate, say plainly there's no documented public API, no webhooks, no Zapier/Make, no MCP — it's a UI web app. Give the workable fallbacks: (1) copy the data you can see into your own store (mind their terms and the 100-product tracking cap), and (2) pull brand-search-volume from source yourself — Google Keyword Planner / an SEO API (Ahrefs, Semrush) — if you need it scripted. The thing worth automating is a real demand signal (landing-page conversions), not the directory.

If you discover a gotcha or tip not in references/learnings.md, append it there with today's date.

Gotchas

Best-effort from research (2026-07) — SaaSy Trends is a small indie tool; its pricing, database counts, and metric definitions move. Verify at saasytrends.com.

• Brand-search-volume growth ≠ validated demand for your idea. It measures how fast searches for an existing company's brand are growing — a niche/competitor heat signal, not evidence a new entrant (or your specific twist) will get paid. Take the go/no-go from a real behavior test.
• The signal is a proxy with blind spots. Brand-search volume misses companies discovered without a brand search (word of mouth, app stores, integrations) and can be skewed by generic or colliding brand names; the numbers are estimates, not audited analytics.
• The data is AI-categorized from 20+ sources. Category and sub-category placement is automated, so a company can sit in the "wrong" bucket — verify category leaders rather than trusting the label.
• The free Idea Generator is an OpenAI wrapper. It returns plausible ideas from database problems in 15–30s; it's a brainstorming aid, not a validator — a generated idea is not demand.
• One plan, one-time payment, 100-product tracking cap. The paid tier is a single lifetime purchase (no subscription); tracking is capped at 100 SaaS products on 1 seat. Confirm current pricing/limits on the site before quoting.
• No public API, no webhooks, no Zapier/Make/MCP. It's a UI web app — you can't script or batch it; pull brand-search volume from an SEO API yourself if you need it programmatically.

Related skills

• /sales-idea-validation — The tool-agnostic validate-before-building method + the full validator/discovery landscape (use this to actually decide build-or-not; a database browse and an AI-generated idea are not demand)
• /sales-buildornot — BuildOrNot platform help (a sibling startup-idea discovery data platform + free AI evaluator — datasets of revenue-ranked tools, Reddit ideas, trending topics; the data is a shortlist, not demand)
• /sales-venturevault — VentureVault platform help (a free browsable vault of AI-scored, pre-researched startup ideas — discovery, not demand)
• /sales-trendseeker — Trend Seeker platform help (Reddit-based demand discovery + evidence scoring — a real-signal sibling to SaaSy Trends' database)
• /sales-content — Broader trend / topic / keyword research for content once you've picked a niche
• /sales-funnel — Build the smoke-test / fake-door landing page the real demand test runs on
• /sales-audience-growth — Grow a pre-launch waitlist and capture real demand
• /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do -a claude-code

Examples

Example 1: "I want to build something in a growing niche — can SaaSy Trends help me find one?"

User says: "I want to clone a smaller version of a SaaS that's clearly taking off. Is SaaSy Trends good for finding one?" Skill does: Positions SaaSy Trends as a discovery tool — point the user at the database, sorted by brand-search-volume growth, filtered by category / business model, to build a shortlist of rising niches and scan each niche's incumbents. Frames the growth metric as a signal that an incumbent is gaining traction (a hot niche), not that a new entrant will win, and warns the volume/category data are AI-estimated (verify against a primary source). Then insists the go/no-go comes from a real demand test, routing the decision to /sales-idea-validation and deeper Reddit signal to /sales-trendseeker. Result: The user gets a data-driven shortlist of growing niches to research, not a false sense that a rising competitor equals demand for their version.

Example 2: "SaaSy Trends' idea generator gave me a great idea — should I build it?"

User says: "I used the free SaaS Idea Generator and it gave me an idea I love. Good to go?" Skill does: Explains the generator is an OpenAI wrapper producing ideas from database problems — useful for angles and differentiation but validating nothing on its own. Tells the user to keep the niche/differentiation/competitor framing and earn a real answer: a smoke-test landing page to a pre-set conversion threshold, then a pre-sale for willingness-to-pay — routing the real test to /sales-idea-validation. Also notes the brand-search-volume ranking can confirm the niche is hot even when the specific idea still needs testing. Result: The founder gets real demand signal before building, using the generator's structure, not its enthusiasm.

Example 3: Can I export SaaSy Trends' database via an API? (developer/automation)

User says: "I want to pull SaaSy Trends' brand-search-volume rankings into my own database via API." Skill does: States plainly there's no documented public API, no webhooks, no Zapier/Make, no MCP — it's a UI web app with a 100-product tracking cap on the paid plan, so there's no supported way to export programmatically. Suggests the fallbacks: copy the visible data into your own store (mind their terms and the cap), or reconstruct the signal from source — pull brand-term search volume via Google Keyword Planner or an SEO API (Ahrefs, Semrush) and rank it yourself. Notes the thing worth automating is a real demand signal (landing-page analytics), not the directory. Result: The user avoids building on a non-existent API and picks a workable path to the underlying signal.

Troubleshooting

A rising company on SaaSy Trends doesn't feel like it validates my idea

Symptom: A competitor's brand-search volume is climbing, but you're unsure that means your version will sell. Cause: Brand-search-volume growth measures demand for an existing company's brand — it confirms the niche is heating up, not that a new entrant (or your specific twist) will win. Solution: Use the signal to pick a hot niche and scan incumbents, then earn the go/no-go from a real demand test — a smoke-test landing page and a pre-sale — via /sales-idea-validation.

The volume or category numbers look off

Symptom: A company's search-volume figure or category placement doesn't match what you expected. Cause: SaaSy Trends pulls from 20+ sources, categorizes with AI, and enriches with estimated search volume — brand-search volume misses non-search discovery and can be skewed by name collisions. Solution: Treat the numbers as directional and verify any figure/category against a primary source (the company's own traffic, similarweb) before quoting it or basing a decision on it.

I want an API or a way to export/automate the database

Symptom: Want to script SaaSy Trends or pull its rankings into another system. Cause: SaaSy Trends has no documented public API, webhooks, or iPaaS connectors — it's a UI web app, and the paid plan tracks only 100 SaaS products. Solution: Copy the visible data into your own store (mind their terms and the cap), or reconstruct the signal from source — pull brand-term search volume via Google Keyword Planner or an SEO API (Ahrefs, Semrush) and rank it yourself. Automate a real demand signal (landing-page analytics) instead. See /sales-idea-validation.