- When you need a fully transparent, self-serve pricing model
- If procurement requires immediate list pricing for bake-offs, IronHQ’s lack of public list pricing may slow evaluations.
- When your organization requires publicly published security attestations
- If your vendor risk program mandates publicly available SOC 2 Type II / ISO 27001 documentation and a trust center, IronHQ’s public materials do not provide clear attestations; buyers should request documentation under NDA if necessary.
- When you require an end-to-end DMS across every dealership department
- If the priority is a single system for parts, service, accounting, rental, warranty, and wholegoods, a full DMS vendor may be more appropriate than a CRM/CPQ-centric solution.
- When you require extensive customization and a large integration ecosystem out of the box
- Horizontal CRMs such as Salesforce or Dynamics may be better suited if you have significant internal IT resources and require advanced customization, at the cost of higher implementation effort.
- When your procurement process relies heavily on peer-review volume and benchmarking
- If decision-making depends on high-volume third-party review platforms (Gartner Peer Insights, G2, TrustRadius), IronHQ’s low presence on those platforms limits the availability of peer benchmarking data.
- Current limitations acknowledged by the vendor
- Contractual limitations: Terms of Service include standard SaaS disclaimers and limit remedies for availability issues to service credits under specified conditions.
- Roadmap / future changes
- Ownership change: IronHQ was acquired by Perseus in March 2026 and is intended to join DIS. Product packaging, roadmap priorities, and support processes may change post-acquisition; buyers should seek clarity on roadmap alignment.
- Scale limitations
- Not publicly documented. Vendor content suggests applicability from single-store to multi-store dealerships, but no formal performance benchmarks were found in public materials.
- Security/compliance gaps (publicly visible)
- No publicly documented SOC 2 or ISO certifications were found in the sources reviewed.
- API limitations or integration constraints
- Not publicly detailed; Terms reference third-party applications and user guides that list integrations, but those guides were not located in public documentation during this research.