Thank you for taking the time to review Nimble.
I want to address a few of the concerns you brought up in the Cons to help out.
For 1. We recommend using the Custom Data fields feature in Nimble to create uniform data instead of Tags because they can definitely get messy.
For 2. Twitter doesn't differentiate between people or company accounts over their API, therefore, we can only import all contacts as a person or a company. We chose to go with "person" by default because this is more often the case than not. We're planning to add the option to convert a contact record from a person to a company in the future to help with this pain from Twitter.
For 3. We offer customer support via email M-F from 9-5 PM Pacific and you will always hear back from us if you write to firstname.lastname@example.org. We are also addressing CSV upload issues this summer to make it easier to bring your data into Nimble.
For 4. LinkedIn has limited their API from allowing CRM systems to sync job changes, therefore, you may update contacts with the Nimble Smart Contacts App while on LinkedIn if a contact changes their job. It's a different workflow, but it achieves the same result.
All in all, I really appreciate your feedback for Nimble. This is the kind of feedback we want so we can continue to stay at the top.