Climb GTM Console — documentation
The console is the operating surface of Climb's revenue-operations engagements: pipeline, forecast, funnel, data hygiene, and the engagement readout, computed from a daily read-only scan of your CRM and judged against thresholds your GTM profile sets — every bar prints its source, so you can argue with it.
How it connects to your CRM — three lanes, one job each
- The scan (read-only, weekday schedule): reads deals, companies, and lifecycle data to compute every metric. It cannot write.
- Name resolution (read-only): our systems store CRM record ids, never names; names are fetched from your CRM only at display time.
- Your edits (per-user): updating a deal from Forecast uses your own HubSpot login via the "Climb GTM Console" app — scoped to deals read/write only, no contacts. Each save also leaves a note on the deal recording who changed what.
Pages
- Overview — the attention list, ranked, each row clicking through to where you act on it.
- Forecast — coverage per stream (new business and expansion judged on their own bars, never blended), scenario band, and inline deal editing.
- Funnel — lifecycle stages with conversion and median days between them; click a stage to inspect it; sources normalized.
- Hygiene — verdicts framed as value protected: duplicates ready to merge, deals nobody can reach, past-due close dates, off-team deals.
- Readout — the engagement's questions answered with numbers, including lift measured from a baseline pinned when your CRM converged to the standard — never before.
Data handling
Read-only toward your CRM (except edits you make yourself), ids at rest with names resolved at the glass, tokens encrypted, every read scoped by database-level security. The full statement is the privacy policy.