You celebrate every new customer. Who notices the ones quietly leaving?

Founder perspective. This Q&A was prepared from Ulaş Arslan's written brief and edited into interview form. It is not a transcript of a recorded conversation.

A new customer gets a Slack announcement. A renewal gets a calendar reminder, if somebody remembers to create one. That is the imbalance Ulaş Arslan wants founders to confront. His argument is deliberately uncomfortable: startups can become highly disciplined about winning customers while leaving the work of keeping them dependent on memory, scattered records and a person who is already overloaded.

Arslan is the founder of Sighub, the company behind Renewal Radar. His case for the product starts with a management question rather than a software category: when an existing customer approaches a decision about staying, does anyone have a clear next step? Here, his founder perspective is presented alongside the practical limits that a buyer should consider.

You celebrate every new customer. Who notices the ones quietly leaving?

That is exactly the question I want founders to ask. We put energy into acquisition because the result is visible. There is a new logo, a deal to mark won and something to announce. Keeping a customer is less theatrical. Somebody has to remember a commitment, follow up before the decision is already made and notice when an account has gone quiet.

My criticism is about priorities. A startup can know the status of every prospect and still struggle to tell you who owns the next conversation with an existing customer. If acquiring that customer mattered, the next decision they make should matter too. The work does not become less commercial just because the first invoice has already been paid.

Are you saying startups should stop chasing growth?

No. They need customers. I am saying the definition of growth becomes selective when we celebrate what comes in and barely inspect what might leave. A full acquisition pipeline does not answer whether existing customers are getting what they bought, whether unresolved problems have an owner or whether anyone has started the renewal conversation.

There is also a practical trap in telling a small team to simply care more. Caring is not a process. People can care deeply and still miss an account when the evidence is spread across several records. The useful question is what the team can reliably see and act on during an ordinary busy week, including the week when the usual owner is unavailable.

Why choose HubSpot for this?

Because HubSpot is a good place to run the customer relationship beyond the first sale. That is why I chose to build around it. The customer record should remain useful when the prospect becomes a customer. Bringing the commercial relationship and the follow-up together is more valuable than asking the team to remember another disconnected destination.

HubSpot provides the broader foundation. Its customer success offering brings account context, health monitoring, renewal visibility and outreach into the CRM. Renewal Radar is a focused addition to that environment. The proposition is to help teams use the customer information they already keep in HubSpot for one specific job: making renewal follow-up visible and owned.

If HubSpot is already good at retention, why does Renewal Radar exist?

A platform can support the work without every team having the same data arrangement or the same operating routine. A renewal date can sit in different places, and having a date somewhere is not the same as having a clear follow-up attached to it. I wanted to focus on that gap.

Renewal Radar's published scope is to resolve renewal timing from supported HubSpot records and identify eligible accounts without clear follow-up. The free scan is read-only. Ongoing paid monitoring can manage an owned follow-up task when its conditions are met. That is a specific operating job. It is not a claim that HubSpot is inadequate, and it is not a promise to solve every reason a customer might leave.

Is this just another dashboard telling founders they have a problem?

That would be a weak outcome. A report can be useful for understanding exposure, but the operating question is what happens afterward. Does a named person review the account? Is there a next step? Can the team distinguish a customer who already has a plan from one who still needs attention?

A queue becomes noise if it keeps surfacing the same account without acknowledging the work already underway. The principle I care about is that an account should lead to a clear piece of work. The customer still needs a human response that makes sense in their situation. Creating a task is the start of accountability, not proof that the relationship has improved.

What would you say to a founder who thinks retention can wait?

Ask who is making it wait. If it is a deliberate decision because there are only a few customers and the founder speaks with each of them, fine. If it is happening because nobody can confidently name the next step for existing accounts, that is a blind spot.

You do not need a complicated customer success department to take that question seriously. Start with the customers you already have. Know the relevant timing, know who owns the relationship and know the next action. If those basics are missing, spending more effort on acquisition does not make the missing work disappear. It only adds more relationships to the same operating system.

What should someone test before paying for Renewal Radar?

Whether the problem exists in their own portal. Start from evidence, not from my opinion. Look at which dates are being found, whether the account associations make sense and whether the reported follow-up gaps are real. If the existing HubSpot setup already produces a clean, owned queue, that is a perfectly good outcome.

Then test the work the product would create. An alert that a team cannot explain or use is not valuable merely because it is automated. The useful test is whether the right person sees a real gap early enough to do something about it. There should be no confusion between finding renewal exposure and claiming to have saved that revenue.

The challenge for founders

The sharpest part of Arslan's argument does not require buying his software: apply the same scrutiny to the next decision an existing customer makes as to the first decision a prospect makes. The suggested exercise is simple. Take the upcoming renewal list into the next revenue meeting and ask for the owner, evidence and next step on each account.

That exercise can produce uncomfortable answers. It can also show that the current process works. Either result is more useful than treating retention as a slogan. HubSpot can be the operating home for that work; whether a focused application is needed depends on the actual gap. The commercial test for Renewal Radar is narrower and more demanding than its founder's rhetoric: does it help the team consistently follow up on the right accounts?