Let the client watch the work without watching the workings.
Early accessIT Project Management Software
Shared kanban boards for migrations, rollouts and onboardings - with the client invited in, and internal-only tasks filtered on the server.
- Part of CubeMSP
- Serving businesses across the UK
- 01234 672 617
Project work is where managed service providers earn their reputation and lose their margin. A migration runs alongside the day job, updates to the client happen over email or not at all, and the moment somebody asks "where are we with this?" the answer takes half an hour to assemble. CubeMSP puts projects on kanban boards attached to the client record, with columns, categories, assignees, dependencies and time booked against tasks. Boards can be shared with the client, so they see live progress rather than a weekly summary, and internal-only tasks and comments are filtered on the server, so your engineers keep the conversation they need to have with each other.
- £0
Charge per client user on a board
- Server-side
Internal task and comment visibility
- Templated
Onboardings and migrations, reused not rebuilt
What it does
Inside IT project management software
The parts of CubeMSP that make up project management. Everything here shares one database, so nothing needs re-keying between them.
Boards that match the work
Columns, categories, swimlanes and work-in-progress limits defined per board, so a Microsoft 365 migration and a client onboarding do not have to share a shape.
Clients invited in, at no per-seat charge
Client users see the board, the progress and the tasks that concern them. Invite the whole steering group if you want to - there is no per-user portal charge.
Internal-only, enforced on the server
Tasks and comments marked internal never leave the API for a client session. Visibility is a property of the record, not a rule in the interface that one bad query undoes.
Dependencies and sequencing
The tasks that block other tasks marked as such, so the thing everything is waiting on is visible rather than being remembered by the project lead.
Time against the task
Project time booked where it was spent, so the difference between the quoted project and the delivered one is a figure you can look at before you quote the next one.
Templates for work you do repeatedly
Onboardings, migrations and refreshes as reusable board templates. The twentieth onboarding starts from the nineteen before it rather than from a blank board.
In practice
Problems this actually solves
Anonymised, but not invented. These are the situations businesses describe to us before they change anything.
A migration reported over email
The situation
A ninety-user mail migration ran for eleven weeks. The client received a status email most Fridays, written by the project lead from memory, and asked for an interim update roughly twice a week in between.
What changed
The client is on the board. The Friday email stopped being necessary, the interim requests stopped almost entirely, and the project lead got several hours a week back.
The same onboarding rebuilt every time
The situation
Client onboarding was a well-understood process that existed as a checklist in a document, copied into a new task list each time. Steps were occasionally missed, and the checklist and the reality had diverged over two years.
What changed
Onboarding is a board template. Improvements go back into the template rather than into one person’s copy, and the missed steps stopped being missed.
Project work quoted on a hunch
The situation
Fixed-price projects were quoted from experience. Some made good money and some did not, and because project time was never recorded separately from support time, nobody could say which had been which.
What changed
Time is booked against project tasks. After two quarters the firm could see which project types were consistently underquoted, and adjusted two of them.
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.
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.
You might call it something else
Project management goes by a lot of names - if you searched for any of these, this is the page you wanted.
- IT project software
- MSP project management
- Migration project software
- Client project boards
- IT rollout management software
- Onboarding project software
Questions
The things people ask first
No. Client users are not charged for. Charging per client seat is how portals end up with nobody in them, and a portal nobody logs into is worse than no portal because it creates the impression of transparency without delivering it.
Visibility is enforced in the API, before data is serialised. A client session cannot receive an internal task or comment even if the interface asks for one, and there is an automated test on every route asserting exactly that.
For MSP delivery work - migrations, rollouts, onboardings, refreshes - yes. If you run formal critical-path programme management with resource levelling and earned-value reporting, it is not, and we would rather tell you that now.
Yes, and the link is kept in both directions. An incident that turns out to be a piece of project work can be attached to the board without being retyped or duplicated.
Yes. Internal boards with no client attached work exactly the same way - most providers end up with a few for their own infrastructure and improvement work.
Related
Other things we can put right
MSP Software
One system for clients, services, renewals, incidents, projects and reviews - built in the UK by a managed service provider.
Read moreClient Reporting Software
Branded quarterly and annual service reviews assembled from the period’s real data - every figure computed, then narrated, never estimated.
Read morePSA Software
Professional services automation for MSPs - clients, contracts, tickets, time, projects and billing data on one model.
Read moreService 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.
Read more
Part of a bigger system
Project management 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.
Talk to us
Is project management 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.