Implementation starts with understanding the business. Establish what HubSpot needs to support, involve the people who know the work, understand the relevant systems and data, and agree a roadmap before delivery begins.

Define what the business needs.

Start with the work HubSpot needs to support. Describe the process today, where it causes difficulty and what you want people to be able to do differently. This gives configuration decisions a reason beyond matching a feature list.

Choose specific examples to discuss in discovery. For an enquiry handover, that could mean establishing who receives it, what information they need and what should happen if the usual owner is unavailable. These are illustrative questions, not a standard implementation package.

  • Which processes need to be supported first?
  • What information do people need to do the work?
  • What would demonstrate that the new setup is working?

Bring stakeholders into discovery.

Include the people doing the work, those responsible for the outcome and anyone who needs to approve changes. Their knowledge will help identify exceptions, dependencies and practical constraints before they become configuration questions.

At Aventine, discovery can include stakeholder workshops online or in person, together with relevant system audits. The aim is to build shared context around the people, processes, assets, systems and data involved.

Bring a real example

A recent enquiry, handover or reporting question often gives a more useful starting point than a general description of the process.

Understand the systems and data.

Identify where relevant information lives, who maintains it and which systems need to keep working together. Agree what should move, what should stay where it is and where an ongoing connection may be needed. These are different requirements and should be scoped accordingly.

If the plan includes importing data, establish the records and fields involved and check the current import requirements before preparing files. HubSpot’s documentation covers file structure, property values and technical limits; the details depend on the import and, in some cases, the subscription.

HubSpot: format import files

  • Who can explain the data and its current use?
  • Which information is needed for the agreed process?
  • Which systems and teams depend on that information?

Agree the work ahead.

Turn discovery into a documented plan. Distinguish quick wins from focused tasks and phases of work, and make the order of delivery understandable. Record the decisions and dependencies that need to be resolved along the way.

You review and sign off the roadmap before Aventine begins delivery. Scope and time are agreed together. The setup and onboarding then follow that agreed work, with opportunities to check the result against the business needs identified at the start.

Before sign-off

Check that the plan makes clear what is being delivered, which decisions are still open and how the team will review the setup.

The takeaway

A shared plan gives delivery direction.

Discovery, a documented roadmap and client sign-off connect the business need to the work that follows.

Related service

Explore how discovery, the roadmap, setup and onboarding fit together in our implementation approach.

Explore implementation & onboarding