Documentation
BaseCommand Documentation
Getting-started guide, agent reference, connector 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 the BaseCommand Suite.
Sign up and connect your CRM
Create your BaseCommand account and connect your CRM via OAuth. The connection flow is a quick OAuth, with no credentials shared with BaseCommand. For HubSpot-specific connector details, see the connectors page.
BaseCommand reads your CRM as-is
No migration or field cleanup required. BaseCommand resolves a coherent renewal view from whatever shape your data is in, including stitching deals back to companies when the association is missing.
Map your existing fields (optional)
If your CRM already has renewal-tracking properties, the setup wizard at agent.basecommand.ai lets you map them so BaseCommand reads your fields instead of computing from scratch.
Your first agent run
Background producers run across your whole book and compute health, risk, and renewal timing from what you have. The next morning, your Inbox has drafted moves ready to review.
Review and release
Open the Suite at agent.basecommand.ai and approve or adjust each drafted move. Nothing reaches a customer until you release it.
Reference
Topic-organized index of everything you might need.
Getting started
- Sign up & connect your CRM
New-customer flow: account, payment method, CRM connector.
- Setup wizard→
Property-mapping interface inside the Suite. External link.
- Pricing & fair-use
Plan tiers, fair-use envelope, and how billing works.
Agent reference
- Live agent demos
Run any live agent on sample data and see the exact output it drafts.
- 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.
CRM connector
- CRM connectors
Supported connectors and how to connect your CRM.
- 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.companies.write | Write bc_expansion_* values to the company record and associate user-approved tasks, notes, and logged emails to the company. Every write is user-click-gated. |
| crm.objects.contacts.read | Read stakeholder data for multi-thread depth signals. |
| crm.objects.contacts.write | Associate user-approved tasks, notes, and logged emails to the relevant contact (engagements link to contacts and companies). |
| 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 the deal object on first install. |
| crm.schemas.companies.read | Read company property catalog before provisioning expansion-related properties. |
| crm.schemas.companies.write | Create the BaseCommand bc_expansion_* property group on the company object so writeback has a destination. |
| crm.lists.read | Check for an existing BaseCommand static list before creating one (idempotent). |
| crm.lists.write | Create the "BaseCommand: Expansion plays in progress" static list and add companies to it via the user-initiated "Add to list" action. |
| automation | Read existing HubSpot workflows for renewal-tier detection and provision renewal automations in Premium mode (via /automation/v4/flows). |
| 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.