Frequently asked questions

Sighub is a renewal radar for HubSpot. It scans deals, line items, quotes, subscriptions and custom objects to find renewal timing scattered across HubSpot data, then turns each at-risk renewal into one self-resolving HubSpot task with the evidence attached.

RevOps and CS leaders running renewals inside HubSpot without a dedicated customer success platform. Typically B2B SaaS teams who own renewal revenue from HubSpot and need renewal timing surfaced and acted on before contracts slip.

Renewal dates rarely live in one clean Company field. They sit on deals, line items, quotes, subscriptions and custom objects. Workflows cannot fire on a date they cannot find. Sighub finds renewal timing across HubSpot objects, scopes to active customers, and creates one HubSpot task per real at-risk renewal.

HubSpot workflows need one clean renewal date field. Most portals do not have that. Workflows also create task debt: the task stays open forever. Sighub reads renewal timing across many HubSpot objects, keeps one task per real risk, self-closes it when the risk clears, scopes to active customers, and checks whether action is already happening before creating a task.

No. Sighub uses deterministic, auditable rules over HubSpot metadata. No black-box AI, no health score, no churn prediction model. Every alert shows the evidence behind it.

No. Sighub never reads email bodies, note content, call recordings, meeting notes or ticket content. It uses metadata only: timestamps, direction, status, dates, amounts, ownership.

None of the above. Sighub is a narrow renewal radar that lives on the HubSpot company record. It does not replace HubSpot, it does not give you another screen to check, and it is not a customer success platform.

Yes. You can connect HubSpot and run a renewal exposure scan for free, with no payment. The free scan gives you the full exposure report, a downloadable PDF, an optional shareable read-only report link, and a manual rescan about once a week. It is read-only and never creates HubSpot tasks or runs daily monitoring.

The Team plan is €99 per portal, per month. It adds daily monitoring of your active customers, one self-resolving HubSpot task per high-urgency renewal risk, the full triage view, and renewed-vs-lost outcome tracking. One subscription covers one HubSpot portal.

Yes. The Partner plan is €399 per month and covers up to 10 client portals, with white-label exposure reports and support for running renewal audits as a service. It is arranged with the Sighub team — use the "Talk to us" button in the pricing section or email info@sighub.io.

Yes. Activating monitoring and task automation needs an active subscription (the Team plan). If your portal is not subscribed, clicking Activate sends you to checkout first. The free scan and PDF stay available whether or not you subscribe.

Checkout and billing are handled by Stripe. You subscribe from the Sighub settings panel (or the scan page), and manage everything — update your card, view invoices, or cancel — through the billing portal, reachable from "Manage billing" in the Sighub settings.

Monitoring pauses: daily scans stop and Sighub stops creating or updating tasks for that portal, and the settings panel shows a "Monitoring paused" notice. HubSpot tasks Sighub already created stay in your account, and your Sighub configuration and risk snapshots are kept. Update your billing or resubscribe to resume. The free scan stays available the whole time.

Click the install link on the Sighub website. You'll be redirected to HubSpot's OAuth consent screen to authorize access. After authorizing, a success page confirms the connection and tells you to open HubSpot Companies to find the Sighub card.

Sometimes. After installing, the Sighub card may not appear in the Company sidebar automatically. Go to any Company record, click "Customize tabs" on the sidebar, and add the Sighub card to your layout.

No custom property is required to complete setup. However, to detect renewal timing risk, you should map a Company date property that represents contract end or renewal date. To display value at risk, you can optionally map a numeric Company value property (ARR, ACV, etc.). Both are optional, skipping them reduces detection accuracy but does not prevent Sighub from working.

Sighub cannot evaluate renewal timing without a mapped contract end date. It operates in engagement-only mode: it monitors email replies, meetings, contact activity, and ticket status, but does not know when a renewal is approaching. If a contract end date property is mapped but the value is empty on a specific company, Sighub uses engagement-only evaluation for that company while other companies with the field populated are still evaluated for renewal timing.

Sighub scans your Company property names and types for common keywords like contract, renewal, subscription, ARR, MRR, or ACV. Suggestions are based on property names only, not on data quality or sample values.

If the saved mapping no longer matches an existing property, Sighub treats it as unmapped at runtime. The settings UI may show a warning that the previous mapping is unavailable. You can remap to a different property.

