Creation of new Quote to Cash Job Family
Why is this change being made?
This MR is creates a new job family within Sales Operations: a single owner of the Quote to Cash Buyer & Seller Experience to Iterate towards a common Q2C roadmap, set of processes and expectations for delivering a quality Buyer/Seller experience and ultimately more Efficient Results.
As our business grows in scale and complexity, our Quote to Cash process is spread across multiple tools, processes and departments. Without a communal owner/advisor of this entire process, the experience of our Buyers AND Sellers of GitLab suffers. This role reports in the Sales Operations group since the majority of the Buyer/Seller experience is concentrated in our processes, however the nature of this role will require strong Collaboration across multiple (if not most!) teams at GitLab. This role requires a very strong background in the tactical and technical aspects of our Q2C stack as well as strong Communication skills.
Author Checklist
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.