Skip to content

Free for a week, then $199 per monthwith unlimited users and accounts.Start free trial →

Platform

The operating system for post-sales.

Five modules that share one data model - so the health score, the agents and the workflows are always looking at the same account.

Today's Focus

Today's Focus

A CSM's daily queue with tasks due today, at least two signals raised overnight, and a meeting - enough that it reads as a real morning, not an empty state.

Start the day knowing what needs you.

Not an org-wide dashboard - only your book. Tasks due today, the signals that fired on your accounts overnight, and the meetings you have coming. It is the page a CSM opens first, and the reason nothing else needs checking.

  • Tasks due today, across every account you own
  • Signals raised on your accounts while you were away
  • Today's meetings from your connected calendar
  • Scoped to you - a CSM sees only accounts assigned to them
Account 360

Account 360

One account open on the Overview tab: stat strip, health ring, signals list, the eight tabs visible.

Every account. One screen. No tabs.

Contract value, renewal date, product usage, open tickets, stakeholder map and journey stage - pulled from your CRM, product analytics and support desk into a single view. The interface is deliberately neutral; colour appears only where an account is at risk, so your eye lands where it matters.

  • A pinned first column, resizable widths and 21 optional columns
  • Inline editing of owner and dates, without leaving the table
  • Eight tabs per account: overview, details, contacts, documents, onboarding, agent runs, tickets, billing
  • Every edit audit-logged, keeping the previous value
Health Score

Six-Pillar Health Score

The health popover open, showing the per-factor "Why 37" breakdown. This is the "no black box" proof.

Health you can defend in a board meeting.

Most health scores are one number nobody trusts. Clynto scores six pillars separately - adoption, engagement, support, relationship, commercial and sentiment - and shows the driver behind every movement. Weights are yours to set; Clynto proposes a starting model from your historical churn.

  • A per-factor breakdown behind every score, visible on the account
  • Missing data is never penalised - no Mixpanel means no adoption penalty
  • Recomputed on a schedule you set, per Profile or per account
  • Pin a score by hand to pause recompute while you investigate
Usage Intelligence

Usage Intelligence

Per-account adoption against entitlement, with a visible decline curve.

Product analytics at the account level, not the event level.

Clynto pulls per-user, per-account usage daily from Mixpanel, your Usage API or seat counts, and turns it into what CS actually needs: seat utilisation, feature adoption, power-user concentration and decline curves. Usage is judged against what each customer actually bought, not a flat benchmark - running low reads as expansion, not risk.

  • Daily sync, no manual exports
  • Adoption percentage and active users per account
  • Judges pace against each account's own credits or seats, and flags "will run out early"
  • Feeds directly into the health score and the expansion workflows
Agents

Agents

20 agents, Profiles (Usage-Led/High-Touch/Self-Serve) and per-Profile step-mode dropdowns visible per row.

20 specialists, working every account, every day.

Each agent has one job. They read signals, reason about them with a tiered model architecture (heavy reasoning where it’s needed, lightweight classification where it isn’t), and act according to the policy you set.

  • Notify, draft for approval, or execute - set per workflow step, per Profile
  • A full audit trail carrying the reasoning behind each decision
  • Build custom agents without code, and test them against historical accounts
Explore the agent library →
Email Responder

Email Responder

All tickets across every account - subject, source, requester, priority and status - in one list.

It replies to what the customer actually wrote.

A customer emails your Clynto address, it becomes a ticket on the right account, and the agent reads the real subject and body, works out tone and intent, and writes a reply to what was said. Your templates are shown to the model as examples of how your company writes, never rendered and sent verbatim - a templated reply cannot answer a real question.

  • Saved as a draft by default - sending is a switch you throw
  • Threads on In-Reply-To headers, not just a "Re:" subject line
  • The customer's original subject is never rewritten
  • Priority and sentiment assessed from the message, written to the ticket
  • One reply per message, and it refuses no-reply, bounce and out-of-office mail
Campaigns

Campaigns

A campaign with its analytics filled in - delivered, open, click and bounce rates - so the numbers read as a real send rather than a draft.

Reach a segment without mail-merging a spreadsheet.

Build the audience with a filter, compose in a block editor, then send now or schedule it. Marketing campaigns honour unsubscribes automatically - anyone who has opted out is skipped without you managing a list - and sending is paced rather than dumped at your mail provider in one burst.

  • Audience built from a filter, materialised one recipient at a time
  • Block email builder, from a template or blank
  • Send now or schedule for a date and time
  • Delivered, open, click, bounce and failure rates per campaign
  • Paced sending, so a large campaign does not trip your provider