30, 60, or 90 days before contract end. The default is 60 days. This controls when Sighub starts evaluating renewal risk for each company.

Yes. During setup Sighub detects candidate renewal sources across Company date fields, deals, deal pipelines, line items, quotes, and contract- or subscription-style custom objects, each with a coverage and confidence label, and selects the best one. You can confirm it, switch to another detected source, or rescan. You also set a fallback for accounts with no renewal date (keep watching renewal timing, or engagement-only) and a default contract term used to estimate a renewal window from a closed-won deal.

In the settings panel you can set the renewal alert window (30/60/90 days), the engagement reply-staleness window (default 28 days, range 15–90), the engagement high and critical day counts, and the open-ticket threshold. The 14-day high-severity renewal cutoff and the 30-day post-expiry grace period are fixed.

You choose during setup: either the Company owner (default) or one specific HubSpot user for all companies. If no owner is available, the task is created without an assignee.

No. Sighub complements HubSpot workflows by focusing on renewal risk signals and owned follow-up tasks. HubSpot workflows are useful for clear rules and predictable automation. Sighub helps when renewal risk forms through weaker signals across engagement, timing, ownership, and stale follow-up. Compare Sighub with HubSpot workflows

Sighub evaluates two types of risk using deterministic rules applied to HubSpot metadata: 1. Renewal Risk, the contract end date is within the configured renewal window (or overdue), and certain conditions are met (e.g., no meeting scheduled before renewal, contract nearly or already expired). 2. Engagement Risk, communication signals have slowed or stopped, based on inbound email replies, meeting activity, contact activity, and ticket status. Renewal risk takes priority when both could apply. If neither signal fires, the company is marked healthy.

Critical (most urgent): the renewal is overdue, within about 7 days with no recent customer contact, or a renewal deal was closed-lost. High: within 14 days, or within 30 days with no meeting scheduled before the renewal date. Medium: within the configured window with a mitigating sign (a booked meeting, an advancing renewal deal, or recent contact), or simply further out. High and critical risks create tasks; medium risks do not.

When no contract end date exists: combinations of no activity for 30+ days, no inbound reply for 30+ days, no future meeting, or 3+ open tickets, all evaluated against whether recent activity (last 14 days) is present. When a contract date exists but renewal risk is not active: engagement risk fires when there is no recent activity, the inbound reply is stale, and there is no future meeting.

Sighub tracks: inbound email replies (by metadata, not content), meeting timestamps, contact last activity dates, logged call dates on the Company, and open ticket counts. It does not read email bodies, notes, call recordings, or ticket content.

Yes. Sighub checks for associated meetings using HubSpot timestamps. A "future meeting" is any meeting with a timestamp in the future. "Meeting before renewal" means a meeting scheduled between now and the contract end date. Meeting content and outcomes are not evaluated.

Yes. An inbound reply is an associated email whose direction is INBOUND/INCOMING, or whose status indicates REPLY while direction is not OUTBOUND. Sighub reads timestamps and direction metadata, never the email body.

No. The current system is entirely deterministic rules applied to HubSpot metadata. There is no AI, machine learning, sentiment analysis, NLP, or churn prediction model.

Yes. On the Sighub card you can snooze a risk for 14 days, mark an account healthy for 90 days, or record a Renewed or Lost outcome. Recording an outcome also completes the open Sighub task. Every control can be undone from the card.

Tasks are created only after you explicitly click "Activate" in the settings panel (which needs an active subscription). Before activation, Sighub runs in summary mode: it scans and stores snapshots but does not create tasks. After activation, tasks are created for high-urgency risks only — severity high or critical, for renewal and engagement risks alike. Medium risks remain visible in the Sighub card and triage view without generating tasks.

Every subject starts with "Sighub:" followed by the action: "Sighub: Schedule renewal meeting", "Sighub: Follow up on no response", "Sighub: Escalate renewal risk", or "Sighub: Reactivate account engagement". The task body names the action, gives a one-line summary, lists up to four evidence lines, and links to the Company record.

Sighub automatically completes the associated task. If the risk changes type (e.g., from renewal to engagement), it completes the old task and creates a new one if the new state is task-eligible.

If the same high or critical risk is still active on the next scan, Sighub can create a new task. Completing a task does not clear the underlying risk, it only closes the task.

