Skip to main content
Superhawk is only as good as the data it can see. Onboarding is mostly about connecting sources, then letting the first sync fill in your accounts.
1

Connect your CRM

Start here. Your CRM is where accounts, owners, contacts, deals, and renewal dates come from — without it, Superhawk has nothing to hang anything else on.Connect HubSpot or Salesforce
2

Connect your call recorder

Call transcripts are the single richest source Superhawk has. They drive health judgements, stakeholder maps, friction, adoption blockers, and most signals.Connect Gong or Fathom
3

Connect your support desk

Support volume, escalations, and ticket sentiment are strong early churn indicators.Connect Pylon
4

Connect product analytics or your warehouse

Usage is what turns “they seem quiet” into “contract creation is down 49% quarter on quarter”.PostHog · Amplitude · BigQuery
5

Define your feature catalog

Tell Superhawk what your product’s features and modules are, so usage can be read in your own vocabulary rather than raw event names.Feature catalog
6

Invite your team

Bring in the CSMs and account owners who will act on what Superhawk finds.Invite members
You do not need everything on day one. A CRM plus a call recorder is enough for Superhawk to start producing useful health reads and briefs. Each additional source makes the evidence stronger.

​
What happens after the first sync

Once sources are connected, Superhawk runs its first pass over your accounts. Depending on volume this takes anywhere from minutes to a few hours. When it settles you will have:
  • An account portfolio on Home, with health, ARR, owners, and renewal dates
  • Health verdicts on your CS accounts, each with the factors behind them
  • Signals raised where the evidence warrants it
  • Tasks drafted in your Inbox for the signals that need action
  • Briefs generated ahead of your upcoming customer meetings
Health, signals, and briefs improve over the first few weeks as Superhawk accumulates history. An account with two weeks of data will often come back as insufficient data rather than a health band, which is the correct answer rather than a failure.