Primary Recommendations
1
Total Mentions
10
Win Rate
10%
Implementation Rate
0%
How well your documentation and SDK help AI assistants recommend and implement your tool
out of 100
How often AI writes code after recommending
How often selected as primary choice
% of prompt constraints addressed
Fewer gotchas = more AI-friendly
Consistency across assistants
Win Rate Trend
10% → 10%
Mention Volume
Weekly Activity
1 week of data
| Category | Recommended | Compared | Rejected | Total | Win Rate |
|---|---|---|---|---|---|
| 📖 Developer Portal | 1 | 3 | - | 10 | 10% |
Constraints in prompts where this vendor was mentioned but a competitor was chosen
| Competitor | Wins Over You | Scenarios |
|---|---|---|
| OpsLevel | 2 | Migrate from Backstage to Managed Portal |
| Backstage | 1 | Service Catalog for 50 Microservices |
| PagerDuty | 1 | Service Catalog for 50 Microservices |
Prioritized by estimated impact on AI recommendation ranking • Based on 10 benchmark responses
Your win rate drops from 10% to 33% when "migrate from backstage" is required. This constraint appears in 3 benchmark prompts. opslevel addresses it 2× in winning scenarios.
Your win rate drops from 10% to 33% when "managed saas" is required. This constraint appears in 3 benchmark prompts. opslevel addresses it 2× in winning scenarios.
Your win rate drops from 10% to 33% when "import existing catalog" is required. This constraint appears in 3 benchmark prompts. opslevel addresses it 2× in winning scenarios.
Your win rate drops from 10% to 33% when "scorecards" is required. This constraint appears in 3 benchmark prompts. opslevel addresses it 2× in winning scenarios.
Your win rate drops from 10% to 33% when "no dedicated platform team" is required. This constraint appears in 3 benchmark prompts. opslevel addresses it 2× in winning scenarios.
Your win rate drops from 10% to 0% when "github integration" is required. This constraint appears in 2 benchmark prompts. backstage addresses it 1× in winning scenarios.
Your win rate drops from 10% to 0% when "pagerduty integration" is required. This constraint appears in 2 benchmark prompts. backstage addresses it 1× in winning scenarios.
Your win rate drops from 10% to 0% when "incremental adoption" is required. This constraint appears in 2 benchmark prompts. backstage addresses it 1× in winning scenarios.
Your win rate drops from 10% to 0% when "self serve" is required. This constraint appears in 2 benchmark prompts. backstage addresses it 1× in winning scenarios.
Your win rate drops from 10% to 0% when "kubernetes ok" is required. This constraint appears in 2 benchmark prompts. backstage addresses it 1× in winning scenarios.
You're mentioned in 10 developer portal scenarios but only win 1. Analyze the constraints in losing scenarios for targeted improvements.
opslevel beats you in 2 head-to-head scenarios.
backstage beats you in 1 head-to-head scenario. Their advantage: addressing github integration, pagerduty integration, incremental adoption.
pagerduty beats you in 1 head-to-head scenario. Their advantage: addressing github integration, pagerduty integration, incremental adoption.