# MSP Software in Gloucestershire > Looking for MSP software in Gloucestershire? CubeMSP works with businesses in Gloucester, Cheltenham and Stroud, from first demonstration through to go-live and beyond. **URL:** https://cubemsp.co.uk/software/msp-software/gloucestershire Gloucestershire businesses tend to reach us at the same point: the current system has become the constraint rather than the tool, and the workarounds have started to cost more than the software. That is the point at which MSP software is worth doing properly. ## Details - **Solution:** MSP Software - **Group:** Core platform - **Platform:** CubeMSP (https://cubemsp.co.uk/platform) - **Location:** Gloucestershire - **Distance from our Olney office:** 68 miles - comfortably within a morning’s drive of our Olney office - **Postcode districts:** GL - **Also known as:** MSP management software, Managed service provider software, MSP platform, IT support company software, MSP business management system, Software for managed service providers ## Coverage Our Gloucestershire coverage includes Gloucester, Cheltenham, Stroud, Tewkesbury, Cirencester and Lydney, and the GL postcode districts. If you are in Gloucestershire and not on that list, we almost certainly still cover you, so ask. ## What is included - **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. ## Real-world use cases ### A twelve-technician MSP running on a shared mailbox **Scenario:** 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. **Outcome:** 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 **Scenario:** 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. **Outcome:** 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 **Scenario:** 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. **Outcome:** 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. ## Figures - **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 ## Frequently asked questions **How is this different from a PSA?** 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. **How long does implementation take?** 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. **Does it replace our RMM?** 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. **Can we bring our ticket history across?** 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. **Who actually built it?** 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. **Where is the data hosted?** 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 solutions - **PSA Software** - Professional services automation for MSPs - clients, contracts, tickets, time, projects and billing data on one model. https://cubemsp.co.uk/software/psa-software/gloucestershire - **IT Service Management Software** - Incidents, requests, problems and knowledge handled consistently, with the service catalogue and the client record in the same system. https://cubemsp.co.uk/software/it-service-management-software/gloucestershire - **Service Desk Software** - A real queue instead of a shared mailbox - incidents logged against the client, site and service they affect, with priority, ownership and time. https://cubemsp.co.uk/software/service-desk-software/gloucestershire - **MSP CRM Software** - Prospects, clients, contacts and sites in the same system as the services you supply and the incidents you handle - so winning an account and running it are one record. https://cubemsp.co.uk/software/msp-crm-software/gloucestershire ## Contact - **Product:** CubeMSP - **Trading name of:** Cube Systems Limited (company number 17220899, ICO registration number ZC216972) - **Email:** hello@cubemsp.co.uk - **Sales:** sales@cubemsp.co.uk - **Support:** support@cubemsp.co.uk - **Telephone:** 01234 672 617 (+441234672617) - **Address:** Unit 11, Olney Business Park, Osier Way, Olney, Buckinghamshire, MK46 5FP - **Opening hours:** Monday to Friday, 9am to 5.30pm - **Part of:** Crushed Ice Group (https://crushedicegroup.co.uk)