Install the app
Add Native Intake in HubSpot and enter the dedicated settings surface rather than treating the product like a detached external form tool.
Install guide
Install Native Intake for one real workflow first.
This guide is for the current launch-state product posture: a narrow HubSpot rollout tied to one governed internal handoff, request, or record-update workflow.
- Use one HubSpot admin owner for the first install.
- Choose one source record type and one intended submission outcome before publish.
- Treat the first install as a pilot path, not a broad forms-platform rollout.
Install sequence
Follow the operating path the product is designed around.
Native Intake should be installed and introduced in the same order the product teaches on the site: install, configure, run, and verify.
Configure one intake path
Choose the record type, align the guided fields to the workflow, set one explicit intended outcome, and keep the first rollout inside the selected launch package limits.
Verify where it appears
Check publish state and runtime placement so the team knows exactly which records should show the intake before you introduce it more broadly.
Launch sequence visuals
Review the actual rollout path before you widen scope.
This page now uses the same public-safe storyboard sequence as the marketplace and homepage proof surfaces, so the install story reads as one governed operating path instead of disconnected instructions.
01
Install
Confirm the portal is connected, the app is installed, and the admin owner knows the next setup step.
02
Configure
Create one draft, choose one record type, and keep the intended submission outcome explicit before publish.
03
Run
Launch the live intake from the HubSpot record instead of sending teams to notes, side messages, or an external form.
04
Verify
Review publish state and placement before introducing the workflow to a wider team.
Launch package truth
Set package expectations before you widen rollout.
The first install should stay inside the same package definitions used on pricing, marketplace, and support surfaces so the admin is not forced to reinterpret limits after setup begins.
Free
$0
Best fit for one admin proving one repeatable workflow.
Documentation-first support
Growth
$39/month
Best fit for one SMB team standardizing several handoffs.
Standard support
Pro
$99/month
Best fit for lower mid-market, agency-managed, or higher-support rollout.
Priority triage and guided rollout support
After install
Use the first rollout to prove clarity, not breadth.
The first week with Native Intake should confirm that the configured path is understandable and supportable for the team using it.
Run one internal test on the target record type before wider rollout.
Confirm the workflow still fits one portal and the chosen package caps before adding more demand.
Document who owns edits to the intake configuration.
Use the trust docs when new stakeholders ask for broader claims than the launch state supports.
Disconnect and uninstall
Remove the app deliberately, not casually.
Because Native Intake governs a live request path inside HubSpot, disconnect and uninstall change how the team starts that work. Treat removal like a workflow decision, not just a technical cleanup step.
Uninstall or disconnect only after confirming which team currently depends on the intake path.
Treat removal as an operating change, not just a technical toggle, because the governed request path disappears with it.
If the customer is evaluating fit rather than expanding usage, prefer pausing rollout and documenting the outcome over silent removal.