The best software opportunities start with an unpleasant Tuesday.
Recurring workflows, clear buyers and switching costs matter more than a crowded feature category. Study the task users already pay to complete, then ask why a better tool would survive renewal.

Questions that matter in this market.
Use these as a research framework, not a claim that a measured trend proves demand.
What makes the current workflow expensive or slow?
Which data migration or integration could block adoption?
Turn uncertainty into a small, useful experiment.
Offer a narrow assisted pilot to a single job role. Track repeated use across several weeks before expanding.
Interpretation limit. A high-intent keyword is not a verified conversion rate or acceptable acquisition cost.
Follow the buyer
Distinguish operator, champion and budget holder; learn which one can actually sign.
Run a repeated-use pilot
Measure whether the same group returns without incentives over several work cycles.
Model the switching cost
List permissions, import needs, team training and support rather than only monthly pricing.
Compare query attention to product evaluations and retention interviews; avoid treating community enthusiasm as revenue.
Read source definitionsFind a recurring problem with a clear buyer.
Software interest becomes commercially useful when you can identify a repeated task, an existing budget and a reason to switch. A popular feature may also be copied by an incumbent. Look for integration requirements, onboarding costs and the teams approving a purchase. Search growth cannot establish retention or market size.
A practical first experiment
Offer a narrow assisted pilot to a single job role. Track repeated use across several weeks before expanding.
- Which existing budget would pay for this?
- What keeps a customer using it after the first month?

SaaS trends
Measured momentum. Useful context. A place to start.
GitHub repository activity: explore dated activity for Supabase. Useful for asking better questions, not predicting sales.
GitHub repository activity: explore dated activity for Apache Airflow. Useful for asking better questions, not predicting sales.
Wikipedia article views: explore dated activity for Software as a service. Useful for asking better questions, not predicting sales.
Wikipedia article views: explore dated activity for Salesforce. Useful for asking better questions, not predicting sales.
Wikipedia article views: explore dated activity for Slack (software). Useful for asking better questions, not predicting sales.
Wikipedia article views: explore dated activity for Zoom (software). Useful for asking better questions, not predicting sales.
Wikipedia article views: explore dated activity for Microsoft 365. Useful for asking better questions, not predicting sales.
Wikipedia article views: explore dated activity for Google Workspace. Useful for asking better questions, not predicting sales.
Wikipedia article views: explore dated activity for Figma. Useful for asking better questions, not predicting sales.
Wikipedia article views: explore dated activity for Atlassian. Useful for asking better questions, not predicting sales.
Wikipedia article views: explore dated activity for Customer relationship management. Useful for asking better questions, not predicting sales.
| # | Trend / category | Sources | Momentum | Growth | 6M outlook | History | Compare |
|---|---|---|---|---|---|---|---|
| 1 | SupabaseSaaS · Global | Regular Growth | +57% | Upward | |||
| 2 | Apache AirflowSaaS · Global | Regular Growth | +100% | Upward | |||
| 3 | Software as a serviceSaaS · Global | Stable | -46% | Upward | |||
| 4 | SalesforceSaaS · Global | Stable | -31% | Downward | |||
| 5 | Slack (software)SaaS · Global | Peaked | -25% | Downward | |||
| 6 | Zoom (software)SaaS · Global | Stable | -57% | Downward | |||
| 7 | Microsoft 365SaaS · Global | Peaked | -31% | Downward | |||
| 8 | Google WorkspaceSaaS · Global | Stable | -33% | Downward | |||
| 9 | FigmaSaaS · Global | Stable | -50% | Downward | |||
| 10 | AtlassianSaaS · Global | Peaked | -46% | Downward | |||
| 11 | Customer relationship managementSaaS · Global | Peaked | -31% | Downward |
A signal is the beginning.
Context makes it useful.
Search interest, pageviews and community activity measure different things. We keep the sources separate, show the available history, and distinguish projections from observations.
Read our methodologyWhat the index cannot establish.
Software interest becomes commercially useful when you can identify a repeated task, an existing budget and a reason to switch. A popular feature may also be copied by an incumbent. Look for integration requirements, onboarding costs and the teams approving a purchase. Search growth cannot establish retention or market size.
Questions to take into a real interview
- Which existing budget would pay for this?
- What keeps a customer using it after the first month?
Field notes for curious minds.
Practical guides to help turn what you observe into a decision.

