Start with one workflow. Pay more only when the usage is real.
Native Intake is priced for teams standardizing internal HubSpot
handoffs, not for seat count. Choose the plan that matches how many
live intake paths you need and how much rollout support your team
expects.
Use the exact launch caps on every customer-facing surface.
Keep one subscription mapped to one installed HubSpot portal.
Do not imply broader workflow automation, ticketing breadth, or unlimited scale.
Each package is designed to help a buyer qualify fit and rollout
shape without implying a broad forms-platform footprint. The point
is a cleaner buying decision, not feature inflation.
Free
Start with one live workflow.
$0
For a team proving that one repeatable internal request should move out of notes, side messages, or manual edits and into a cleaner in-record path.
1 active intake
50 submissions per month
1 HubSpot portal
Best fit for one admin proving one repeatable workflow.
One object scopeOne stated outcomePublish state visible
Why the packaging stays narrow
The commercial model matches a visible rollout surface.
Native Intake pricing works because the product itself stays legible:
one governed intake path, one portal boundary, and one visible publish
model. The package story should feel like an extension of what the
admin can actually see and control in settings.
Package limits map to published intake paths, not seats or abstract usage claims.
Growth discussion starts after the first operational workflow is real.
The visual system keeps pricing tied to product truth instead of SaaS theater.
How pricing works
Price the operational footprint, not the org chart.
The pricing logic is designed to stay understandable for SMB buyers and
commercially defensible against broad low-cost internal forms tools.
Active intake
A published intake that can be used in the live portal
Count only published intakes that are available for real use in the installed HubSpot portal.
Submission
One successful intake submission counted at the portal level in a calendar month
Count successful submissions against the installed portal's monthly total rather than per user or per form draft.
Portal
One installed HubSpot account
Launch packaging assumes one subscription maps to one installed HubSpot portal by default.
Buyer self-qualification
Start where the first workflow is easiest to prove.
Use these lanes to place your team quickly instead of forcing a
premature install decision or a vague enterprise conversation.
Start on Free for one painful handoff, one admin, and one workflow to prove.
Move to Growth when one operating team needs several repeatable requests.
Use Pro for lower mid-market, agency-managed, or higher-support rollout.
That keeps the commercial story aligned with the narrow operational wedge
the product is actually selling.
FAQ
Answer the buying questions directly.
What exactly counts toward the package limits?
An active intake is a published intake that can be used in the live
portal. A submission is one successful intake submission counted at
the portal level in a calendar month. A portal means one installed
HubSpot account.
Is Native Intake priced per seat?
No. Native Intake is priced around active intake paths, monthly
operational volume, and rollout complexity. Seat-based pricing is
the wrong mental model for this product wedge.
Can a buyer start free today?
Yes, the Free plan is positioned as the entry point for one real
workflow. Buyers who want help qualifying fit, rollout scope, or
support expectations should start with the walkthrough before they
expand beyond that first use case.
Why not undercut broader form builders on price?
The commercial strategy is to look more native, more trustworthy,
and more specific for operational handoffs, not cheaper. A race to
the bottom would blur the wedge and invite commodity comparisons too
early.
Who should request a guided conversation first?
Agencies, implementation partners, multi-team buyers, and anyone
unsure whether their workflow fits the current launch scope should
start with the guided conversation.
Continue evaluation
Resolve trust and fit before the rollout gets broader.
Pricing closes the package question. The remaining pages help a
careful buyer understand scope, rollout posture, and whether the
product fits the workflow they want to standardize.