A wrapper around the 'optimised for field sales' crm ForceManager - specifically the JSON API used to maintain the background data.
Structurally I plan to make it one base class (ForceManager.pm) and currently 13 ForceManager:: child classes due to the facility to set custom fields and requirement parameters which would be better served as a class definition than monolithic configuration.
I've already got a working version of this developed with assistance of ForceManager themselves, but it used something of a questionable approach.
I hope to use this as an easy on ramp to CPAN contributions as it's more a case of procedure and optimisation than hard coding problems.
Insights greatly appreciated!