Workflow Builder

Workflow Builder

A workflow canvas with three Profile branches expanded (High-Touch Enterprise, Usage-Led, Self-Serve/PLG), each with its own agents and actions configured.

Your playbooks, finally running themselves.

Drag-and-drop triggers, conditions and actions - or describe what you want and Clynto builds the canvas. 15 workflows ship pre-built for the moments that decide NRR - Health Risk, Renewal Risk, Onboarding Stall, Champion Loss, Expansion Opportunity, QBR Cadence and more. Start from ours, ship yours.

  • Twelve trigger events, seven actions, and branches on Profile, health, ARR or renewal date
  • 15 workflows seeded on day one, as drafts you can inspect before publishing
  • The canvas refuses to let a workflow look fine while doing nothing
  • Run it now to test at 15-second intervals instead of waiting for the 15-minute sweep
Longtail Automation

Longtail Automation

The same branch-conditioned workflow canvas as workflow-builder - Profile branches, each with its own agents and actions.

The accounts too small for a CSM, covered anyway.

Your longtail still churns and still expands - it just never gets a human. Pick the Self-Serve / PLG profile for that part of your book, and its steps run automatically by default while your High-Touch Enterprise accounts stay approval-gated. The seeded workflows already route through Playbook Executor and Escalation Handler, so the "let it run itself on the small accounts" pattern is set up out of the box.

  • Three built-in Profiles by ARR range, each with its own thresholds and approval rules
  • Steps run automatically on Self-Serve / PLG while staying approval-gated on High-Touch Enterprise
  • Playbook Executor drives each sequence one step at a time
  • Escalation Handler is the circuit-breaker when a sequence stalls instead of looping
Reports

Reports

A generated QBR with the customer logo, the status badge and at least one chart visible. This is the asset that shows the output is sendable as-is.

The business review, already written.

Pick accounts and a period - monthly, quarterly, half-yearly or annual - and Clynto drafts an executive-styled review: summary, health with per-dimension commentary, adoption, support experience, risks, recommendations and an action plan. Every number is computed from your data; the narrative is written from those numbers, and a chart only appears where a real measurement exists.

  • Monthly, quarterly, half-yearly or annual periods
  • Edit any narrative before sending - the numbers stay as computed
  • Download as PDF, or send it and file it as a ticket on the account
  • A separate time-saved ledger for your own internal reporting
RevOps

RevOps

The ARR waterfall with new, expansion, contraction and churn all non-zero, so the breakdown is legible.

Where the revenue actually moved, and why.

Two views. Financial breaks ARR into new, expansion, contraction and churn by year, so a movement has a cause rather than just a delta. Billing projects invoice by invoice - who gets billed which month and for how much - driven by each account’s billing frequency.

  • ARR waterfall: new, expansion, contraction and churn
  • Invoice-level projection by month, from each billing frequency
  • Movements arrive from Stripe or from CSV import
  • Behind its own permission, separate from account access
Control

Three Profiles, set once by ARR.

Agents only think and write - it's the workflow step that acts, at the mode each Profile sets for it. Pick the Profile that matches an account and every step inherits sensible defaults.

Under ~$1M ARR

Self-Serve / PLG

High account volume, low touch. Most steps run automatically; a human sees only what actually needs them.

~$1M-$5M ARR

Usage-Led

A blend: day-to-day steps run themselves, and anything customer-facing waits for approval first.

~$5M-$10M ARR

High-Touch Enterprise

Your largest accounts. Agents reason and draft; a CSM approves every step that touches a customer.

Larry

Your data gets cleaner every week.

Larry asks the right person for a missing renewal date, owner, ARR figure or contact while they're already working - not as a separate cleanup project.

  • Surfaces the gap in context

    A card appears right where the person is already working, naming exactly what's missing and why it matters.

  • One answer, not a form

    Answer what you know - renewal date, owner, ARR, a contact - and move on. Nothing blocks you from skipping the rest.

  • Skippable, never nagging

    Skip for 7 days and Larry asks again later, instead of repeating itself every time you open the account.

Larry asking for a missing renewal date and owner inline, while a CSM is already working the account.
Health

A score you can show your working on.

Six weighted factors, out of 100. Missing data is left out of the formula entirely, never scored as zero - no Mixpanel means adoption just isn't part of that account's score.

Product usage

30 points

Adoption, active users and decline curves from Mixpanel or your Usage API

Open signals

25 points

