Have a question about best practices
Theres discussion about bringing our transaction table which looks like this
Type - Amount - Date
new $50 2015-01-01
upsell $25 2015-02-04
downsell -$10 2015-03-03
Into SFDC as Opportunity Record
The goal is to track not only sales but also downsell or churn and apply clawback to sales reps
My concern is that it will create alot of noise and it is not the intent of an opportunity record and there would be alot of uncessary complexity added to opportunity records
Does it make sense to try to create a process to load this data or maybe have it in a separate object that reside in SFDC
Thoughts?
2 Antworten
Hi Chattry,
1. Definitely wouldn't recommend creating these as Opportunities. It's not really an Opportunity and as you said it will create alot of noise and confuse your sales team and dilude the pipeline numbers
2. Because these are already acquired customers, I have done this in 2 ways:
- If you are looking at subscription on an Account level, you could create acustom object that is master detail to Accounts to track these types of transactions (FYI - these are on the lines of Invoices and Payment that we integrate from our own Db into SFDC on the Acocunt level so reps know what was invoiced and paid)
- If you are looking more at a Contract/Annual contract where each Opportunity represents the Contracts that have been won, I'd consider having the custom object, called Software transactions and such on the Opportunity
I've implemented these on a SaaS business with membership and subcription model that they currently use to manage their membership cont processes
Hope that helps
Best
V
