Firstly, the Sonar team has done a wonderful job with v2 building a piece software that is a joy to use. Sonar is an integral part of our business. We’ve developed a lot of custom code to extend it to fit our needs.
We’re at a fork in the road, because the scheduling/dispatch isn’t cutting it anymore, It is actually really great for what it does… The map, the scrolling it was really well designed… but we’ve grown a little bit and need more from it, specifically:
- We need to put multiple people on jobs
- We have install jobs that take a week, with many people, how can we schedule them?
The workaround: “job cloning”… so if we had a 1 week job with 2 people, I would need to create 1 job + 13 dummy/clone jobs to block out the calendar. (Or am I wrong? Maybe I’m missing something).
But, what if a job gets re-scheduled? Then I have to move 14 jobs around. And where would job notes go? which job? It might be confusing.
Here are the options I can think of:
Option 1: Keep using Sonar
- Go with the Dummy/Clone job route, but use the API to manage them… perhaps build a tool that would link jobs together and be able to perform bulk changes on them.
- PRO: No integration needed with other software
- CON: Seems messy and clunky. We would end up with hundreds of dummy jobs each month.
Option 2: Build our own calendar
- I’ve had to do it before, build off of FullCalendar.io, to do exactly what we need
- It would have it’s own “appointments”, that link back to actual Sonar Jobs
- PRO: we get exactly what we want
- CON: Expensive - we have to build and maintain, re-inventing the wheel a little bit
Option 3: Use 3rd party, like Jobber
- PRO: Get specialty software for cheap (depending on how much integration there is)
- CON: Constrained by integration, where will customer data and job notes live? duplicated?
Option 4: Pay Sonar for Development?
- Is this an option?
I would love to hear peoples opinions… especially @simon. Thanks!