Sorry for taking so long to reply, I was a bit swamped over the last days. There are now a few screenshots over at the "Features" page (https://cormhq.com/featu

Sorry for taking so long to reply, I was a bit swamped over the last days. There are now a few screenshots over at the "Features" page (https://cormhq.com/features https://cormhq.com/features) as well as link to a live Demo at the bottom of "Features" and at the top of "Pricing"/"Sign Up". You/Your dad can just check it out yourself and see whether it's the right fit (I'd argue it is). That said: This was originally planned during my work for another startup where we were in contact with a lot of customers of relatively low lifetime value. As such, we needed a lightweight system to track our interactions with them without any sales overhead – all we needed was to know if/when we already had contacted them and maybe how their mood was. Plus, a bit of oversight over our outbound agents was required, so some basic statistics needed to be collected. (Also, a lot of our customers came through other channels than direct contact, so we would often have to move contact details from production systems into our CRM, which prompted the inclusion of an API.) So, I'd say the main use case is if you're in a similar position: You need to keep track of who you've already talked to and what they said, but you're not in need of a real campaign management and don't have a highly structured sales process that needs to be reflected in your CRM. This often applies to smaller startups selling SaaS-Accounts, where most customer contact is of the "are you happy/is everything working?"-variety and large acquisition strategies are prohibitively expensive compared to what a customer brings in (or are simply not relevant).