Documentation
BaseCommand Documentation
Install guide, agent reference, integration details, and the Renewal Operations Standard. Most setup work happens inside the BaseCommand Suite at agent.basecommand.ai — this page links you to the right place for each task.
Quickstart
Five steps, about 5 minutes end to end. Most of the work is one-time setup; daily use lives inside HubSpot and the Suite.
Install from the HubSpot Marketplace
Authorize the BaseCommand HubSpot app from the marketplace listing. The OAuth flow takes about 30 seconds.
Provision the Renewal Operations Standard
BaseCommand creates ~24 namespaced bc_* properties on your deal and company objects. Idempotent — existing properties are never overwritten.
Map your existing fields (optional)
If your portal already has renewal-tracking properties, the setup wizard at agent.basecommand.ai/setup-preview lets you map them so we write to your fields instead of ours.
Watch the first writeback land
Within ~1 minute, risk tier, forecast bucket, and the recommended save play appear on every open deal in your portfolio.
Open the Suite for deeper work
Visit agent.basecommand.ai to run forecasts, generate QBRs, draft outreach, and pull board-ready NRR reports.
Reference
Topic-organized index of everything you might need.
Getting started
- Sign up & connect HubSpot
New-customer flow: account, payment method, HubSpot OAuth.
- Setup wizard→
Property-mapping interface inside the Suite. External link.
- Pricing & fair-use
Plan tiers, fair-use envelope, billing relationship with agent.ai.
Agent reference
- Full agent catalog
All 23 Premium agents across the four fleets, with descriptions and tier metadata.
- What is Renewal Intelligence?
The category we belong to and why it exists.
- Use cases by role
Renewal Leader, CSM, AE — what each role typically runs.
HubSpot integration
- Security & data handling
OAuth scopes, sub-processors, retention, and the sandbox evaluation path.
- OAuth scopes reference
Per-scope justification (see below).
- Writeback & freeze-on-edit
How agent values land on records and what happens when you override them (see below).
Comparisons
- Comparison overview
Where BaseCommand fits relative to other CS and renewal tools.
- vs HubSpot Customer Success Workspace
How we complement Workspace rather than replace it.
- vs Breeze Customer Agent
Where BaseCommand and Breeze overlap and where they don't.
- vs Gainsight
For teams considering a CS platform vs an intelligence layer.
Account & legal
- Privacy policy
Data we collect, sub-processors, your rights, and retention.
- Terms of service
The legal agreement governing use of the service.
- Support & contact
How to reach us, response-time expectations, status.
OAuth scopes reference
The scopes BaseCommand requests when you install the HubSpot app, and exactly what each is used for.
| Scope | Used for |
|---|---|
| crm.objects.deals.read | Read deal records to score renewal risk, forecast GRR/NRR, and surface deal-level recommendations. |
| crm.objects.deals.write | Write bc_risk_tier, bc_forecast_bucket, and bc_save_play back to the deal so they display on the record and are usable in views/reports/workflows. |
| crm.objects.companies.read | Read company context for portfolio health and Expansion Intelligence. |
| crm.objects.contacts.read | Read stakeholder data for multi-thread depth signals. |
| crm.schemas.deals.read | Read existing deal property catalog before provisioning (idempotent install). |
| crm.schemas.deals.write | Create the BaseCommand Renewal Operations Standard property group on first install. |
| crm.schemas.companies.read | Read company property catalog before provisioning expansion-related properties. |
| crm.schemas.contacts.read | Read contact property catalog for stakeholder-mapping features in the Suite. |
| sales-email-read | Read email engagement metadata (timestamps, direction) to compute "days since last touch". We do not read email body content. |
| oauth | Required to authenticate the user via HubSpot OAuth. |
Writeback & freeze-on-edit
When you enable writeback, BaseCommand writes computed values onto your HubSpot records as native properties — so they show on the record page and are usable everywhere HubSpot supports properties (views, reports, workflows).
What gets written
- bc_risk_tier — Low / Medium / High / Critical, computed from activity recency, stakeholder depth, and deal context.
- bc_forecast_bucket — Commit / Best Case / Worst Case / Omitted, based on stage, activity, and proximity to renewal date.
- bc_save_play — A one-line recommendation derived from the risk drivers and renewal proximity.
- bc_expansion_play_type, bc_expansion_estimate, bc_expansion_signal — written to company records by Expansion Scout.
How freeze-on-edit works
BaseCommand respects your edits. If you (or another tool) modify a BaseCommand-managed property after we wrote to it, we mark that property as frozenand stop overwriting it. The freeze lifts automatically when the deal's stage changes — signaling that the situation has shifted enough that the prior override may no longer apply.
You can audit writeback activity from the Suite under Settings → Writeback log.
Can't find what you need?
Email help@basecommand.aiwith the question and we'll respond within one business day. Most documentation gaps get patched within 48 hours of being raised.