Permission-set design
Designed permission sets in collaboration with HubSpot as part of the global rollout.
Why it mattersAccess follows responsibilities, so each market works within the shared setup.
← Selected workRentokil Initial.
Global HubSpot operations
Rentokil Initial.
Global HubSpot rollout.
MarTech Admin and HubSpot expert, freelance, inside the global MarTech team for the HubSpot Enterprise rollout across markets.
50+countries in the programme
15+business units
3hubs: Sales, Service & Marketing
The challenge
Global consistency.
Local usability.
A multi-country rollout needs shared CRM rules while accommodating local commercial processes, service needs and external systems.
Local teams need pipelines and workflows that reflect their work. The global programme also needs consistent data definitions, integration rules and governance.
My role
From market requirements to HubSpot configuration
The role: define and implement processes with local markets across Sales Hub, Service Hub and Marketing Hub, and work with IT, data and compliance teams so each implementation is secure, scalable and adapted locally.
The working approach
How requirements become
configured processes.
A simplified view of the decisions behind a multi-market implementation.
Working across the platform
Explore HubSpot rollout & migration → These projects sit alongside service workflows, marketing communication and integration support, including connections to health portals, with local markets, HubSpot and internal IT, data and compliance teams involved throughout.
Examples from the engagement
Implementation work
inside the rollout.
Marketing contacts & core seats
Managed marketing contacts and supported the migration of user seats to core seats within the HubSpot setup.
Why it mattersLicences that match how each team actually uses HubSpot.
Migration between portals
Migrated data from a legacy HubSpot portal to the new portal with the MarTech team.
Why it mattersOne shared platform instead of a legacy setup running in parallel.
Sales pipelines & custom objects
Designed sales pipelines and configured custom objects to support the processes defined with local markets.
Why it mattersLocal processes represented without fragmenting the global data model.
Workflow centralization
Centralized HubSpot workflows within the shared platform setup.
Why it mattersFewer duplicated automations, with clear ownership of what runs.
External integrations & synchronization
Configured integrations and data synchronization between HubSpot and external systems, in collaboration with IT and data teams.
Why it mattersRecords that stay consistent between HubSpot and the systems markets rely on.
Advanced documentation
Documented the HubSpot configuration and workflows to support ongoing operations and handover.
Why it mattersA setup the next admin or market team can understand and maintain.
Start a conversation
What needs
to work better?
Describe the process that is causing friction, the teams involved and what needs to change. You do not need a technical brief to start the conversation.
- 01 I review your situation.
- 02 We discuss the scope and whether I can help.
- 03 You receive a proposal with clear next steps.
Based in Barcelona · Previously Paris and London