A HubSpot CRM quick start is the minimum viable structure for a growing team: pipelines that match how deals actually move, a short list of required properties, clear ownership, and permissions that stop accidental deletes — enough discipline to trust the data without burying reps in admin.
1. Start from the sales process, not the default pipeline
Open a blank note and write how a deal actually moves from first touch to closed-won. Ignore HubSpot’s default stages for five minutes. Then map each real step to a pipeline stage.
- Name stages after buyer progress (e.g. Qualified, Demo done, Proposal sent) — not internal busywork
- One primary pipeline for core revenue; add a second only if the motion is truly different
- Define exit criteria for each stage in one sentence (what must be true to advance)
- Archive unused default stages so they stop polluting reports
2. Properties: only what decisions need
Every custom property is a tax on every form, import, and sync. Keep a short list of fields that change routing, forecasting, or reporting — and make those required at the right moment.
- Lifecycle stage — aligned with marketing and sales handoff definitions
- Lead source / original source — for attribution that leadership already believes
- Deal amount + close date — required before proposal stages
- Owner — always set; never “Unassigned” in active pipelines
- 2–4 ICP fields max (segment, region, product interest) — not a census form
3. Permissions that match how you work
Start strict on delete/merge, open on edit for owners. Growing teams usually need: reps edit their records, managers see the team, ops admins own pipelines and properties.
- Separate Super Admin from day-to-day sales users
- Limit who can create pipelines and custom properties
- Use teams for visibility if you sell by territory or product line
- Document who owns HubSpot changes — one named owner beats a shared login
4. First automations (keep them boring)
- Assign owner on create when source/region is known
- Create a task when a deal sits in a stage past its SLA
- Notify Slack (or email) only for high-signal events — not every property change
- Block stage moves that skip exit criteria if your process is mature enough
If you haven’t mapped the process yet, skip clever automation. Automating confusion just makes confusion faster.
5. Go-live checklist
- Import cleaned contacts/companies/deals — or start fresh if history is unusable
- Train on stage exit criteria, not on clicking every HubSpot feature
- Pick 3 dashboards: pipeline, activity by owner, and conversion by stage
- Schedule a 30-day hygiene review (duplicates, blank owners, stuck deals)
Done well, HubSpot becomes the system of record for revenue — not a graveyard of half-filled forms. Start narrow, enforce a few rules hard, and expand only when the team asks for the next field.