A holistic approach

We believe in thinking to the future when it comes to System Design. In the context of CRM, and especially salesforce.com, there are a number of questions that must be taken into account in relation to systems design. These include, when to use custom objects versus standard object or picklists, when to use record types versus new objects, when to use custom classes or triggers in Apex, and when to use Visualforce.

Our hindsight is your value

To someone who is inexperienced in deploying salesforce.com these choices may not seem to matter, because they may not have direct implications on the current roll-out, but through experience, Hallman knows that choices you make in the initial design will have long lasting affects as the system is extended and expanded.

Why does this matter?

One example for you to think about, you want to track Partners in your CRM system and want to have a separate tab that you can click on to show all your partners, sounds simple enough, right? At first thought someone would potentially create a new custom object, link it to a custom tab, and create a new partner screen. There are problems that arise though with this approach, because if you know salesforce.com you would have realised that while this works in the short term, what if you then want to deploy a Partner Portal in the future? Well in salesforce.com the Partner Portal is driven from the Account object, and if you had chosen this design approach, and then decide to use Partner Portal, you would then have to re-design your entire Partner setup, which could take days or weeks to complete.

Experts

Hallman knows the end to end functionality in salesforce.com, and will advise you not just on the shortest path to get it up and running, but also we'll let you know the future implications of design choices you make when you roll out now.

Want to know more? Please feel free to contact us.