CubeMSPEarly access

Run the whole MSP from one system.

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.

Book a walkthroughWhat it costs

Most managed service providers end up running on a PSA they have outgrown, a spreadsheet of renewal dates, a shared mailbox that has quietly become the ticket queue, and a review deck somebody rebuilds by hand the week before every client meeting. CubeMSP replaces that with one system where a prospect becomes a client, a client gets services, services generate renewals, incidents are logged against them, and the service review at the end of the period is assembled from what actually happened. It is built for providers in the five-to-fifty-technician range: firms large enough that the spreadsheet has stopped working, and small enough that a six-figure PSA licence and a nine-month implementation is not a serious answer.

  • 20+

    Years running an MSP

    Crushed Ice has supported UK businesses since 2003

  • 1

    System, not five

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

  • 100%

    UK hosted

    Data, backups and support all in Britain

  • 0

    Per-seat portal charges

    Invite as many client users to a board as you like

What changes

Three things that are different by the end of the first quarter

Not a feature list. These are the differences people describe when we ask them what actually improved.

  • You can see the client whole

    Services, renewals, open incidents, project status, time spent and margin on one screen. The question "how are we doing with this client?" gets an answer in ten seconds instead of three people and a spreadsheet.

  • The same fix stops being re-derived

    Semantic retrieval over your own resolved incidents means the technician who has never seen this problem gets shown the three people who have, and what they did. Knowledge stops leaving when people do.

  • Margin you can actually see

    Cost and sell held on every service, time booked against the work it was spent on, and renewals dated. Which clients make money - and which have quietly been subsidised for years - stops being a matter of opinion.

The platform

11 modules on one database

Every module reads and writes the same records. There is no integration layer between quoting and stock, because there is nothing to integrate - it is one system.

  • Clients, contacts & sites

    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.

  • Pipeline & opportunities

    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.

  • Services & subscriptions

    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.

  • Renewals & margin

    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.

  • Incidents & service desk

    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.

  • Time tracking & billing data

    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.

  • Projects & shared boards

    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.

  • AI-assisted knowledgebase

    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.

  • Client service reviews

    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.

  • Reporting & dashboards

    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.

  • Integrations & API

    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.

The technical answers

The questions your IT people will ask

Answered here rather than in a follow-up call, because they are reasonable questions and the answers do not change.

  • Hosting

    UK data centres, managed by the group. Encrypted at rest and in transit, encrypted off-site backups, and a documented, tested recovery process.

  • Tenant isolation

    Every query is scoped to your tenant at the data layer, not by a filter somebody remembered to add. Cross-tenant access returns a 404, and every route ships with an automated test proving it.

  • Access control

    Role-based permissions, per-board client visibility, internal-only tasks and comments enforced on the server, single sign-on, and an immutable audit log of every change with who, what and when.

  • AI handling

    Your data is never used to train a third-party model. Retrieval is scoped to your tenant by construction. Everything generated is a draft for a human to approve, and every AI interaction is logged.

  • Your data

    Exportable in full, at any time, in open formats. There is no commercial advantage in holding a customer’s data hostage and we do not design as though there is.

  • Updates

    Continuous, versioned and migrated. No forklift upgrade project every three years, and no version so old it can no longer be supported.

Who we see most often

A description, not a restriction

If you are not on this list, the question is still whether the system matches how you work - and that is a ten-minute conversation, not a qualification form.

  • Managed service providers with five to fifty technicians
  • IT support companies running on a shared mailbox and a spreadsheet
  • MSPs who have outgrown a small PSA but cannot justify a tier-one one
  • Providers billing recurring services, licences and subscriptions
  • Firms running client migrations, rollouts and onboarding projects
  • Anyone rebuilding the same client review deck by hand every quarter

It does not stand alone

Keep your accounts package, your web shop and your couriers

CubeMSP handles the business layer and hands the finished numbers over. Nothing here is a paid connector.

Getting there

What implementation actually involves

Five stages, each one quoted before it starts. Discovery, training and go-live are done on site.

  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.

By problem

The same platform, described the way people search for it

Modules are how the system is built. These are the problems it gets bought to solve.

Where the product currently is

CubeMSP is in early access. That means we are onboarding a limited number of businesses at a time, with direct access to the people building it and real influence over what gets built next. It also means the roadmap is public to the people on it and we will tell you plainly if something you need is not there yet.

Ask about early access

Talk to us

See it against your own paperwork

Bring a real client, a real week of tickets and a real renewals spreadsheet. A walkthrough using your own data tells you more in forty minutes than a scripted demo does in a fortnight.

Start a conversationCall 01234 672 617