After saying I was not interested in paying that nearly four figure amount, their development project person responded with:
“Unfortunately, this amount is the a starting point for us. I saw that there was another user who wanted this functionality, you could go half and half with him.
At the moment we try not to take small projects like this. We hope for your understanding.”
My response was:
“I do understand but don’t think you do: ANY business has multiple people interacting with the website and WP-CRM is only useful if multiple roles can access its functionality.
Example: I am our company’s website administrator. Janice is our WooCommerce Shop Manager and she also manages all website users as well as our user and prospect databases.
I do NOT want to make Janice an administrator on the website. She is not technically capable, there are an overwhelming number of menus that load (which have nothing to do with her job nor does she have to see them) and I also do not want her in doing things on the website she should not.
We have two other roles who also need to manage users and I also do NOT want to make them administrators and I DO NOT HAVE TIME PERSONALLY TO TAKE ALL THEIR REQUESTS AND PERFORM USER MANAGEMENT.
That is why this should NOT be a custom-coding job but rather built-in to the plugin.”
———————————-
This “admin only” capability is so short-sighted that it would be funny if not going to create more work for us. It would be like WordPress having only ONE role (the admin) so everyone who authored a post, for example, could do whatever they wanted on the site.
So I’m going to rip out WP-CRM this week and replace it. The sad part is that we leveraged their custom fields and re-imported all user data with these fields.