If the same risk state remains unchanged, Sighub currently does not recreate the deleted task. This is a known limitation.

A background scheduler checks every 60 minutes and runs a full portal scan when the last completed scan was at least 23 hours ago. You can also trigger a scan by refreshing the Sighub card, opening the settings panel, or using the manual scan option in settings. Sighub is not real-time, there are no CRM object webhooks.

There is no one-click pause for the whole portal. Canceling your subscription pauses monitoring and task automation (existing tasks stay in HubSpot). Per account, you can snooze a risk, mark it healthy, or exclude the account from monitoring on the Sighub card or triage view.

Yes. The Sighub settings panel has a triage view: one list of every flagged account, with the reason, value at risk, owner, and renewal date, plus links to the Company record and the open task. You can filter by severity and signal, sort, and record Renewed or Lost straight from a row. The full, continuously updated triage view comes with the Team plan; the free scan shows a one-off snapshot.

Every connected portal gets a renewal exposure report at its own scan link. It shows where renewal timing lives in your HubSpot data, how much value renews inside the window, how many renewals are already overdue, and the most exposed accounts. It is read-only and you can download it as a PDF.

Yes. You can turn on a read-only report link from the Sighub settings panel to forward to a budget owner, or for an agency to put in front of a client. It opens with no login, is not indexed by search engines, and is rendered live from current data. Sharing is off by default and revocable — turning it off disables the link, and turning it back on creates a new link, so the old one stops working.

The triage view sums up Protected ARR (all monitored accounts), At-Risk ARR (flagged accounts), Renewing-Soon ARR (next 60 days), and Retained ARR (accounts marked Renewed in the last 90 days). It also tracks a rolling 90-day view of flagged, actioned, renewed, and lost accounts.

Yes. The Snooze 14d button on the Sighub card suppresses the risk for 14 days. The card shows "Snoozed until [date]". The snooze expires by itself, or you can end it early with Remove snooze.

It overrides the risk decision and treats the account as healthy for 90 days. The card shows "Marked healthy until [date]". You can end it early with Restore automation.

The account is treated as healthy for the next 90 days and the open Sighub task is completed. The risk can surface again at the next renewal cycle.

The account is excluded from monitoring and the open Sighub task is completed. The card shows "Excluded from monitoring". You can bring it back with Re-include account.

No. Controls are stored in Sighub, not written to your CRM records. The only HubSpot change is that recording a Renewed or Lost outcome completes the open Sighub task.

Company properties (name, owner, currency, mapped fields), email metadata (timestamps, direction, status), meeting timestamps, ticket status (open/closed), contact activity timestamps, deal amounts and currencies, and Company logged call dates. Sighub does not read email content, note bodies, call recordings, meeting notes, or ticket content.

Portal configuration (mapped properties, renewal window, owner routing), encrypted HubSpot tokens (AES-256-GCM), and one risk snapshot per company (company name, signal type, severity, evidence strings, value at risk, owner name, task status, timestamps). Sighub does not store raw HubSpot content.

No. Sighub does not use AI and does not use customer data for training any model.

All stored Sighub data (configuration, tokens, risk snapshots) is deleted. HubSpot tasks previously created by Sighub are not removed, they remain in your HubSpot account.

Tokens are automatically refreshed before expiry. If refresh fails or HubSpot returns repeated authentication errors, the portal is marked as requiring reauthorization. Scanning pauses for that portal until you reconnect via the Sighub settings.

Sighub handles missing data gracefully: no contract end date means engagement-only mode; no Company value means Deal fallback; no Deal value means amount is not displayed; no owner means tasks are created unassigned. Companies with no data at all are skipped.

If live signal data is unavailable (e.g., HubSpot API issue), Sighub preserves the last confirmed active risk state and adds evidence noting which sources were unavailable. It does not treat missing data as negative evidence.

First from a mapped Company value property (requires valid numeric value + Company hs_currency_code). If unavailable, Sighub falls back to one associated Deal with a valid amount and currency. The per-account value at risk is shown in its original currency. When your portal uses multiple currencies, the portfolio ARR totals in the triage view are converted into your HubSpot home currency using your own HubSpot exchange rates; if the optional currency access isn't granted, they fall back to your most common currency.

Sighub requires Company, Deal, and Ticket objects, which are available on HubSpot Starter and above.