Linear integration
Maximus reads Teams, Projects, Issues, Cycles and their updates from Linear over a read-only connection. The connection feeds the Onboarding checkpoint: Maximus tracks the projects and issues the first-value milestone depends on, compares each cycle's scope at start against its scope now, and escalates to the CSM when a committed project misses its target date.
Linear is one of the systems Maximus reads to run the Onboarding checkpoint. Below: the exact objects it reads, how the connection is made, and what runs once it is live.
- Category
- Delivery
- Lifecycle checkpoint
- Onboarding
- Access requested
- Read-only by default
- Write access
- Opt-in per action
Maximus reads your whole stack.
The exact objects and fields. This is the whole of what Maximus reads from Linear — a list, not a claim about a category of tooling.
| Object | Fields read |
|---|---|
| Teams | name, key, members |
| Projects | name, state, target date, lead |
| Issues | state, priority, assignee, estimate, updated date |
| Cycles | start date, end date, scope at start, scope now |
| Issue updates | state changes, cycle moves, target date changes |
Two-way sync with your CRM. Read access to everything else. No rip-and-replace.
Connect Linear
Four steps, and the first one is an OAuth handshake with read-only scopes. There is no import to run and no data model to migrate. Least-privilege integrations: read-only scopes by default; write scopes opt-in per action.
Step 1: Connect Linear
OAuth into Linear. Read-only by default, and most teams see their first risk scores within one business day.
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.
How Linear data reaches the lifecycle
Where the data goes after the handshake, and where it stops.
- SourceLinear — Delivery.
- Read path5 objects and 19 fields, read with read-only scopes.
- CheckpointOnboarding, on the account's lifecycle timeline.
- ActionAgents run the plays below: they draft the follow-up, open the Jira ticket, brief the CSM in Slack, and escalate what actually needs a human.
Five agent plays that run on Linear
Five of the prebuilt plays that run on this data, named as they appear in the product. Each one is a checkpoint, an owner, a deadline and a defined exit — not a notification.
Onboarding chase
Runs the onboarding project and its milestone SLAs, so a slipping step is chased the day it slips (§5 B.13).
Adoption dip
Fires on the day-30 adoption dip, with an owner, a deadline and a defined exit (§4).
Ticket-storm escalation
Routes the escalation by severity, segment or ARR band, and opens the Jira ticket with the context attached (§5 A.8–A.9).
Renewal prep
Runs the 180/120/90/60/30-day renewal countdown plays and auto-drafts the QBR deck in your brand voice (§5 B.12, A.7).
Expansion signal
Turns an expansion trigger into a play, with the evidence attached (§5 B.11).
Every run is logged — each action, its input, its output and the reasoning trace behind it — and approval gates are configured per action class (§5 A.5).
What Maximus is allowed to touch in Linear
Least-privilege integrations: read-only scopes by default; write scopes opt-in per action. Write access is granted by you, per action, not by the install.
| Object | Access requested | Write access |
|---|---|---|
| Teams | Read | Not requested by default |
| Projects | Read | Not requested by default |
| Issues | Read | Not requested by default |
| Cycles | Read | Not requested by default |
| Issue updates | Read | Not requested by default |
SOC 2 Type II: In progress — not yet verified · GDPR and India DPDP: In progress — not yet verified · SSO/SAML · Data residency in United States, European Union, India
Linear and the customer lifecycle
The narrative this page carries about Linear and the Onboarding checkpoint.
Delivery slippage is the leading indicator nobody watches
Onboarding starts at the kickoff and exits when the first value milestone is met and the customer's administrator is trained. The milestone is usually delivery work wearing a customer-facing name: an integration that has to ship, a migration that has to finish, a workflow that has to be configured. Owned by the CSM and the implementation lead, the stage runs its checks on day 7, day 21 and day 45.
Linear is where that work is planned. Maximus reads the projects and issues behind the milestone and reports the slip to the person who owns the customer relationship, because the engineers already know the work is late and the CSM is the one who has to say something about it.
What the milestone check needs from the tracker
Three questions decide whether a milestone is at risk: is the committed work still in flight, has its target date moved, and has anything been added to the cycle that was not there when it was planned. Linear answers all three from project states, target dates and cycle scope, and Maximus turns that into a checkpoint status rather than a dashboard the CSM has to go and read.
The escalation itself is routed by severity, segment and ARR band, so an enterprise account with a slipping migration and a mid-market account with a cosmetic delay do not arrive in the same queue, and the same signal informs the onboarding project tracking the site describes as milestone SLAs.
What the connection writes
Reads happen at install. Writes are opted in one action at a time.
| Action | Read | Write | Default |
|---|---|---|---|
| Milestone risk detection | Projects, issues, cycles, updates | None | At install |
| Onboarding status reporting | Projects, issues, cycles, updates | None | At install |
| Escalation issue with context | Account and health drivers | A new issue | Opt-in per action |
What this connection does not do
- It does not read issue comments, documents or attachments as part of the risk model. It reads states, dates, estimates and state changes.
- It does not move work between cycles or change a priority. Delivery decisions stay with the engineering team.
- It does not write at install; each write is an approved action and every action is logged.
Connecting it
Maximus reads with read-only scopes by default, there is no migration to run and nothing to move, and the connection is live the day the Linear admin authorises it. The read surface starts at Teams and stops where this page says it stops: nothing else in the account is read, and no field outside the list above is requested.
Questions about Linear
The three things buyers ask about this connection before they sign.
Where Linear fits
The integrations near this one, then the pages a buyer reads before buying.
- Jira integration
The Jira objects and fields Maximus reads, the delivery risks it detects, and how it opens an escalation ticket with the context attached.
- Slack integration
The Slack surfaces Maximus reads, how sentiment on customer channels feeds the health score, and where its own escalations are posted.
- Salesforce integration
The Salesforce objects and fields Maximus reads, how writeback keeps one forecast, and what the renewal countdown does with the opportunity record.
- Pricing
$189 per seat per month, $170 when billed yearly — every feature, every integration, unlimited managed accounts.
- Trust and security center
SOC 2 Type II: In progress — not yet verified · GDPR and India DPDP: In progress — not yet verified · SSO/SAML · Data residency in United States, European Union, India
Stop reacting to churn. Start running the lifecycle.
Most teams connect their stack and see their first risk scores within one business day. There is no implementation fee.
14-day money-back guarantee.