Pricing
Early accessWhat it costs, and what actually drives the number
A per-named-technician subscription with every module included and no charge for client users, plus a one-off implementation quoted stage by stage before it starts. This page explains how that works and what moves it, because a headline figure with an asterisk helps nobody.
- Per technician, all modules
- Implementation fixed per stage
- 01234 672 617
The model
Two numbers, both of them written down
One recurring, one one-off. Everything else is either included or not needed.
- 01 · Recurring
Subscription, per named user
Monthly or annual, with every module, the API, UK hosting, backups, updates and support included. It scales by the number of people who actually log in - not by turnover, transaction volume or how many modules you happen to use.
Annual is cheaper. Increases are capped and notified in writing.
- 02 · One-off
Implementation, fixed per stage
Discovery, configuration, data migration, training and go-live, each quoted as a fixed price before it starts. You approve each stage knowing what it costs, and you can stop after discovery with a usable document and no further obligation.
Typically the larger of the two numbers in year one, and the one worth scrutinising.
Included
Things other suppliers charge extra for
This list exists because these are the six lines that most commonly appear on somebody else’s renewal invoice as a surprise.
Every module
All 11 modules are in the base product. There is no service-desk edition, no advanced reporting tier and no knowledge add-on - you get the whole system and switch on what you use.
API and webhooks
The documented REST API and webhook system are included, with no per-connector licence and no integration platform fee. If you want your data somewhere else, that is your right, not an upsell.
Security and audit
Role-based permissions to field level, approval limits, single sign-on and a full audit log. None of it is reserved for an enterprise contract.
Updates and hosting
UK hosting, encrypted off-site backups and continuous versioned updates. No forklift upgrade project every three years and no separate hosting invoice.
UK support
Support from the people who built the platform, with a named contact and agreed response times. Not a ticket queue in a different timezone.
Your data, exportable
A full export in open formats whenever you ask, including if you leave. There is no commercial advantage in holding a customer’s data hostage and we do not design as though there is.
What moves the number
Five variables, in the order they usually matter
If a supplier can quote you before knowing these, they are quoting the software and hoping you do not ask about the rest.
Named technicians, not headcount
You pay for the people who log in to do the work. Client users invited to a shared project board or a service review are not charged for - charging per client seat is how portals end up empty, and an empty portal helps nobody.
How much data has to move
Migrating clients, contacts, sites and a service catalogue is straightforward. Migrating ten years of ticket history, contracts in three formats and a renewals book that lives in somebody’s workbook is not. This is usually the single biggest variable in implementation.
How many processes are unusual
Configuration is included in implementation. Bespoke development (a commercial model nobody else uses, a client-specific reporting requirement, a bespoke integration) is quoted separately and only when we agree it is actually needed.
How many systems it has to talk to
Microsoft 365 and a mainstream RMM are standard. A chain of integrations across an unusual RMM, a legacy billing platform and a bespoke provisioning tool is a project in its own right, and we would rather say so at the quote stage.
Trading entities and training groups
Providers running several trading entities, or several offices that need separate training days, need more configuration and more on-site time. The software cost barely moves; the implementation cost does.
What you are paying for
The five stages, quoted individually
You approve each one before it starts. Nothing begins on the assumption that you will agree to it later.
Discovery
A structured session mapping how you run now - the PSA you have outgrown, the spreadsheet of renewals, the shared mailbox that is really your ticket queue, and the review deck somebody rebuilds by hand every six months. We come back with what the platform covers as standard and what needs building.
Configuration
Your service catalogue, ticket taxonomy, boards, roles, approval limits and review templates set up to match how you actually work - not a demo tenant with your logo dropped on it. Your categories, not ours.
Data migration
Clients, contacts, sites, services, renewal dates and enough ticket history to make the knowledgebase and similar-incident retrieval useful on day one. An empty AI is a useless AI, so the history matters more here than in most migrations.
Training & rollout
Role-based training - the service desk learns logging and resolution, account managers learn reviews and renewals, directors learn the reporting. We usually pilot with one technician and one client before opening it up.
Ongoing support
UK support from the people who built the platform and use it themselves, with a named contact, agreed response times, and a roadmap you can influence. Being a small vendor is an advantage here and we intend to keep it.
Early access
CubeMSP is in early access, so we are onboarding a limited number of businesses at a time. In practice that means direct access to the people building it, real influence over the roadmap, and pricing fixed for the first term. It also means we will tell you plainly if something you need is not built yet rather than putting it on a slide.
Ask about early accessQuestions
The ones people are slightly reluctant to ask
Because a per-user figure on its own would be misleading. Implementation is usually a larger first-year number than the subscription, and it varies enormously with data quality and how many processes are unusual. We give a written quote covering both after a single conversation, and we do not need three qualification calls to produce it.
A monthly or annual per-named-user subscription with every module included. Annual is cheaper. There is no minimum term beyond the first year, and price increases are capped and notified in writing rather than applied at renewal and explained afterwards.
It is quoted as a fixed price per stage - discovery, configuration, data migration, training and go-live - before any of it starts. If a stage turns out to be larger than scoped, we tell you before doing the work rather than presenting it on an invoice.
Hosting, backups, updates, the API, security features and standard support are all in the subscription. Not included: bespoke development, additional on-site training days beyond the agreed plan, and third-party licences you already pay for, such as your accounts package.
For a provider in the five-to-fifty-technician range, usually yes - largely because the licensing is simpler, there are no tiers to climb and the implementation is smaller. For a large provider needing fifteen years of accumulated functional depth, one of the established platforms may suit you better, and we would tell you so.
You add technicians. The modules, the API and the support model do not change, so there is no threshold at which the system reclassifies you as an enterprise customer and the number changes shape.
Yes, and most providers do. Starting with clients, services and renewals and moving the service desk across a month or two later is a configuration change, not a second purchase - which is a large part of why the pricing is not module-based.
Pricing
Get a written quote after one conversation
Tell us roughly how many users, how many sites and what you are running now. We will come back with both numbers in writing - and if we think you would be better served elsewhere, we will say that instead.