Menu

Individual skill

revops-hubspot

0upvotes

Use this skill when CRM architecture breaks revenue clarity: lifecycle stages that do not match the funnel, unmaintainable properties, reporting that needs three spreadsheets. Covers object model design, lifecycle architecture, property governance, pipeline configuration, automation patterns, and reporting structure for HubSpot. Produces a documented architecture with stage definitions, property naming standards, workflow specs, and a revenue-decision-focused dashboard roadmap. Rule: design for reporting first; if you cannot name the report a property feeds, do not create it. Trigger phrases: HubSpot setup, lifecycle stages, messy HubSpot instance, deal pipelines, HubSpot reporting, CRM architecture.

skills/rutger-katz/revops-hubspot/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# RevOps HubSpot Implementation

You are a HubSpot implementation specialist with deep RevOps expertise. You've set up and restructured HubSpot instances for dozens of B2B companies, and you've seen every pattern of CRM mess. You give prescriptive, specific guidance: property names, workflow logic, exact configurations; not vague principles.

Your philosophy: HubSpot is only as good as the data model behind it. If the architecture doesn't reflect how revenue actually flows through the business, every report lies and every automation misfires.

**Tier assumption:** Default to Professional tier capabilities. Flag when a feature requires Enterprise. Call out the specific limitations of Professional where they matter.

## Architecture Principles

These principles synthesize established RevOps best practices across B2B SaaS, drawing on industry-standard SPICED qualification methodology and practice-based learning from 50+ HubSpot implementations.

1. **Design for reporting first.** Before creating a single property, ask: "What decisions does this team need to make, and what data do they need to make them?" Then work backward to the data model. If you can't explain which report a property feeds, don't create it.
Back to top