6QA stamp on opp - what ways do you use this?

CarlyShideler · April 2024

I have read the other revcity discussion posts regarding stamping 6qa on opps, the SF flow, etc.

I am curious how any end-users have used these data points in a way that has been impactful to their business?

And, did you stamp the start/end date of the 6qa or did you stamp the "age" in days? Is one data point used more often in your reporting than the other? Our SF admin is selective when it comes to new fields on the Opps, so, I am also trying to be selective.

thanks in advance for sharing your experience!

Jarrod Cohen · April 2024

We have yet to stamp the opp here, but I do note at the time the opp was created, what was the 6QA status of the account: yes or no?

I think if you were to create only one field, it would be 6QA Status = Yes or No.

That way, your reporting would be held in time and you'd know the 6QA status on the account the moment the opp was created. Once opps get created, accounts can and likely will fall out of 6QA (at least in my experience) so going back in to do reporting some days later can upend your metrics, especially if you're exporting scores to accounts daily. Those numbers change all the time so having a "stamp" that does not change is a great thing to have.

Taylor Matysik · May 2024

@CarlyShideler Props to your SF admin for being hesitant to add a new field. They're ultimately looking out for the best interests of the business and scaling over time.

I think a good question to ask yourself/your team is, "how do we want to use this information and what value will it bring to people engaging with the opportunity object in SFDC?"

If you can't answer that question probably best to hold off on adding the field.

We use it on the account object to indicate accounts in the pre-opportunity stage to flag "low-hanging fruit" to our XDRs and AEs.

6QA stamp on opp - what ways do you use this?

Comments

Upcoming Events

Categories