- Company sizes or stages where this product is overkill or insufficient
- Very early-stage dealers with minimal RMR and few accounts may find per-account/per-invoice fees and onboarding overhead not worth it.
- Industries or use cases where competitors are clearly superior
- Businesses needing full general-ledger accounting and complex multi-entity finance may prefer accounting/ERP-first platforms and keep billing ops separate.
- Technical requirements that this product cannot meet
- If you require SSO/SAML, SCIM provisioning, customer-managed encryption keys, strict data residency, or a published security/compliance package—Cornerstone’s public documentation does not currently confirm these.
- Budget constraints that make alternatives more appropriate
- If your subscriber count is large and your billing complexity is low, a lower-cost billing engine (or in-house process) may be cheaper, though it may cost more in labor.
- Specific workflows or integrations where the product falls short
- If your central station integration is niche, custom, or requires real-time bidirectional sync, you must confirm support and scope.
- Red flags in the buying process
- Lack of public pricing for most tiers can slow procurement and complicate ROI planning.
- Vendor ROI metrics and efficiency claims are largely marketing-led; demand methodology.
- Current limitations acknowledged by the vendor
- Not explicitly presented as “limitations,” but help desk articles indicate operational constraints such as strict invoice run dates and the need to handle “past next bill dates” manually in certain scenarios.
- Features on the roadmap (not yet available)
- Not clearly published as a roadmap in sources reviewed.
- Scale limitations (at what volume/size does it break down?)
- No Frills plan explicitly notes “limited to 500 accounts maximum.”
- Enterprise tier implies scaling beyond standard packages, but no quantified limits are published.
- Security or compliance gaps
- No public SOC 2/ISO documentation found.
- Data residency, SSO/SCIM, and encryption specifics not clearly documented.
- API limitations or integration constraints
- Integrations exist (central station-related; Zapier listed on Capterra), but breadth/depth and API availability are unclear from public materials.