Halo for real project work, or is it a service desk with a project tab?
Leadership wants us to grow the project services side now. Traditional IT consulting, some app dev, cloud migrations, transformation-type stuff. Mix of fixed milestone and T&M.
For anyone who’s tried to run actual project work through Halo:
Does the project module hold up under real project delivery, or does it feel bolted on next to the service desk
Resource planning across a 50 - 60 people. Is it there or are you exporting to Excel?
Utilization and margin reporting at the project level. How deep does it go?
Where does it hold up? Where does it fall apart? Anyone move off it to Kantata, Scoro, Projectworks and never look back? Anyone try one of those and wish they’d gone with Halo?
Anyone try to run this in Halo, give up, and move to something else?
Trying to figure out if we push harder on Halo or accept we need a second tool for project delivery.
Posted Jul 23, 2026, 5:13 AM UTC