Directions: Ofri Avivi Renewals Operator Interview
Source: raw/meetings/Directions w_ Ofri Avivi (2026-06-16 12.00).txt
Summary
The team interviewed ofri-avivi, Renewal Manager at cymulate, to understand renewals as a concrete sub-workflow inside the account-management-vertical. Ofri described a role that sits between Customer Success, sales/account managers, technical AMs, support, partners, and customer decision makers. The strongest insight: renewal work is mostly pre-call investigation and internal coordination, not the customer meeting itself. Dashboards help, but they often miss the “real story” that CS knows: whether the customer sees value, has resources to act, or is drifting toward churn.
Key takeaways
- Renewals is a distinct AM/CS workflow. Cymulate created the Renewal Manager role after existing customers and renewals were falling between CS and account managers. Ofri sees the role as essential in a license/retention business because Customer Success does not fully own the commercial renewal.
- The renewal manager is the connector. Ofri connects CS, support, sales/AM, technical AMs, product context, procurement, CISOs/CIOs, and sometimes channel partners before renewal.
- Prep dominates the job. The customer meeting, email, quote, and phone call are small compared with the preparation: checking who is up for renewal, usage/admin signals, failed runs, agent status, support tickets, unresolved technical issues, and CS sentiment before contacting the decision maker.
- Customer-health dashboards are necessary but insufficient. A BI tool can show that usage and technical signals look healthy, while CS knows the customer sees no new value, lacks resources to remediate findings, or is preparing to consolidate vendors.
- Timing is the highest-leverage variable. Cymulate works roughly 90 days before renewal, but Ofri noted that six months can be better because tenders, vendor review, low usage, and unresolved issues are often impossible to fix in three months.
- Onboarding/adoption is a renewal problem. Weak handoff from sales to CS and slow adoption can surface a year later as a first-renewal failure: “what did we get from this product?” Ofri specifically called the sale-to-adoption transition an Achilles heel.
- Regional operating models differ. Israeli renewals rely heavily on personal relationships, phone/WhatsApp timing, and direct CISO/CIO contact. Europe/APAC are more partner/distributor-driven; the renewal manager may never directly discuss commercial terms with the decision maker.
- Scale depends on automation plus technical depth. Ofri manages roughly 90-120 Israeli accounts depending on multi-year renewals. She thinks more coverage is possible if data, reminders, and technical answers are automated, but a renewal manager also needs enough technical confidence to answer decision-maker questions without always pulling in CS.
Decisions
- No product or vertical decision was made.
Action items
- (none captured)
Open questions
- Is “renewal-risk cockpit” a sharper first wedge than broad AM productivity?
- Who is the buyer for a renewals workflow: VP CS, CRO, RevOps, renewal-management lead, or regional sales leadership?
- Can a product reconcile hard telemetry with the qualitative CS story well enough to be trusted before renewal?
- Does the first product need to be verticalized by industry, e.g. cybersecurity SaaS, because the renewal conversation gets technical?
- Should the product optimize 90-day renewal prep, six-month early-warning coverage, or full post-sale adoption from day 1?