1.0 - Introduction
Your packages are built using the services you’ve created in HighGround. Think of a package as a bundle of protections you offer to your clients. A package can contain just one service or multiple services, depending on how you want to structure your offering. There’s no strict limit.
It also doesn’t matter what type of service you’re working with. Both Managed IT and Security services can be added to packages, allowing you to create solutions that reflect how you actually deliver support and protection to your clients. This flexibility makes it easy to build packages that match different client needs, industries, or risk profiles.
To learn more about services please read our Creating & Understanding your services article.
2.0 - Creating a Package
When you first sign in to HighGround and complete the onboarding flow, we’ll automatically create a few starter packages for you. These are there to help get the ball rolling and give you a starting point for structuring your service offerings.
Of course, most MSPs will want to tailor things to match how they actually deliver services. When you're ready to create your own packages, here’s how it works.
Choosing Your Package Type
When you click Add Package, the first step is deciding what type of package you want to create. HighGround gives you two options:
Standard Package
A generic package that can be applied across multiple clients. This is ideal for your core offerings - for example, a Standard IT Support Package or a Managed Security Bundle that you offer to most customers.
Custom Package
A package built specifically for a single client. Custom packages can only be applied to the client they are created for, making them perfect when a client has unique requirements or needs a tailored service bundle.
Once you select the package type, you’ll be taken to the Package Details screen.
Configuring Your Package Details
This is where you configure the core settings for your package, including:
Package Name – The name that will appear in HighGround and in proposals.
Pricing Model – How the package will be billed.
Price – The base price for the package.
Contract Term – The duration of the agreement linked to this package.
Setting these details early helps ensure your packages are consistent, clear, and ready to be applied to clients.
Pricing Models in HighGround
HighGround supports two pricing models when creating packages:
Package Pricing – Minimum Units
This model allows you to set a minimum number of units that must be billed for the package.
Asset Pricing – Minimum Revenue
This model focuses on ensuring a minimum level of revenue, regardless of the asset count.
Depending on the pricing model you choose, you’ll see a Minimum Counts field appear. This field allows you to define your minimum billing threshold, but it’s completely optional - you can leave it blank if you don’t need to enforce a minimum.
Defining Contract Terms
On the same screen, you’ll also see the Contract Section, where you can define the contract terms associated with the package. This allows you to set things like contract length and agreement conditions directly at the package level.
Note: Contract terms defined at the package level will override any contract terms attached to individual services that are added to the package later.
This ensures that the package behaves as a single, consistent offering, rather than inheriting potentially conflicting contract settings from the services inside it.
3.0 - Build your Package
Now it’s time to build your actual package.
Packages in HighGround are made up of services, and you can include any type of service you’ve created. This flexibility allows you to combine your Managed IT and security offerings into a single, structured solution that reflects how you deliver protection and support to your clients.
Note: If a service has the “I will not sell this service on its own” option selected, it cannot be used in a Per Asset package.
Service Categories
When building your package, you’ll see your services organised into two sections:
Managed IT Services
Security Services
This layout makes it easier to quickly locate the services you want to include and helps keep your package balanced between operational IT support and security protections.
Reviewing Service Details
When you add a service to a package, its details will appear on the right-hand side of the screen. This preview allows you to quickly review the service before finalising your package.
This is particularly helpful when you’re working with multiple services, as it lets you double-check the details without leaving the package builder, reducing the risk of configuration mistakes later on.
It’s important to note that services cannot be edited from within the package builder. If you need to make any changes to a service, you’ll need to do this in the Services module.
Removing or Reviewing Services
If you need to adjust your package while building it, you can easily manage the services you’ve added:
Remove a service by clicking the “X” at the end of the service row.
View the service details again by clicking on the service.
This allows you to quickly refine your package until it reflects the exact combination of services you want to deliver to your clients.
4.0 - Relationship between Packages, Services, Products and your Stack
The image below demonstrates the relationship between Packages, Services, products and your stack.
