Who takes part, and when
| Role | What they do | Typical time |
|---|---|---|
| Project owner (RevOps or Sales Ops) | Weekly check-in, decisions, approvals | 2 to 4 hours per week |
| Sales leader (CRO or VP Sales) | Process and reporting workshop, sign-off on stages and dashboards | 2 to 3 sessions |
| Super user | Joins build sessions, gets deeper training, supports the team after launch | 2 to 3 hours per week |
| Sales managers and 1 or 2 reps | Process workshop, testing before go-live | 2 to 3 sessions |
| Marketing | Lead handoff and lifecycle stages, if Marketing Hub is in scope | 1 to 2 sessions |
| IT | System access, security review, integrations, data exports | As needed |
| All users | Role-based training | 60 to 90 minutes per session |
These are typical minimums. The real time depends on the project, and we agree on it at the start.
What we do and what your team does
We:
- Analyse your sales process and design the setup.
- Build pipelines, properties, automations, integrations and reports.
- Clean, map and migrate your data.
- Prepare training and documentation.
Your team:
- Explains how you sell today and where it breaks.
- Decides on stages, exit criteria and what leadership needs to see.
- Tests the setup and checks the test import.
- Takes part in training.
Why the super user matters
The super user keeps HubSpot working after the project ends. They answer daily questions, add users and make small changes. Choose someone who knows how your team sells and has time for the role. This is often a sales operations specialist or a senior rep.
Where projects slow down
- Decisions wait for people who were not in the workshops.
- Nobody has access to export data from the current system.
- The scope changes in the middle of the project.
- The super user has no time set aside for the project.
Next step
See how we train teams on the Team Enablement & Training page, or book a call.
Related answers: How long does a HubSpot implementation take? · Why isn’t our team using HubSpot?
