Skip to content
Agentmart
Submit a tool

hubspot-setup

Set up HubSpot for B2B SaaS GTM — CRM configuration, deal pipelines, lifecycle stages, marketing automation, sequences, reporting dashboards, and enrichment…

Skill by LeadMagic

IndexedMIT★ 67
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/leadmagic-hubspot-setup

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Set up HubSpot for B2B SaaS GTM — CRM configuration, deal pipelines, lifecycle stages, marketing automation, sequences, reporting dashboards, and enrichment integration. Use when configuring HubSpot for sales, marketing, or revops. Triggers on: "HubSpot setup", "configure HubSpot", "HubSpot CRM", "HubSpot pipeline", "HubSpot marketing", or any HubSpot configuration request.

Use cases: data, marketing, sales

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found
Runs as
Python package

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/hubspot-setup

What's inside

Skill name
hubspot-setup
Description
Set up HubSpot for B2B SaaS GTM — CRM configuration, deal pipelines, lifecycle stages, marketing automation, sequences, reporting dashboards, and enrichment integration. Use when configuring HubSpot for sales, marketing, or revops. Triggers on: "HubSpot setup", "configure HubSpot", "HubSpot CRM", "HubSpot pipeline", "HubSpot marketing", or any HubSpot configuration request.
License
MIT
Compatibility
Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
Metadata
author: LeadMagic · version: 1.1.0 · category: automation
Instructions
135 lines in SKILL.md · view on GitHub

Before installing

  • Ships executable scripts

Files (4)

  • SKILL.md
  • framework-notes.md · references/
  • check-output.py · scripts/
  • output-template.md · templates/

SKILL.md (first lines)

# HubSpot Setup

## Overview

HubSpot is the most popular CRM for SMB and mid-market B2B SaaS. Its strength
is the unified platform: CRM, marketing, sales, and service in one system. Its
weakness is that it's easy to configure poorly and hard to fix later. This skill
covers setup for GTM teams: deal pipelines, lifecycle stages, marketing
automation, reporting, and enrichment integration.

## Authoritative Foundations
- **HubSpot Knowledge Base — Lifecycle stages** — Define entry criteria for each lifecycle stage and let stages move forward only, so funnel reporting stays trustworthy.
- **HubSpot Academy — CRM setup** — Configure objects, associations, properties, and pipelines before importing data or building workflows.
- **Winning by Design — Revenue Architecture** — Bowtie lifecycle model — align sales, marketing, and CS on stage-based outcomes.

## When to Use

- "Set up HubSpot for our sales team"
- "Configure HubSpot deal pipelines"
- "Set up HubSpot marketing automation"
- "Build HubSpot reports and dashboards"
- "Integrate enrichment with HubSpot"

## Step-by-Step Process

Load **crm-toolkit** first — confirm HubSpot fit (crm-selection), contacts-vs-leads
(HubSpot uses **Contacts only** — lifecycle stages replace Salesforce Leads), and
hubspot-blueprint (field and workflow catalog).

### Phase 1: CRM Foundation

**Contacts vs leads:** HubSpot has no Lead object. Inbound records are **Contacts**
with lifecycle stage = Lead until qualified. Do not duplicate records. See
**crm-toolkit** → contacts-vs-leads reference.

**Lifecycle stages:** Subscriber → Lead → MQL → SQL → Opportunity → Customer →
Evangelist. Define clear criteria for stage advancement. Never use "Other."

**Deal pipeline stages:** Customize per sales motion. Standard: New → Contact
Made → Discovery → Demo → Proposal → Negotiation → Closed Won / Closed Lost.
Each stage: required fields (Amount, Close Date, Next Step).

**Contact/Company properties:** Standardize naming. Add custom properties:
ICP fit score, enrichment status (pending/enriched/verified), lead source
detail, MEDDICC dimensions for enterprise.

### Phase 2: Marketing Hub

**Email marketing:** Lists by lifecycle stage. Sequences for nurture. Templates
with brand consistency. A/B testing on subject lines.

**Forms:** Embedded on website, pop-ups, landing pages. Map form fields to
contact properties. Auto-enrich on form fill via webhook to enrichment provider.

**Lead scoring:** HubSpot score based on fit (company properties) + engagement
(Page views, email clicks, form fills). Threshold: score >X triggers MQL.

### Phase 3: Sales Hub

**Sequences:** Automated email follow-up sequences. Personalization tokens.
Task creation for calls and LinkedIn touches. Unenroll on reply.

**Meeting scheduler:** HubSpot meetings integration. Round-robin or rep-specific.
Embed on website and in email signatures.

**Playbooks:** Guided selling for reps. Discovery questions, objection handling,
competitive positioning. Triggered by deal stage.

### Phase 4: Reporting

**Dashboards:** Sales (pipeline, forecast, rep activity), Marketing (traffic,
conversions, MQLs), RevOps (pipeline velocity, conversion rates, data health).

**Key reports:** Pipeline generation by source, MQL→SQL conversion rate, average
deal velocity by stage, win rate by source and rep, forecast accuracy.

### Phase 5: Enrichment Integration

**Clay → HubSpot:** One-direction push. Clay enriches, pushes to HubSpot.
Use clay_status property to gate: only verified records enter sequences.
Never two-way sync.

**LeadMagic integration:** Verify emails on form fill. Enrich companies on
contact create. Automate via webhook: webhook fires enrichment, results write
back to HubSpot properties.

## Output Format

HubSpot configuration document with: lifecycle stage definitions, deal pipeline
map, required fields per stage, marketing automation flows, dashboard specs,
and enrichment integration setup.

## Quality Check

- [ ] Lifecycle stages defined with clear advancement criteria
- [ ] Deal pipelines configured with required fields per stage
- [ ] Lead scoring model active (fit + engagement)
- [ ] Enrichment integration: one-direction push from Clay to HubSpot
- [ ] Dashboards built for all three functions (sales, marketing, revops)
- [ ] Data quality: no duplicate contacts, no missing required fields

## Common Pitfalls

1. **No stage criteria.** "We think they're an MQL" creates chaos. Define hard
   criteria: "ICP fit confirmed + demo requested = SQL."

2. **Too many required fields.** Reps skip CRM updates when every field is
   mandatory. Required: Amount, Close Date, Next Step. Everything else optional.

3. **Two-way sync with enrichment.** Clay-enriched data should flow to HubSpot,
   not back. Two-way sync creates data conflicts.

4. **Default HubSpot lifecycle stages.** Customize stages to your business.
   "Subscriber" and "Other" don't map to any real process.

5. **No data hygiene cadence.** Quarterly: deduplicate contacts, re-verify
   emails >90 days old, audit required fields completion.

## Execution Artifacts

From LeadMagic/gtm-skills, MIT.

More from LeadMagic/gtm-skills

Signals

Stars
67
Forks
18
Open issues
0
Last commit (this folder)
Oct 1, 2026 (29 days ago)
Last release
Oct 1, 2026 (29 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Version
1.1.0
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from LeadMagic

Cite this page

hubspot-setup skill. Agent Mart. https://agentmart.dev/skills/leadmagic-hubspot-setup (last updated 2026-10-24)