Your CSM team, multiplied by agents.
Maximus connects to HubSpot, Salesforce, Jira, Slack and Zendesk, then runs the customer lifecycle for you — proactive checkpoints, early churn signals, and renewal forecasts your CFO will sign off on.
SOC 2 Type II (in progress) · GDPR (in progress) · SSO/SAML · Data residency in US, EU and India
Example data. Figures are ARR per account, in $K.
- Healthy
- At risk
- Churn risk
Bar height is fixed per band: short for healthy, medium for at risk, tall for churn risk.
Why the old way fails.
Your health scores are fiction.
They're built on last-quarter's CRM fields, not what's actually happening in tickets and Slack.
CSMs are doing triage, not strategy.
60% of the week goes to chasing status instead of expanding accounts.
Renewals surprise you.
The first honest signal arrives 30 days out — far too late to save the contract.
From connection to board-ready reporting.
Step 1: Connect.
OAuth into HubSpot or Salesforce, plus Jira, Slack, Zendesk and your data warehouse. Read-only by default. Live in under an hour.
Step 2: Map the lifecycle.
Maximus builds a checkpoint timeline per contract — onboarding, first value, adoption review, QBR, renewal window, expansion trigger.
Step 3: Let the agents run.
Agents monitor every signal, draft the follow-up, open the Jira ticket, brief the CSM in Slack, and escalate what actually needs a human.
Step 4: Report on revenue.
NRR, GRR, logo and dollar churn, renewal forecast by confidence band — exportable, auditable, board-ready.
Describe the play in plain English.
Maximus turns it into an agent that runs on schedule or on trigger, with a full audit log of every action it took and why.See agentic workflows
Trigger
Example run: 120 days to renewal, risk sweep
Approval
Approved by the owning CSM
Reviewed the drafted follow-up before it reached the customer.
Signals read
- Zendesk: ticket volume up over the trailing 30 days
- Jira: a committed epic slipped past its date
- Slack: escalation raised in the shared channel
Actions taken
- Drafted the follow-up with the drivers and their sources
- Opened a Jira ticket linked to the account
- Briefed the owning CSM in Slack
Contract-aware milestones fire automatically.
Day-30 adoption dip, 120-days-to-renewal risk sweep, post-escalation recovery check — each with an owner, a deadline and a defined exit.See lifecycle checkpoints
Complete
Day-30 adoption dip
Adoption
- Trigger
- Monthly adoption dip detected after first value
- Owner
- CSM
- Deadline
- Play triggered on a 20% drop
- Exit
- Target seat activation and depth of use
Due now
120-days-to-renewal risk sweep
Renewal
- Trigger
- 120 days to contract end
- Owner
- CSM + AE
- Deadline
- Before the 90-day play
- Exit
- Renewal closed or loss reason recorded
Upcoming
Post-escalation recovery check
Escalation
- Trigger
- Escalation resolved
- Owner
- Support → CSM → VP
- Deadline
- Day 14 after resolution
- Exit
- Root cause closed, recovery check passed
Every signal on one timeline.
Example account, signals by source
68At risk
Four systems, one account, one timeline. Example data.
- Zendesk: tickets35%
Ticket volume up over the trailing 30 days.
- Jira: sprint slip25%
A committed epic slipped past its date.
- Slack: escalation25%
Escalation raised in the shared channel.
- HubSpot: deal stage15%
Renewal opportunity moved back a stage.
A score is useless without the why.
Example account risk score
72At risk
Recommended play: executive sponsor call and a recovery plan before the 90-day renewal play. Example data.
- Adoption dip45%
Weekly active seats down since the day-30 checkpoint.
- Support load35%
Reopen rate up and CSAT down on recent tickets.
- Sponsor silence20%
No executive sponsor activity this month.
One view of the whole book.
Example data
$840K
At-risk ARR
Enterprise segment, inside the renewal window
104%
Net revenue retention
Trailing twelve months
91%
Gross revenue retention
Trailing twelve months
Maximus reads your whole stack.
Two-way sync with your CRM. Read access to everything else. No rip-and-replace.
CRM
HubSpot
Reads companies, deals, contacts, tickets and engagements.
CRM
Salesforce
Reads accounts, opportunities, contacts, cases, contracts and Tasks and Events.
Delivery
Jira
Reads projects, epics, issues, sprints and issue changelog.
Communication
Slack
Reads channels, Slack Connect channels, messages and users.
Support desk
Zendesk
Reads tickets, users, organizations, groups and satisfaction ratings.
Support desk
Intercom
Reads contacts, companies, conversations, messages and notes.
Delivery
Linear
Reads teams, projects, issues, cycles and issue updates.
Communication
Microsoft Teams
Reads teams, channels, messages and replies and members.
Revenue intelligence
Gong
Reads calls, transcripts, deals, accounts and users.
Data warehouse
Snowflake
Reads account tables, usage event tables, subscription and billing tables, seat and role tables and views and shares.
Data warehouse
BigQuery
Reads The tables or views you expose to Maximus.
Customer data
Segment
Reads sources, track calls, identify calls, group calls and destinations.
Billing
Stripe
Reads customers, subscriptions, invoices and Prices and Products.
Service management
ServiceNow
Reads incidents, change requests, problems and configuration items.
Support desk
Freshdesk
Reads tickets, contacts, companies, Agents and Groups and SLA tickets.
Communication
Zoom
Reads meetings, participants, recordings and users.
Knowledge base
Notion
Reads pages, databases, blocks, comments and users.
Your security review, pre-answered.
| Item | Status | What that means |
|---|---|---|
| SOC 2 Type II | In progress — not yet verified | Audit status is being confirmed against the current report. The report is made available under NDA on request. |
| ISO 27001 | In progress — not yet verified | Certification programme. The certificate is not held yet, so no certificate number is published. |
| GDPR and India DPDP | In progress — not yet verified | Consent is captured with its source and timestamp and is unchecked by default. The data processing addendum is being reviewed by counsel. |
| SAML SSO and SCIM | Available | |
| Field-level encryption | Available | |
| Regional data residency | Available | United States, European Union and India. Selected when the workspace is provisioned, not after the fact. |
| Customer data used for model training | Never — contractually committed | Customer data is never used to train foundation models, and that commitment sits in the data processing addendum. |