Run the whole MSP from one system.

CubeMSP is UK-built software for managed service providers who have outgrown a shared mailbox and a renewals spreadsheet. Clients, services and renewals, project work and time, the service desk, knowledge, integrations and governed AI in one place - built by an MSP that runs on it.

  • You can see the client whole
  • The same fix stops being re-derived
  • Margin you can actually see
yourcompany.cubemsp.co.uk/
Search clients, tickets…UA

Morning, User A

Tuesday 12 May · service desk · 3 on shift

Open service desk records

38

3 breaching

Recurring revenue

£47.2k

per month

Renewals, 30 days

9

2 unconfirmed

Unbilled time

26h

this month

Needs a decisionView all
  • INC-4182Company ASLA breach in 40 minBreaching
  • REQ-4190Company BAwaiting client approvalWith client
  • INC-4193Company CContract expired 30 AprOverdue
  • REQ-4196Company DReady to closeResolved
  • 20+

    Years in IT

    Crushed Ice has supported UK businesses since 2003

  • 1

    System, not five

    CRM, services, projects, tickets and reviews on one model

  • UK

    Hosted on AWS

    Hosted in the UK on AWS, with UK support

  • 0

    Per-seat portal charges

    Invite as many client users to a board as you like

Sound familiar?

Nobody replaces a working system. They replace one that has quietly stopped working.

These are the problems we hear about most often. Tick the ones that are true - once it reaches three, the problem is no longer the spreadsheet.

0/ 8

Tick the ones that are true of you today.

Read the full diagnostic guide

What CubeMSP is

One database, no re-keying

Clients, contacts and sites, service and subscription tracking, shared project boards, incident logging, an AI-assisted knowledgebase and branded client reviews - one platform, one data model, built by an MSP.

  1. One record per client, with every contact, every site, every address and every piece of history attached. Multi-site clients are modelled properly rather than being three separate records that nobody remembers to keep in step.

    More on this module
  2. Prospects, opportunities, forecast value and expected close date in the same place as the clients they turn into. When you win, nothing is retyped - the prospect record becomes the client record.

    More on this module
  3. Every licence, circuit, backup, firewall, hosted mailbox and support contract you supply, with quantity, unit cost, sell price, term and renewal date. The thing MSPs most often run in a spreadsheet, and most often get wrong.

    More on this module
  4. A dated view of what is coming up for renewal, what it costs you, what you charge for it, and what the margin actually is. Renewals stop being a surprise and start being a diary entry with a number next to it.

    More on this module
  5. Log an incident against a client, a site, a service and a category, with priority, assignee, notes and time entries. Full history on the client record, so the tenth time a problem recurs it is visible as a pattern rather than a coincidence.

    More on this module
  6. Time booked against the incident or task it was actually spent on, billable or not, at the rate that applies. What a client costs to support stops being a feeling and becomes a figure.

    More on this module
  7. Kanban boards for migrations, rollouts and onboardings, with columns, categories, assignees and dependencies. Boards can be shared with the client, with internal-only tasks and comments filtered on the server rather than hidden in the interface.

    More on this module
  8. Resolved incidents are drafted into knowledgebase articles for a human to approve. Semantic search over your own history surfaces the last three times this happened and what fixed it - so the fix is found rather than re-derived.

    More on this module
  9. Branded quarterly and annual reviews assembled from the period’s real data: tickets raised and resolved, response times, projects delivered, services supplied, spend and renewals due. Every figure is computed, then narrated - never estimated by a language model.

    More on this module
  10. Live dashboards by role - service desk load, project status, renewal exposure, client profitability - and scheduled reports that arrive in an inbox instead of waiting for somebody to remember to run them.

    More on this module
  11. A documented REST API and webhooks on every meaningful event, so your RMM, your PBX, your billing platform and your quoting tool can all read from and write to the same record. Included, not licensed per connection.

    More on this module

Where to start

Find the bit that is currently hurting

Most people arrive with one specific problem rather than a plan to replace everything. Start there - the rest is already in the same system when you are ready for it.

Core platform

The system of record - the pages that describe CubeMSP as a whole, under the names the market searches for.

Service desk

Handling the work: the queue, the incident, the time it took and the knowledge that came out of it.

Client & commercial

The relationship: who the client is, what you supply them, what is in flight and what you show them at the end of the period.

Who it is for

Built around the kind of provider you actually are

A telecoms reseller, a security consultancy and a general IT support firm all sell a recurring service - but what they renew, what they bill and what they have to evidence are not the same. These pages set out what changes.

How it is built

Six things we decided at the start

These are the decisions that are expensive to change later, so we made them deliberately and we do not quietly reverse them for a bigger deal.

  • Built by people who run an MSP

    Crushed Ice has been supporting UK businesses since 2003 and is the first tenant on CubeMSP. Every screen has been argued about by someone who will have to use it during an outage, which is a different standard from a product demo.

  • One record, end to end

    A prospect becomes a client, a client gets services, services generate renewals, incidents get logged against them, and the review at the end of the period is assembled from what actually happened. Nothing is re-keyed between those steps because there are no seams between them.

  • The client sees a system, not an inbox

    Shared project boards give clients a real view of the work in flight, with internal-only tasks and comments filtered on the server. They get transparency; you keep the conversation you need to have with your own team.

  • AI that drafts, never decides

    Similar-incident retrieval, knowledgebase drafting and review narratives are all generated as drafts for a human to approve. The AI never invents a number - every figure in a review is computed from your data and handed to the model, not asked of it.

  • Tenant isolation is the architecture

    Every MSP’s data is kept completely separate, and your clients only ever see what you choose to share with them.

  • We tell you if we are not a fit

    If CubeMSP is not the right fit we will tell you during the demonstration rather than six weeks into a migration. It costs us the sale and saves you the write-off, and in a market this small the reputation is worth more than the licence.

What happens next

Set it up yourself, or with us

  • Set it up yourself, online

    Import your clients, services and ticket history, set up your service catalogue and invite your team. Bring as much ticket history as you can: it is what makes the knowledgebase and similar-incident retrieval useful from day one.

  • Enterprise

    We can do the set-up and migration with you, in person if you’d like, or run CubeMSP in a dedicated environment.

Where we work

Online from anywhere, in person if you’d like

For Enterprise set-up and migration, we work in person across the UK from our base in Olney, Buckinghamshire. These are some of the areas we regularly cover. If you’re not listed, we’ll still come to you.

Talk to us

Tell us what is actually broken

No scripted demo and no hoops to jump through before you speak to someone technical. Describe the problem and we will tell you whether we can fix it and what it would take. If we are the wrong people for it, we will say so.