You’re offline. This is a read only version of the page.
20
Our company provides a hosted marketing automation application. It is sold as monthly to annual contract to anything from 1 person shops to large multi tiered companies with 500+ users.
We are migrating from CRM 3.0 on premise to CRM 4.0 and are rethinking some of our strategies. In CRM 3 we basically used "accounts" for two purposes. #1 they were used as a container for an "organization" as intented. However we had an account type dropdown with a number of custom tabs that coresponded to an account type = customer. The custom tabs stored everything from dates used to track the setup process, number of users, etc.
The problem with this is a redundancy of data. Sometimes a single person will buy our product. A contact is used to track the person but then a "customer account" is created as their name to track their subscription and it's status.
How would you solve this issue? A custom entity perhaps? We need a lot of the functionality provided by accounts (parent / child relationships, connection to contacts, rollup of notes etc)
I appreciate any feedback and experience.
-Jeff
*This post is locked for comments
I have the same question (0)
Jeff,
I don't think there is anything wrong with your design. You're selling to an organization no matter what the size and each organization must have at least one contact. So, I think that's fine.
If you don't like having that extra contact, just put a checkbox on the Account form that states that this organization is a single person.
Mitch
Share
Report
All responses (
Answers (
