A software competitor describes itself in several places that do not always agree: a marketing site, a documentation portal, an integrations directory and a changelog. The question here is which products a buyer places next to yours in public material, and what each of them demonstrably does. You receive a competitor map, an offer comparison built on documentation rather than slogans, and a source log.
Vendors choose category names for search and for analyst coverage, so two products with the same label can solve different problems and two with different labels can compete for one budget. The map starts from the job the buyer hires the product for and from the way buyers phrase it on comparison and directory pages, then tests each candidate against its own documentation.
Where a feature appears only on a marketing page and not in the documentation, we describe it as the company's own statement, carry it as unavailable and flag the gap as an open question.
Usage, customer counts and revenue are not visible in public material. Where a vendor states a figure itself it is shown as the company's own statement, class unavailable until an independent source confirms it.
Each source type answers a different question, so the comparison table records which source every cell came from.
Shows what the product does today, which objects and limits exist, and what is described as available only on higher plans.
Shows direction and pace as written by the vendor, and which capabilities are new rather than long-standing.
Show which other tools the product connects to and how the vendor is positioned inside partner ecosystems.
Show how the offer is split into tiers and what is gated behind a sales conversation. We record the structure of the packaging, not a price list.
Show how buyers phrase needs and objections. They are read as opinion, with the platform's own incentives noted.
Needs to separate the incumbents buyers name from adjacent tools that merely overlap, so the map is wide on the niche edge and records why each tool was placed.
Needs to know whether competing suites already bundle the capability and in which plan, so documentation and packaging pages are read first.
Needs to see how rivals structure integrations and marketplace listings, so directory and partner pages lead the review.
Performance, reliability and support experience are not established from public pages. We do not test the software.
Future plans are visible only where a vendor publishes them, and are shown as the company's own statement, not as likely.
Positioning and pricing decisions are yours. The map supplies evidence and stops before them.
Research reports what can be established from public and provided sources. It is not a guarantee about a counterparty's future conduct and not legal advice.
No. The map is built from public material.
No. It is a dated map, not a monitoring system.
Where buyers name them in the sources reviewed, they appear as a separate group with the reason.
No obligation. We read your request and reply with a straight answer.
Tell us what you need to find out and by when. We confirm scope before any work starts.
Request research