Handbook Update for: 1) GitLab Legal Stamp for documents to be signed, and 2) Request for "Vendor Setup" Forms
@jhurewitz @pmachle @daleb04 @jbraughler @james_harrison
This MR is to update the Sales Operations Handbook to highlight:
- As of November 18th, 2019, all contracts that require GitLab countersignature will be digitally stamped, by a Contract Manager or legal representative, to signify that it has been reviewed and vetted by our legal department. a. There is no change to the signature process itself. Instead, once the parties reach a ‘clean’ document, the GitLab Contract Manager or legal representative, will insert the digital stamp below the signature line/box where GitLab is required to execute. This will be the version that is processed for signature by the parties. b. For those that execute on behalf of GitLab, we should reject any Agreement that does not have this stamp. c. Sales will be advised to ensure the final “Clean” version of the Agreement has the stamp prior to submitting for signature. d. This process has been discussed with @jbraughler, and will be placed in the Contract Manager onboarding / playbook documentation that is being created.
@james_harrison @dhong To be clear, we are not changing any steps for our sales reps. Instead, the contract manager / legal team members will simply ensure that our final version(s) include the 'stamp' on contracts/agreements that require GitLab signature. I'm happy to present this change on the WW sales call if you all feel it necessary.
- We are seeing increased requests to complete customer “Vendor Forms”. We’ve updated the process in the handbook to ensure our Sales Team Members understand who do engage and how to address this information. a. Of note, we clarify that any terms in these Vendor Forms will be reviewed and potentially removed by GitLab Legal
Edited by Robert Nalen