What it is
Velaris is an AI-native customer success platform — health scoring, success plans, analytics, automations, and a chat-based AI Copilot — aimed at post-sales teams that want the AI layer built in rather than bolted on. London-founded (2021, Octopus Ventures-backed seed), it’s a newer entrant positioned directly against Gainsight, Vitally, and Planhat. The pitch: the same CSM workflow surface those tools offer, but with a Copilot that drafts QBRs, builds success plans, and answers portfolio-level questions (“which accounts show expansion potential this quarter?”) instead of leaving the CSM to assemble the answer by hand.
Why it shows up in Customer Success stacks
- Copilot over dashboard. Velaris leads with an AI Copilot that reads across accounts, meetings, emails, tickets, and notes, then drafts the artifact (QBR, onboarding plan, account plan) rather than just surfacing a number. This is the differentiator versus the older CSP generation where AI was a late add-on.
- Background signal agents. Context-aware agents monitor the book for churn and expansion signals, sentiment-label customer comms, and alert the CSM — closer to Pendo-style signal-watching than a static health dashboard.
- AI-native, not retrofitted. Health scoring, account summaries, and sentiment analysis were designed around the model from the start, which shows in the Copilot’s portfolio-level reasoning. That’s the reason a CS team picks it over a Gainsight/Vitally that added AI columns later.
Pricing
Velaris is custom-quoted; no public pricing tiers. The model is license-based — a fixed number of full users plus unlimited viewers, with add-ons. Expect mid-market deployments to land in the low-to-mid five figures annually and enterprise higher, in the same band as Vitally and ChurnZero, but confirm directly — there’s no published number to anchor on, and pricing transparency is a recurring reviewer complaint. We set pricing_starts_at to null rather than invent an entry price.
Best for
- $5-100M ARR B2B SaaS CS teams (roughly 5-30 CSMs) that want the AI Copilot as the primary surface, not a feature flag.
- CS leaders replacing a spreadsheet-or-CRM workflow who’d rather start on an AI-native platform than buy a legacy CSP and wait for its AI roadmap.
- Teams whose CSMs spend real time drafting QBRs, success plans, and account summaries — that’s where the Copilot earns its keep.
Watch-outs
- Younger product, thinner track record than the incumbents. Smaller install base than Gainsight/Vitally; fewer battle-tested enterprise references. Guard: ask for references at your ARR band and CSM count, and pressure-test the integrations you actually depend on before committing.
- No MCP server today. If your plan is to drive Velaris data from Claude or a custom agent over MCP, that path isn’t available — you’re on the REST API and the built-in Copilot. Guard: confirm the API covers your read/write needs; don’t assume programmatic parity with the Copilot UI.
- AI output quality tracks data quality. Copilot drafts and health scores are only as good as the synced meetings, tickets, and product-usage signal feeding them. Guard: confirm your product-analytics and support integrations are mature before expecting useful churn/expansion calls — a sparse data layer gives confident-but-empty drafts.
- Custom pricing, opaque comparison. Without published tiers you can’t quickly benchmark against Vitally or ChurnZero. Guard: run parallel quotes and normalize on per-CSM cost at your seat count.