The hard part isn't the technology
A PSA system works from day one. What takes time are the decisions: what your contracts should look like in the system, who is authorized to approve what, which categories should exist, and how time should be tracked.
No vendor can make those decisions for you. We can show you how other Nordic MSPs have solved it and tell you what usually works, but the choices are yours.
That is also why projects drag on. Not because the configuration is difficult, but because someone needs to make a decision.
What you should prepare
A list of your contract types. All of them, including the two customers with special arrangements. Exceptions are what usually break a configuration, and it is best to discover them before, not after.
Your price lists. Which prices apply to whom, and what happens outside of office hours?
A designated system owner. A person with the mandate to make decisions. This is the single most important preparation.
An answer to what you want to achieve. Shorter lead times? Higher billable utilization? Stop leaking time? Your goal drives the configuration more than you might think.
A list of integrations. Accounting systems, monitoring, documentation, and Microsoft 365 – including information on who owns each system at your company.
Phases
Mapping. We review your business model, contract types, customer structure, and tool stack. We conclude with a concrete plan and a fixed price.
Basic configuration. Customers, contract models, price lists, ticket types, SLAs, and permissions.
Integrations. Financial systems first – that is where the greatest time savings are found. Then monitoring and documentation.
Customer portal. White-labeled portal, service catalog, and approval workflows.
Automation. Assignment, escalation, and recurring billing. Start small – see automation.
Verification and training. You test against real-world scenarios before go-live, and both technicians and administrators are trained.
Go-live and follow-up. We follow up after a few weeks and iron out any friction.
Why projects drag on
No one owns the decisions. When every issue needs to be vetted by a group, the project stalls between meetings. A system owner with decision-making authority cuts lead times in half.
There are more agreements than you thought. Mapping often reveals setups that have evolved organically without anyone actually deciding on them. It’s useful to discover, but it takes time.
Everything must be included from the start. Including projects, quotes, advanced reporting, and five integrations in the first release is a surefire way to delay the go-live date.
Training is booked too late. A system that technicians haven't had time to learn will feel worse than the old one for two months, no matter how good it actually is.
Start smaller than you think
The most common advice we give, and the one followed the least.
Get ticketing, time tracking, agreements, and invoicing working first. That’s where the money is. Projects, quote workflows, and advanced reporting can come in step two, once you know how you actually use the system.
A business up and running in six weeks that is expanded continuously beats a perfect project that launches after six months.
We’ve done it ourselves
MSP Nordics runs its entire business in HaloPSA – service desk, agreements, time tracking, and invoicing.
We know which configurations hold up as your customer base grows, and which ones look good in a demo but become a headache after six months. We are the largest distributor of Halo in the Nordics and work in your time zone.
If you are switching from an existing system, see migrating to HaloPSA. If you first want to clarify what a PSA should do, the overview is available under PSA.
