Object scope visible Outcome stated Publish state visible
Rollout pricing dossier
Pricing
Price the first governed rollout, not the whole org chart.
Native Intake is priced by live intakes and usage, not by seats. Start with one workflow, then move up only when more teams or more volume are actually live.
- 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.
How to choose
Pick the plan that matches your first rollout, not the broadest future idea.
Most teams should start with one workflow they can describe clearly, review with the right admin, and prove in production. That keeps the buying decision understandable for the people who will own the rollout.
- Free is the narrowest proof lane for one workflow.
- Growth is the default SMB lane once several repeatable handoffs are real.
- Pro is for lower-mid-market or agency-managed rollouts needing higher support.
Plans
Three lanes keep the buying decision legible.
Each plan is built to answer one question: how much live usage is real today, and how much support will the rollout need?
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.
- Documentation-first support
Growth
Run the default SMB setup.
$39/month
For SMB teams that already know the product fits and want several live intake paths for recurring internal handoffs in one HubSpot portal.
- Up to 5 active intakes
- 500 submissions per month
- 1 HubSpot portal
- Best fit for one SMB team standardizing several handoffs.
- Standard support
Pro
Support a broader guided rollout.
$99/month
For lower-mid-market teams and agency-managed rollouts that need more live workflows, more monthly volume, and a higher-touch support lane.
- Up to 15 active intakes
- 2,000 submissions per month
- 1 HubSpot portal by default
- Best fit for lower mid-market, agency-managed, or higher-support rollout.
- Priority triage and guided rollout support
How pricing works
Price the operational footprint, not the org chart.
The pricing model stays tied to what an admin can count and support: published intakes, monthly submissions, and one installed portal.
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.
Trust page
Review the launch-safe trust boundary
See what Native Intake is and is not claiming publicly today, how admins stay in control, and why the launch path remains demo-led.
Read the trust pageGuided walkthrough
Bring one workflow for a pricing and fit review
Use the demo path if you want help deciding which plan matches the first process and what rollout complexity the team actually has.
Request the walkthrough