Case Study (Refreshed Edition, 2026): How SupplyAnchor Used Abhord to Win AI Mentions in Procurement SaaS
Company snapshot
SupplyAnchor is a mid‑market B2B SaaS for manufacturing procurement teams. The product automates three‑way match, PO approvals, and supplier onboarding across NetSuite and Microsoft Dynamics.
1) The initial problem
By October 2025, SupplyAnchor’s website traffic was steady, yet sales heard a new refrain: “We asked an AI assistant for vendors and didn’t see you.” Internal spot checks across popular LLMs showed:
- Brand not mentioned in 68% of high‑intent prompts (e.g., “best three‑way match SaaS for NetSuite,” “PO approval workflow for mid‑market manufacturing”).
- When mentioned, features were misattributed (e.g., “no native SOC 2,” “no NetSuite vendor bill sync”)—both incorrect.
- Competitors with thinner documentation were cited more often because their names overlapped with generic procurement terms, confusing entity recognition.
In short, SupplyAnchor was invisible or inaccurately described where buyers increasingly start: AI answers.
2) What Abhord’s analysis uncovered
After onboarding to Abhord in November 2025, the team ran an Entity & Answer Audit against 120 buyer‑intent prompts across six leading models and three vertical variants (discrete manufacturing, CPG, industrial distribution). Key findings:
- Mention Share: 14% average brand inclusion; only 6% top‑3 inclusion for core terms.
- Misattribution Rate: 31% of mentions contained at least one incorrect capability or integration.
- Source Coverage Gap: Only 18% of AI answers citing SupplyAnchor linked to owned, authoritative pages; most citations pointed to third‑party forums with outdated details.
- Entity Ambiguity: “Supply Anchor” and “procurement anchor” surfaced as generic phrases. Abhord’s Entity Graph showed weak disambiguation between the brand and a maritime logistics glossary entry.
-