I currently find myself serving the role of interim (it's a contract-to-hire role) IT director at a 300 person company. There are three people in my department currently (however the headcount is currently at 2, with the 3rd person being a contractor who they'll only want around while we get the helpdesk under control). The company is just now exiting their "startup phase" and trying to shift to a more structured corporate culture.
We use G Suite as our Identity Provider, we also have a grossly underutilized Okta implementation. There are a handful of PCs (~10), but the rest of the endpoints are Macs.
Currently, we have a JAMF Pro instance (running on JAMFCloud) that is also grossly underutilized. We have part of a prestage enrollment configuration set up, but it's still missing a few things. We do not have anything else set up in terms of policies or profiles. Our Self Service is somewhat of a joke. The tl;dr of it is that our JAMF Pro setup is grossly under-utilized. If we stick with JAMF Pro, I almost want to start it all over.
We're considering switching to Kandji. The primary thing enticing me (other than the $1K per month in savings) is that it sounds like it will free me from having to be both a dedicated JAMF Pro admin and an IT director. I have formal training in JAMF (I have the CCT for Casper 9, and 2018 JAMF 200 and 300 certifications for...well...2018 era JAMF Pro 10. I haven't had hands-on experience with JAMF Pro since then. While there's a ton of familiarity with it and while a lot of it is kind of like riding a bike, I'm absolutely rusty.
That said, I love and revere JAMF Pro. I'm just not sure if, given both the nature of our staffing, and the nature of the company at its current state (and our G-Suite and Okta affinity) that we're going to be able to get JAMF Pro to where we want to be given that there are only going to be 2 1/2 of us for the foreseeable future; Kandji sounds like it fits the bill.
That said (and I seriously apologize for how long this is already), regardless we still want to deploy something like JAMF Connect to enable users to log in with either their Okta and/or GSuite credentials rather than a local account password, and we'll still use JAMF Composer for Package creation.
Thoughts? Again, sorry about the length. I didn't expect to find myself conflicted here.