Customer story

Sailer AI saved $97k in renewals with a month's warning

AI sales automation · BrazilB2B: automotive, education, e-commerce, insuranceAnnual contracts $18k–$60k
$45krenewal saved the week of the first alert
$52ksecond contract kept after a risk showed up 6 weeks out
4quietly cooling accounts found in the first 60 days
30–45 daysof warning before renewal

Context

Sailer AI is a fast-growing Brazilian sales automation platform. Its B2B customers are in automotive, education, e-commerce and insurance, on annual contracts from $18,000 to $60,000. The team tracked engagement and support numbers, but often found out a customer was unhappy only once they had started to pull away.

"We were growing fast, but some of our best customers were quietly drifting. By the time we noticed, we were playing defense instead of strengthening the relationship."
Vinícius Molina, CEO, Sailer AI

The problem

The warning signs were there, in three different places:

  • Product usage patterns lived in analytics dashboards no one checked daily.
  • Support problems sat in Zendesk, with no link to the renewal date.
  • The champion went quiet slowly, and nothing raised an alert.

Each looked minor on its own, and nobody saw all three at once.

"Our CRM said the account was healthy. Our support team said tickets were resolved. But no one saw that the champion had stopped responding to emails three weeks ago."
Vinícius Molina

What changed

Sailer AI connected Horizon to the tools it already used, without replacing anything. Horizon pulled product usage, support tickets and email onto each account, so the team could see when several warning signs showed up together.

Horizon · Signals · one accountIllustration of the account described
Usage down 40%Adoption · product usage
Adoption
Support ticket reopenedProduct · Zendesk
Product
Champion stopped replying 3 weeks agoRelationship · email
Relationship
Three warning signs on one account the CRM still showed as healthy, each with its source.
"The first alert we got was for a customer we thought was happy. Three signals had converged: usage down 40%, a reopened support ticket, and a champion who'd gone quiet. We reached out that week and saved a $45k renewal."
Vinícius Molina, CEO, Sailer AI

In the first 60 days, the team found 4 more accounts that looked fine in the CRM but were quietly cooling.

The outcome

A month's warningAt-risk accounts were flagged 30–45 days before renewal.
One picture per accountSupport, product and sales warning signs side by side.
Fewer last-minute rescuesRenewal talks started before the customer had decided.

In another case, falling usage plus an unresolved integration issue showed up 6 weeks before renewal. The team fixed it in time and kept a $52,000 annual contract.

What Horizon did, and didn't do

Didn't

  • Replace Zendesk, the CRM or the analytics tool
  • Talk to customers for the team
  • Make every renewal safe

Did

  • Put usage, tickets and email on one account
  • Flag risk 30–45 days before renewal
  • Give the team a reason to call that week
"For me, it was about confidence. Knowing that if something is drifting, I'll see it before it becomes a problem."
Vinícius Molina, CEO, Sailer AI

Takeaways

  1. Healthy in the CRM, slipping in three other systemsUsage, support and email each held part of the story.
  2. A month of warning was enoughBoth saves came from acting 30–45 days out.
  3. Act the week the warning signs line upSailer AI reached out the same week and kept the customer.

See which of your renewals are at risk.

A 30-minute call on a demo book, or on your own top 25 accounts.

Book a call