Neptune.io is a real underdog. Setting up cron and monitoring 'pipes' is completely painless, which actually encourages you to configure more of them. This is a virtuous cycle of improving the system quality, and enabling a few people to keep a handle on many things. Before locking yourself into a cloud-specific product, look at Neptune and experiment on a trial.
AWS Fargate was a really pivotal decision for us, because it ensured the integrity of code running in production. That was a major requirement for the security and compliance audits (SOC II, etc).
Successfully completing those audits gave us access to new business partnerships, while on the engineering side Fargate reduced the work needed to maintain production apps.
Even decided to use Keybase Teams because we needed a BYOK solution to securely sharing critical data, which could be expired, and was TOFU-safe.
These together allowed us to use this tool within our data security chain.
We chose Kustomer because of the excellent engine and API at the core of the product. Kustomer has built a truly dynamic rules engine (and language) for automating service and response patterns, identifying trends, and improving engagement. This enabled a much smaller team to help a larger audience than normal.
Configuring the rules engine does take someone with an engineering mindset. It really is a programming language — like regex for Customer Service workflows. The upshot is that the Kustomer team loves you when you use it yourself, and provide top-notch support for those that do. I got into a great relationship with the crew there.
I would avoid using any other CS SaaS, having now used Kustomer.
We use Lattice because it has great integrations with Slack and other tools that we use daily. Moreover, Lattice has the solid visualization and charting method. The biggest win is the check-in system. Lattice has had the smoothest of all the check-in systems that we found. Even moreso than Betterworks
Banner auction controls via direct integration with our in-house admin and the DFP Ad Management API. Google Doubleclick for Publishers let us control yield management for parameters that were outside the scope of our datawarehouse
We used Betterworks because it had good integrations with may tools, and felt like a ful-featured experience. The learning curve was slightly more that other OKR tools, but we felt more in-control of the configuration, and the support was great for any question that we asked.
Moreover, Betterworks has the best visualization and charting of any of the small-office OKR tools that we found. Since the OKR framework is so open, it makes it hard to say exactly why betterworks is so much easier to use. e.g. it's far better than Atiim. I think the product team there must heavily dogfood the app's ability to set numerical targets and graph those properly.
