Renewal Radar Is Live in the HubSpot Marketplace: Here Is What Changes

Before the listing, installing Renewal Radar depended on a direct link and a conversation with Sighub. The Marketplace makes the product independently discoverable.

A HubSpot user can now evaluate the integration where they already evaluate other HubSpot apps. The listing shows the use case, data shared between the systems, pricing, setup documentation, support route, and the install button. That reduces ambiguity for a team deciding whether the app fits its portal and gives every installation the same starting point.

The listing is available here: Renewal Radar by Sighub in the HubSpot Marketplace.

HubSpot manually reviews an app's Marketplace listing against its published listing requirements. Those requirements cover areas such as a distinct use case, OAuth as the authorisation method, active production installs, only the scopes the app needs, accurate shared-data information, public setup documentation, clear pricing, support information, and a functioning installation route.

That matters because a listed app is not only marketing copy on an external website. The public description, permissions, setup flow, and support commitments have to line up with the app users actually install.

This should not be described as technical approval, certification, or an endorsement of Renewal Radar's business logic. The distinction is explained separately in What HubSpot Marketplace Review Means for Sighub. The live listing means public availability after that listing review.

It does not mean HubSpot has technically approved or certified the product, endorsed its claims, audited every line of business logic, validated its risk decisions, or guaranteed accuracy, stability, or outcomes. Renewal data is messy by nature. One account stores the contract date on a deal, another on a line item, another on a custom object. Historical deals, stale properties, and unusual lifecycle models can still create ambiguity.

The responsible product standard is therefore not "Marketplace listed, so the output must be right." It is "the app has a legitimate public distribution route, and every result still needs explainable evidence." Renewal Radar shows why a company surfaced, which date and value it used, and which risk evidence supported the decision. When the data is too weak, the product should hold back rather than manufacture certainty.

Sighub is the company. Renewal Radar is the first product. Keeping those identities separate was deliberate: the product should be easy to understand as one narrow action layer for HubSpot renewals, while Sighub can grow into a broader company around signals that exist in CRM data but fail to become timely action.

The Marketplace listing strengthens that separation. Teams search for and install Renewal Radar because they need renewal risk detection. They learn that Sighub is the builder and operator behind it. Search engines and AI systems also gain a consistent public connection between the company, the product, the use case, and the official HubSpot ecosystem listing.

Going live changes the main question. The challenge is no longer whether Renewal Radar can be distributed as a HubSpot app. The challenge is whether teams trust the output enough to act on it every week.

That means faster first scans for large portals, stronger reconciliation of historical and active renewal dates, clearer confidence when the source is inferred, and fewer tasks created from stale data. No new dashboard and no feature expansion for its own sake. The product gets better by becoming quicker and more dependable at the one job it is already listed to do: catch renewals that need attention before missed follow-up becomes lost revenue.