Every unresolved signal raised against the account

Support backlog

15 points

Open tickets and how long they have sat unanswered

Payments

10 points

Failed or late invoices from Stripe

Engagement

10 points

Recent contact with the account across email and meetings

Onboarding

10 points

Time-to-value against your benchmark, while the account is still ramping

Healthy75 and aboveWatch50 – 74At riskbelow 50
Workflows

Twelve triggers, seven actions, and branches in between.

A workflow wires a trigger to agents to actions, splitting down branches on account conditions. Ten ship seeded on day one.

Triggers

  • Health score drops
  • Any signal raised
  • Product usage declining
  • Renewal approaching
  • Renewal flagged at-risk
  • Payment failed
  • Customer email received
  • QBR due
  • Onboarding stalled
  • Champion gone quiet
  • Seat utilisation scan
  • Market intelligence scan

Actions

  • NotifyIn-app notification to the CSM, and Slack if connected.
  • Create taskA task on the account, visible in Today’s Focus.
  • Raise signalAn open signal, respecting your signal rules.
  • Flag accountA named flag, surfaced on the Risk dashboard.
  • Send emailDrafts into the connected mailbox by default.
  • Update account fieldWrites one workflow-bookkeeping field.
  • Push to CRMPushes the account to Salesforce.

The canvas will not let a workflow look fine while doing nothing

This is the part that separates a builder from a diagram. Each of these is caught before you publish, not discovered three weeks later when nobody got the alert.

  • - A step whose type the engine has no handler for
  • - An agent that can’t be driven by the chosen trigger
  • - A required setting left empty
  • - A trigger that needs a paired agent to detect anything
  • - A missing integration the trigger depends on
  • - An empty branch that accounts would fall through
  • - A workflow with no agents and no actions at all

Seeded on day one

  • Health Risk
  • Renewal Risk
  • Renewal Window
  • Onboarding Stall
  • Champion Loss
  • Expansion Opportunity
  • Billing & Payment Risk
  • Inbound Email Auto-Reply
  • QBR Cadence
  • Market Intelligence
  • New Customer Handoff & Kickoff
  • Adoption / Usage Drop
  • Support Escalation & SLA Breach
  • Cancellation & Churn Save
  • Engagement Loss / Re-engagement
Studio

The documents your work already needs.

Written from each account's real data, not a blank template.

The Studio hub, with Business Reports and Campaigns live, and Proposals, NDA, Contracts and Presentations marked coming soon.

Business Reports

Live

Written from each account's real data - the same engine behind Reports.

Campaigns

Live

One sequence across a whole segment, sent to many contacts at once.

Proposals

Live

Renewal and expansion proposals, drafted from the account.

NDA

Live

Non-disclosure agreements from your own template.

Contracts

Live

Order forms and contract documents.

Presentations

Coming soon
Integrations

Connects to the stack you already run.

HubSpot

Read-only

Deals and pipelines into accounts, ARR, renewal dates, contacts.

Stripe

Read-only

Subscriptions and invoices into ARR, plus instant payment-failure and cancellation signals.

Freshdesk

Read / write

Support tickets, companies and satisfaction ratings.

Mixpanel

Read-only

Product usage into adoption %, active users and low-usage signals.

Gmail

Read / write

Inbox and sent rollups in; drafts and sends out.

Outlook / Microsoft 365

Read / write

The same sync as Gmail.

Slack

Write

Notification and signal fan-out.

Calendar (iCal)

Read-only

Calendar events into the Scheduler.

CSV / Excel

Import

Accounts, contacts, ARR movements, signals and tasks.

Salesforce

Write

The target of the Push-to-CRM action.

Usage API

Import

Send daily usage from your own product when you don’t run on Mixpanel.

HubSpot, Stripe, Mixpanel and support data are read-only - those adapters have no write method to call, so a bug cannot push data back. Salesforce sync writes accounts to Salesforce, and only when you connect it.

Explore all integrations →
The insight

Most CS work is repeatable. Larry handles that part.

In our discovery calls with 15+ founders and CS leaders, the same work came up again and again: spotting risk signals, chasing follow-ups, updating the CRM, preparing renewals. Larry, Clynto's AI CSM, does that repeatable work, so the people on your team can spend their time on the conversations that need judgment.

Larry handles

  • Signal detection and health scoring
  • Triage decisions on low-complexity risk
  • Initial outreach and follow-up cadences
  • CRM updates and task creation
  • QBR preparation and data gathering
  • Renewal timeline tracking and sequencing
  • Meeting summaries and action items
  • Pre-call briefings for every customer call

