We built the tool Cameron needed at his last SaaS job
By 2024, Cameron Wells had watched the same sequence play out a dozen times from the CS side of a B2B SaaS company in Austin: a customer goes quiet, the billing attempt fails, no one connects the dots, and the churn shows up in the monthly post-mortem. He built Renewharbor to be the tool that connects those dots before the window closes.
Why Cameron built this
Cameron ran customer success at a B2B SaaS company in Austin through 2024. His team tracked renewals manually — a shared spreadsheet, a mix of alerts from the billing system, and a gut sense of which accounts felt quiet. The system worked until it didn't.
One quarter, three accounts churned within the same renewal window. All three had login frequency that had dropped sharply 3–4 weeks out. All three had open support tickets. One had a failed card that nobody had followed up on. None of those signals had been connected to the renewal date in a way that put a call on anyone's calendar.
Cameron spent a few months in early 2025 building the internal tool he wished had existed — something that read billing data, CRM activity, and support queue age, and assembled them into a daily list of accounts that needed a call before the renewal invoice ran. He launched Renewharbor publicly in October 2025.
We are not a health scoring platform. We are not a CSM workflow tool. We are the specific thing that tells you which accounts are about to churn, three signals at a time, before the window closes.
Discover churn after the customer cancels. Review what went wrong. Update the spreadsheet. Repeat.
See the login gap, the failed card, the open ticket — two weeks before renewal. Act before the customer decides to leave.
Three principles we don't compromise on
Signals before dashboards
We show you the three signals that map to a renewal action, not a wall of health score charts. If a metric on the screen doesn't tell you who to call or what to fix, it shouldn't be on the screen.
Act before the cancellation
Renewharbor is not a reporting tool — it is a daily queue that exists because your CS team has a finite number of calls they can make each week. We make sure the right accounts get called before the renewal invoice runs, not after the cancellation email arrives.
Priced by accounts, not seats
Churn prevention requires the whole revenue team in the same room: CS, finance, RevOps. We price by the number of accounts you track. Your CSMs, your VP Finance, and your RevOps lead all see the same queue — no per-seat math when you're trying to protect ARR.
Small team, deep focus
We're a three-person team based in Austin, TX, entirely focused on the SaaS renewal problem.
Cameron Wells
Former CS lead at a B2B SaaS company in Austin. Spent years watching churn get discovered in monthly post-mortems — three weeks after the signals were visible. Founded Renewharbor in 2025 to build the queue that makes those calls happen in time.
Priya Sundar
Built billing and CRM integrations at two early-stage SaaS companies before joining Renewharbor. Responsible for the connectors that read subscription events, renewal dates, and payment history from Stripe, Chargebee, Salesforce, and HubSpot.
Marcus Obi
Six years running CS at SaaS companies from 80 to 600 tracked accounts. Shapes the queue UX and the recommended-action playbooks — the part of the product that tells your CSM not just that an account is at risk, but what to do about it today.