The operating system for post-sales.

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

See exactly where an account stalled.

A two-lane timeline shows stage and sub-stage for every account - onboarding, adoption, value realisation, renewal, expansion - with the expected duration against the actual. Stalls light up before they become churn.

• Six stages with their own sub-stages, from onboarding through to churned
• Escalation is not a linear step - an account can drop in from anywhere and recover out
• Clynto only ever suggests a transition; you accept or dismiss it
• A dismissed suggestion is never re-surfaced

Nineteen 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 agent and per segment
• A full audit trail carrying the reasoning behind each decision
• Build custom agents without code, and test them against historical accounts

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

The accounts too small for a CSM, covered anyway.

Your longtail still churns and still expands - it just never gets a human. Segment thresholds decide which accounts qualify, and per-segment tiers let agents act freely there while staying approval-gated on your strategic book. The seeded workflows already route longtail branches through Playbook Executor and Escalation Handler, so the "let it run itself on the small accounts" pattern is set up out of the box.

• Segment thresholds you set once, from ARR - Strategic, Core, Longtail
• Agents run fully autonomous on longtail while staying notify-only on strategic
• Playbook Executor drives each sequence one step at a time
• Escalation Handler is the circuit-breaker when a sequence stalls instead of looping

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