You handle

  • Executive relationship management
  • Renewal negotiations and pricing
  • Competitive displacement strategy
  • Account political dynamics
  • Champion building
  • Escalation judgment calls

How it works

Every signal. One place. Automatic action.

Clynto ingests signals from your entire post-sales stack and acts on churn risk and expansion the moment they appear - not at the next QBR.

One brain. One memory. Everything automated.

Larry does it all - signal detection, triage, outreach, CRM updates, QBR prep, renewal sequencing, expansion identification. Every action tracked. Every outcome fed back into Larry’s learning loop.

01

Signal fires

Champion goes silent. Mixpanel webhook fires. Normalised and written to Account Graph.

Instant

02

Larry reads context

45 days to renewal. Health trending down. No CSM touch in 18 days. QBR 4 months ago.

~2 seconds

03

Larry decides

High priority. Compounding renewal risk. Act now. Routes to Intervention Executor.

~5 seconds

04

Email drafted

Personalised email referencing last QBR goals. Approval card appears in CSM’s queue.

~30 seconds

05

CSM approves

30 seconds. One click. Larry sends, tracks response at 7 and 30 days, and learns.

30 sec CSM time

Total elapsed time from signal to CSM approval card: < 60 seconds

Step 01

Connect every signal

Pipe in CRM, billing, product usage, support and email. Clynto builds one live profile per account - no warehouse project, no engineering ticket, and read-only by default.

Explore integrations →

Northwind Robotics · sources

Syncing
  • HubSpot
  • Stripe
  • Slack
  • Freshdesk
  • Mixpanel
  • Gmail
  • Outlook
  • Salesforce

Northwind Robotics

northwind.io

Contract
$128,400 ARR
Renewal
24 days
Open tickets
4

Sample account - figures are illustrative

Meet Larry

Ask it in plain English. It checks, and tells you what it found.

"What does Orchid Health’s contract say about notice?" Larry answers from your live data and whatever contracts you’ve uploaded - and shows exactly what it checked.

Larry answering a plain-English question - what the contract says about notice - with the source it checked shown alongside.
  • Answers from what it can actually see

    Live account data and any contracts you've uploaded - not a guess.

  • Shows its work

    Every answer names what it checked, so you can verify it yourself.

  • Confirms before it acts

    Ask it to update records and it waits for your confirmation first - including a bulk update across up to 500 accounts in one request.

  • Voice and file uploads

    Talk to it, or hand it a document - a contract, a call transcript - and ask about what's in it.

Control

Nothing reaches a customer unless you said it could.

Every workflow step runs at a mode you set per Profile. The normal pattern is to let steps run themselves on Self-Serve accounts and require approval as you move up to High-Touch Enterprise.

Just notify

An in-app notification. Nothing else happens.

Needs approval

The step waits in Approvals for a human to confirm.

Draft in CSM mailbox

An email step lands as a draft in the owner’s mailbox. A human still clicks send.

Do automatically

A task, flag or CRM update runs with no human in the loop.

Send automatically

An email step sends for real, behind the guards that gate every auto-send.

Email never sends by surprise

Every email lands as a draft in your CSM's mailbox by default. An Admin has to switch on auto-send for a workflow before anything sends by itself - and even then, these guards hold a send back:

  1. 01No send if the contact was already emailed in the last 3 days
  2. 02No send if the account was emailed by another workflow in the last 48 hours - goes to Approvals instead
  3. 03Quiet hours: nothing sends 8pm-8am in the recipient’s time zone
  4. 04Held while a support ticket is open on the account
  5. 05Skipped entirely for Lost accounts
  6. 06Inbound Auto-Reply never replies about cancellation, pricing, legal, security, complaints or escalations
Security

Enterprise-grade from day one.

The answers your security reviewer asks for, before they ask.

Azure-hosted

Container Apps, Key Vault, Front Door. No long-lived cloud keys in the pipeline.

Tenant isolation

Enforced at the database layer. Cross-tenant access is architecturally impossible.

Field-level encryption

Pricing, renewal terms and commercial notes get a second layer on top of at-rest.

SOC 2-aligned controls

An 80-item internal control framework. Questionnaire and DPA on request.

Never trains shared models

Enterprise AI deployments in our own tenancy. Your data serves only your org.

Read-only where it matters

HubSpot, Stripe, Mixpanel and support data are read-only. Salesforce sync writes accounts back, and only when you connect it.

See the platform on your data.

Backed byMicrosoft for Startups