HubSpot use case library
Business problems, written as recipes.
A catalog of jobs teams actually run in HubSpot: the hubs, the tools, the build, and the point where native HubSpot stops. Written for admins, RevOps, and owners who need a straight answer.
Browse by function
Start from the team that owns the problem. Every card opens a set of recipes, not a feature list.
Pipeline, territories, partners
Deal desk, partner registration, and who owns the account.
Campaigns and events
Registration, follow-up, and attribution that sales will trust.
Tickets and renewals
Onboarding, success, and the handoff back into revenue.
The work around the CRM
Field jobs, orders, and the data other systems still own.
Start here
Eight recipes to open first.
Each one names the business problem, the HubSpot build, and the point where another system has to take over.
Partner and dealer portal
Let partners register deals without a full paid seat for every rep.
Subscription renewals
Custom objects and a deal that appears before the contract expires.
Franchise, one brand, many sites
A parent record, location records, and a view each franchisee can live in.
10 uses for manufacturers
RFQs, dealers, after-sales, and the jobs HubSpot should not pretend to run.
Event management, end to end
Registration, reminders, and a pipeline sales can see the next morning.
Territory assignment
What owner rotation can do, and when you need a real territory model.
Student admissions pipeline
Applications, counselors, and stages a university office will recognize.
Where outside tooling starts
Inventory, billing, payroll, and portals that HubSpot only fronts.
Industries with their own objects.
The CRM shape changes when the thing you sell is a unit, a campus place, a shipment, or a store.
Read a recipe in this order.
The collection names the job. The build level says how heavy it is. The limit says what HubSpot should only front.
Open a collection
Sales, marketing, service, or operations. Start from the team that owns the problem.
Check the build level
Native, native plus an app, or a custom build. The recipe says which one it is.
Name the outside system
Inventory, billing, payroll, and portals that HubSpot should not pretend to run.
The handoff the recipe has to name.
A build that stops at one team leaves the next team with a record they cannot use.
From campaign to pipeline
Registration and follow-up only count if sales can see the person the next morning.
From closed-won to the ticket
Onboarding and renewals need the deal, not a second copy of the account.
From the CRM back to the job
Field work and orders stay in the system that already owns them. HubSpot keeps the chase.
Inside every recipe
Problem, build, limit.
Every recipe answers the same questions, so you can compare two builds without sitting through a sales demo.
- Function, industry, and the hubs required
- Tier and complexity: native, native plus apps, or a custom build
- Tools, build steps, and the limitations in plain language
