

You've decided to switch PSAs, and since your team has been complaining about the old one for a couple of years, nobody is going to push back on the decision. You decide to pull dispatch, billing, the techs and the account managers into a room so everybody has a hand in building the plan because the PSA touches all of them. I would have done exactly the same thing earlier in my own MSP.
The trouble is that this is where the project starts to go sideways and it happens so quietly that most owners don't notice until they're a few months behind and trying to work out where the time went.
Think about what the weekly project meeting looks like around week three.
The same questions from last Tuesday are still on the agenda. Somebody wants a custom field added to the ticket form while somebody else thinks it's a waste of everyone's time, and dispatch and the techs spend forty minutes debating what to call a ticket status.
When someone finally says they'd like a little longer to think it over, the decision gets pushed a week, and then pushed again. Nobody in that room is being difficult, and most of them are working hard to get it right, but when there's nobody with the authority to break a tie, the effort to get it right slowly turns into never deciding anything.
What gets overlooked is that when ten people share one decision, none of them owns the result. If go-live slips by two months and you ask who was responsible, you'll get a room full of people looking at each other. The whole time, the project has felt collaborative and productive, which is exactly why it's so easy to miss that it stopped moving.
The answer is to name one person as the owner of the PSA switch.
I mean one actual person. Not a department or a committee with a chairperson but someone who owns the result and the date and who makes the calls along the way. When two options are both reasonable, they pick one and move forward. I would take a decent decision made this week over a perfect one made next quarter because in my experience the perfect one tends to never get made.
When owners ask me who that person should be, I usually tell them it probably shouldn't be them.
The owner is the most expensive hour in the building, and a project like this will eat time that ought to go toward hiring, key client relationships and the other things only the owner can do. A better choice is whoever sits closest to the daily operation, has the trust of the team and has some room on their plate. That might be your service manager, a senior tech who likes process, or your ops lead, as long as it's somebody who finishes what they start.
Whoever you choose, you have to back them in public. If they make a call on Monday and someone comes to you on Tuesday to get it changed, you've quietly rebuilt the committee, and your team will work that out inside of a week. After that, the title you gave that person doesn't carry any weight.
A lot of owners worry at this point that putting one person in charge shuts everybody else out, but it really doesn't. Dispatch still gets to tell the owner what they need from the board, the techs still get to say what slows them down on a ticket, and billing still gets to flag what has to work on day one or the invoices break. The owner takes all of that in before making the call, so everyone gets heard even though they don't each get a vote.
The person you pick will also need a few things to do the job properly. They need a written definition of what done looks like, a date, a short weekly status that somebody can read in five minutes, and a list of the decisions they're allowed to make without checking with you first. If they end up having to run every call past you, you haven't really handed over ownership, you've just given them the job of carrying messages back and forth.
There's one more thing I'd set up at the very start, which is that once a call has been made, everybody commits to it, including the people who argued for the other option. I'd say that out loud at the kickoff so nobody is surprised later, letting people make their case before the decision and treating it as settled afterward. Without that agreement, every call the team doesn't love gets reopened and you end up right back in Tuesday's meeting.
Scope tells you what gets built and by when, the bathroom before the kitchen, while ownership tells you who makes the calls inside that scope. A project with scope but no owner still drifts, and a project with an owner but no scope still sprawls, so you really do need both to get across the finish line.
This applies well beyond the PSA, of course.
A new RMM, a new onboarding process, a new documentation system or a change in how you run your quarterly security briefings will all go better with a single named owner who has real decision rights and whose name is written down before the work begins. That belongs in your field guide as a standing rule for how your business handles change, so you aren't figuring it out from scratch every time a big project shows up, and it's the kind of thing we help MSP owners build at www.builttorunmsp.com.
Frequently Asked Questions
Who should lead a PSA migration at an MSP?
The best choice is usually one person who is close to the daily operation, trusted by the team and able to give the project real time, such as a service manager, an ops lead or a senior technician. It's usually not the owner, whose hours are better spent on work only the owner can do. Whoever leads it needs the owner's visible backing and the authority to make decisions without asking permission each time.
Why do MSP projects stall when the whole team makes the decisions?
When a decision is shared by many people, the accountability is shared too, which means nobody feels responsible when the schedule slips. The meetings fill up with open questions that get pushed from week to week because nobody has the authority to break a tie.
Does single ownership mean ignoring the rest of the team?
No, because the owner still gathers input from dispatch, technicians, billing and account managers before making a decision. Everyone contributes to the outcome even though only one person makes the final call, and that keeps the project moving without shutting anyone out.
What does a project owner need in order to succeed?
They need a written definition of done, a deadline, a short weekly status update and a clear list of the decisions they can make on their own. The rest of the team needs to commit to those decisions once they're made, even when some people would have chosen differently.
Adam Kuester
Adam Kuester has a PhD in genetics and a career built inside managed services, an unusual combination that shapes how he works. He spent time designing operations at an MSP before joining Bruce McCully to build Galactic Advisors, where he's served as VP of Special Projects. His focus has been operational: finding gaps, building systems, and turning expertise into tools MSP owners can use across a partner base of nearly 1,000 companies. Built to Run MSP is that same work in a different form, practical frameworks for MSP owners who are good at winning business and want to get equally good at running it.