See the risk. Price the renewal. Grow the revenue.
Signals shows which accounts are at risk and why: it owns the four inputs to a health score (product usage, support history, survey feedback and relationship quality) and collects all four itself, where most platforms buy three of them in. Renewal Desk builds the offer, takes it through approval and records the outcome that lands in your net revenue retention. Revenue Book holds every change in ARR and the NRR and GRR it adds up to. All three run on the Shared Platform: one customer record, three engines, Touchpoints and Mira.
Nobody trusts a health score they cannot check.
When the working behind a score sits in four systems the CSM cannot open, they rebuild it by hand before every renewal, and a churn percentage that names no model and no confidence figure cannot be weighed at all.
Five stages, start to finish.
Signals reads your sources and scores each account against your settings. It ranks the book and hands the work to the person allowed to act on it.
Signals reads your warehouse, your support desk, your meetings and email, and our survey engine.
Signals turns every source into one comparable reading per account. That gives you a trend.
You set the components, weights and thresholds. Four components are computed, one is the CSM's judgment, and all five show beside the score.
The churn model ranks the whole book and shows its confidence, its factors, the ARR at stake and its version on every row.
Work goes to the person allowed to do it. Anything above their permission level goes up a level.
Nobody files a status update. A CSM works the account and their VP watches the book.
Five components, weighted the way you decide.
You own the components, the weights and the thresholds. Four components are computed from your data: adoption, engagement, support and sentiment. The fifth is the CSM's own assessment, weighted like the others and shown as its own row, so their read stays visible. A second human input, finance's risk flag, comes off after the weighted sum rather than inside it.
Four computed components, then the CSM’s own read at thirty-five, carrying fifteen percent like support and sentiment. The bracketed figure on each row is its share of the composite. Check it: 38×.35 + 35×.20 + 38×.15 + 70×.15 + 35×.15 = 41.75, shown as 42.
Two human inputs, both on the record.
The CSM’s assessment is a weighted component, shown as its own row. Finance’s risk flag is a deduction: a person your administrator has authorized flags the account, a penalty you set comes off the calculated score once, and the flag carries who set it, when, and the reason if it is cleared. Both are a person’s judgment, and the score shows them as one.
Every prediction shows its working.
| Probability and tier | Ranked across the whole book |
| Confidence | A confidence figure on every row |
| Contributing factors | Named, with the evidence behind each |
| ARR exposed | Attached to the risk when it is raised |
| Model version and run | Named and timestamped on the page |
The page says what the prediction is for: deciding what to work on first, not declaring a customer lost.
From signal to decision.
Your CRM stays your system of record. Signals adds the path from the event to the person who needs to know about it. Each path runs inside one product. Built from separate tools, each one is an integration you maintain.
On the roadmap
When onboarding completes in Engagements, the project survey fires and a crediting rule will calculate the CS bonus. The question engine already runs on the Shared Platform. The incentive engine and onboarding as a project (Engagements) are future releases.
The customer decides. Everything here serves that.
The renewal decision belongs to your customer, who is not in your system. Everything in Renewal Desk exists to build the best offer and take it to them. Two steps, Price and Renew, on the same record Signals wrote to, with no handoff in the middle.
Build the offer from what you already know.
The inputs are what Signals knows about the account and what the customer said on the calls. Renewal Desk builds the offer from the subscription lines you already hold. Nobody prices from a blank quote.
Health, risks, usage and the churn ranking come across from Signals. Meeting Intelligence adds what the customer raised on the calls: objections, sentiment, and the commitments on both sides, each with an owner and a due date.
You start from the current subscription lines and reprice, add or remove. Quotes follow from the plan, versioned. Proposals, agreements and SOWs come from templates you control, with a clause library behind them. Renewal Desk checks every line against the floor price in your price books.
An approver signs off before the offer leaves. Who approved it, and when, stays on the record. A line under the floor shows on the quote before anyone approves it.
Take it to the customer, with the calls on the record.
The negotiation happens in meetings and email. Renewal Desk records the calls, pulls out what was decided and what was objected to, and keeps the renewal's stage and forecast category where the whole team sees them. The CRO reads the renewals by stage, forecast category and owner without asking anyone to write it up.
Ferent Recorder joins the call and transcribes it. Gong and uploaded transcripts come in beside it. Meeting Intelligence pulls the decisions, objections, actions and follow-ups out of each round. In the negotiation itself, Mira proposes the next lever, what to get in return, the approval it needs and where the floor is.
Every renewal sits at a stage, 180 Days down to 30 Days, then Negotiation, Renewed or Churned, with a probability on each. Its owner sets the forecast category: Committed, Likely, Pipeline, At Risk or Excluded. Expansion that Signals found is priced beside the renewal it belongs to. The subscription lines are the ones in your CRM, with the contract behind them.
Once enough of a customer's renewals have closed, the next one will show what was offered, what was conceded and what landed last time. Being built; not shipping today.
What each renewal did to ARR.
Revenue Book is where the CFO and the CRO read what each outcome did to ARR. A customer success lead reads it for the accounts they own. It answers three questions: where we are, what moved us, and who moved us. Every outcome lands as an ARR movement: New Business, Expansion, Contraction, Churn or Renewal.
Ferent records every account's ARR each business day, so the book can be read as it stood on any past date and compared with another. NRR, GRR and logo retention are reported for the trailing twelve months, or for any period you choose, and each figure comes with the same figure from the period before. Every amount keeps its own currency and that day's rate to your reporting currency, so old ARR is never restated at today's rate.
The bridge takes ARR from the opening figure to the closing figure through each kind of movement, new business, expansion, contraction and churn, by period and by month. Every figure traces back to the movements behind it, and each movement to its account and its contract. A Renewal keeps ARR where it was and is never counted as growth. If the movements don't add up to the ARR in your CRM, the gap is on the screen.
Revenue Book names the accounts that added the most ARR in the period and the accounts that lost the most, with the movements behind each one. It also looks ahead: it shows the ARR up for renewal in each of the next twelve months, split by the health score Signals gives each account, so the CFO can see how much ARR is at risk next quarter and in which accounts.
Where the parts meet.
Signals scores the health behind a renewal, Renewal Desk builds and closes it, and Revenue Book records what it did to ARR.
Nobody rekeyed anything or wrote a report.
Thirteen skills, in four kinds.
Mira is the assistant on the Shared Platform, and she reads the account through your own role and field permissions. Thirteen skills ship with Portfolio today, in four kinds. Four prepare and run a renewal negotiation. Three plan an account and write to the customer. Two find the customer’s own evidence in calls and email, and four analyze a meeting after it happens. You write your own beside them, in plain words, and turn any of them on or off. Mira has her own section on the Shared Platform page.
That boundary, the row-level isolation under it, and who else touches your data are all on one page rather than scattered through the product pages.
Everything in Portfolio.
Three parts of one product, on the Shared Platform every customer gets. Each name below is a screen in the product.
Customer 360, Product Usage, Support Intelligence, Surveys and NPS, Meeting Intelligence, Meeting capture.
Customer Health, Churn Intelligence, Customer Risks, Priority, Segmentation, Stakeholder roles.
Success Plans, Playbooks, Onboarding (progress and satisfaction; running it as a project is Engagements, a future release), AI Digest, Mira.
Product Opportunities, Dashboards, Feedback record, Lifecycle handoffs, Survey delivery, Audit trail.
Renewal plan, Quotes, Proposals, agreements and SOWs, Commitments, Approval.
Renewal stages, Forecast categories, Opportunities, Subscriptions, Negotiation evidence.
ARR movements, daily ARR history, the bridge as a waterfall, top movers, renewal exposure, Revenue Intelligence.
The customer record, the three engines, Touchpoints and Mira, described on the Shared Platform page.
Every name in this list ships today
If you sell to businesses and have 50 or more customer accounts on renewable contracts, we should talk.
Bring your hardest account.
We will pull up its health score and go through the components with you. Forty-five minutes on your data.