Annual-to-Monthly Contract Conversion
Led a data-driven shift of roughly 1,000 customers from year-long to monthly evergreen contracts, using SalesRabbit's own retention data to win unanimous buy-in and cutting refund volume dramatically in the process.
Problem
By late 2025, SalesRabbit's Growth team was already spending a majority of its time manually moving customers off annual contracts and onto monthly ones — one at a time, racing each customer's renewal date. When they didn't finish in time, the customer would wake up to a surprise invoice for the following year paid upfront, often north of $10,000, and Support and CS would spend the next few days fielding the fallout. The company had effectively already found its own fix; it just hadn't been allowed to apply it systematically.
The underlying data backed up what Growth already knew from experience: customers on monthly billing stayed past 12 months about 80% of the time, while annual customers canceled before renewal roughly half the time.
Approach
Mickey, as Director of Revenue Operations, coordinated a cross-functional effort spanning Ops, Marketing, CS/Growth, and Finance to convert roughly 1,000 customers still on annual plans. Serious conversations started in late 2025; a minimum 30-day customer notice period began going out in January 2026; and the actual conversion process began in February 2026.
He personally owned the subscription conversion itself, making sure each customer's existing MRR and discounts carried over unchanged rather than repricing anyone as part of the switch.
Marketing communicated the change to affected customers ahead of time during the January notice period, giving them a window to raise concerns — essentially no one did. CS, Growth, and Finance built the internal business case and drove urgency, framing the change around customers being better served on monthly billing rather than as a cash-flow play.
All but the top 50 enterprise accounts were converted automatically, with an opt-out available that no customer used.
Conversions were timed to happen at each customer's renewal rather than mid-contract — operationally simpler, avoided prorated credits, and kept invoice and subscription history clean.
Technical depth
- Tray handled the actual subscription update, triggered by an Ordway webhook.
- Rather than building a separate conversion process, the mechanism leaned on Ordway's existing auto-renew behavior: let the annual subscription auto-renew as scheduled, have that renewal event fire a Tray workflow via webhook, then immediately update the subscription to monthly through the Ordway API.
- The customer only ever saw the new monthly invoice — never the annual one it had briefly renewed into.
Outcome
Refund requests either stopped entirely or dropped roughly 12x in size when they still occurred, since customers were no longer disputing a full year's charge at once.
Retention data confirmed the bet behind the project: about 80% of monthly customers stayed past 12 months, versus about 50% of annual customers canceling before renewal.
Billing had been the #2 most common support ticket category for a long stretch. The exact before/after change in ticket volume isn't known — that's a genuine open question rather than an estimate — but the conversion removed the single most common source of that category: the surprise annual renewal invoice.
Finance's initial pushback centered on MRR predictability and cash flow. The counter-argument that won unanimous buy-in had three parts: MRR was already expected to shift at renewal regardless, since customers commonly adjusted seat counts at that time anyway; the conversion itself preserved the same monthly rate as the prior annual plan, so it introduced no new pricing change or MRR impact on its own; and the company was routinely losing chargebacks on the refund volume the old model generated, so reducing that refund burden — in both count and dollar amount — was worth the theoretical cash-flow trade-off, which may have been somewhat illusory anyway given how refund-prone the annual-prepayment model already was.
Every team ended up aligned on this change — a notably clean internal sell, in contrast to the friction the self-registration project faced getting buy-in from Sales (see that case study elsewhere on this site).