Replace the PSA you have outgrown, the renewals spreadsheet and the shared mailbox pretending to be a queue.

Early access

MSP Software

One system for clients, services, renewals, incidents, projects and reviews - built in the UK by a managed service provider.

Book a walkthroughAbout CubeMSP

MSP software should do one thing above all else: let anybody in the business see a client whole. CubeMSP holds the client record, the contacts and sites, the services and subscriptions you supply, the renewal dates and margins attached to them, the incidents raised against them, the projects in flight and the review that summarises it all - in one place, on one data model. It is designed for providers with five to fifty technicians who have outgrown a spreadsheet-and-mailbox setup but who cannot justify a tier-one PSA licence and the nine-month implementation that comes with it.

  • 1 record

    Prospect to review, no re-keying between stages

  • Live

    Renewals, incidents and margin, not a monthly export

  • UK

    Hosted, supported and built in Britain

What it does

Inside MSP software

The parts of CubeMSP that make up MSP software. Everything here shares one database, so nothing needs re-keying between them.

  • The client, whole

    Contacts, sites, services, renewals, open incidents, project status, time spent and margin on one record. The question "how are we doing with this client?" gets an answer in ten seconds rather than three people and a spreadsheet.

  • Services and subscriptions tracked properly

    Every licence, circuit, backup, firewall and support contract you supply, with quantity, cost, sell price, term and renewal date. The thing MSPs most often run in a spreadsheet, and most often get wrong.

  • Incidents against the thing they affect

    An incident is logged against a client, a site, a service and a category - so the tenth recurrence of the same problem is visible as a pattern rather than ten unrelated tickets.

  • Projects the client can actually see

    Shared kanban boards for migrations, rollouts and onboardings, with internal-only tasks and comments filtered on the server rather than merely hidden in the interface.

  • A knowledgebase that builds itself

    Resolved incidents are drafted into articles for a human to approve, and semantic search over your own history surfaces the last three times this happened and what fixed it.

  • Reviews assembled, not rebuilt

    Branded quarterly and annual service reviews composed from the period’s real data - tickets, response times, projects, spend and upcoming renewals. Every figure computed, then narrated.

In practice

Problems this actually solves

Anonymised, but not invented. These are the situations businesses describe to us before they change anything.

  • A twelve-technician MSP running on a shared mailbox

    The situation

    Support arrived at support@, rules sorted it into folders, and whoever was free picked it up. Nobody could say how many incidents a client had raised in a quarter, what the response time had been, or whether a recurring fault had ever been fixed properly.

    What changed

    Incidents are now logged against the client, site and service they affect, with priority and time booked against them. The quarterly review is generated from that data instead of being reconstructed from a mailbox.

  • A provider losing renewals to a spreadsheet

    The situation

    Licences, circuits and support contracts were tracked in a workbook maintained by one person. Two renewals auto-rolled at the old price in a single year, and one lapsed entirely before anyone noticed.

    What changed

    Every service now carries a term, a renewal date, a cost and a sell price. Renewals appear on a dated view with the margin next to them, and the conversation happens before the date rather than after it.

  • An MSP where the knowledge lived in one engineer

    The situation

    The senior engineer knew every client’s quirks, every awkward legacy application and every workaround. When he took two weeks off, three problems that had been solved before were solved again from first principles.

    What changed

    Resolved incidents are drafted into knowledgebase articles and indexed for semantic search. A technician who has never seen the problem is shown who has, and what they did about it.

How it happens

What implementation actually involves

No mystery, no discovery phase that quietly becomes the project. Five stages, and you will know what each one costs before it starts.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

You might call it something else

MSP software goes by a lot of names - if you searched for any of these, this is the page you wanted.

  • MSP management software
  • Managed service provider software
  • MSP platform
  • IT support company software
  • MSP business management system
  • Software for managed service providers

Questions

The things people ask first

  • In scope, it overlaps heavily - clients, tickets, time, projects and contracts. The differences are that CubeMSP treats client-facing reviews and shared project boards as core rather than as add-ons, that the knowledgebase is built from your resolved incidents rather than typed from scratch, and that it is priced and implemented for a firm of five to fifty technicians rather than five hundred.

  • For a typical provider of ten to thirty people, expect six to twelve weeks from kick-off to go-live: discovery, configuration, data migration, training, then a supported cutover. We give you a realistic range after discovery rather than an optimistic one to win the order.

  • No, and it is not trying to. CubeMSP is the business layer - clients, services, renewals, incidents, projects, knowledge and reviews. Your RMM does monitoring, patching and remote access, and talks to CubeMSP through the API. Replacing a good RMM would be a bad trade.

  • Yes, and you should. The knowledgebase and similar-incident retrieval are only as useful as the history behind them, so migrating tickets matters more here than in most implementations. Clients, contacts, sites, services and renewal dates come across as standard.

  • Cube Systems, part of Crushed Ice Group. Crushed Ice has been running as an MSP since 2003 and is the first business using CubeMSP in production. Every screen has been argued about by somebody who has to use it during an outage.

  • In the UK, on infrastructure managed by the group, with encrypted off-site backups and a documented, tested recovery process. Data residency is part of the platform rather than a premium tier.

Related

Other things we can put right

Part of a bigger system

MSP software is one part of CubeMSP. You can start here and switch the rest on later - it is the same system, not a separate purchase bolted on.

Explore the platform

Talk to us

Is MSP software your actual problem?

Sometimes it is not. Tell us what is going wrong and we will tell you whether this is the right thing to fix first.

Start a conversationCall 01234 672 617