The kick-off may be handled as part of the Welcome to GitLab call orchestrated by the GitLab Customer Success Manager. However, many times the implementation kick off will be an on-site engagement or one handled directly by the Professional Services Engineer. This template is for use in those cases.
After the SOW, or a specific Milestone has been successfully delivered and completed, the customer will need to sign a Project sign off document. This should be sent by the Project Manager. To send a Project Sign off document:
Create a Project sign-off document for the Project or Milestone, based upon the Project Sign off template
Create an email using the message below and attach the new Project sign off document
Add the recipient who will be signing the document to the email and CC yourself and the PS Operations Manager
Update subject line to “[customer name]- project sign off
Send the email
Dear [Signer],
Attached you will find the project sign off documentation for your GitLab Professional Services Statement of Work.
Please sign the document and return at your earliest convenience. Alternatively, you may reply all with the word "accepted" and that will be accepted as sufficient approval as well.
If you have any questions, please feel free to reach out to let me know.
Thank you,
[your signature]
Once you receive the Project Sign off, via signed document or email acceptance, or passive acceptance, you’ll need to follow these steps to process in Mavenlink
This welcome e-mail will be sent by the Manager, Professional Services to introduce the customer to our Professional Services Engineering team and the concept of a GitLab implementation.
E-mail Template
Dear [Main Contact],
Let me add my welcome to GitLab, and extend our sincere desire to ensure that your GitLab implementation process is smooth and efficient, resulting in a system that will benefit your workflow, your software delivery process and thus your business. We look forward to working with [Customer Name] to make this project a success!
The most important next step in our process together is to identify key personnel on each side that will be dedicated to this project. Over the coming days, I will be working to identify a member of our dedicated Professional Services Engineering team to be the project lead for GitLab for your implementation. The GitLab Professional Services Engineer will work closely with the members of your team that will be working on this project.
The team members from [Customer Name] that will need to be identified to kick off the project include:
* GitLab Champion - this individual will be the champion for GitLab at your organization
* A GitLab Administrator(s) – this user or users will be the key lead for implementation decision making, system build, system management and aiding in coordinating resources from [Customer Name].
* Technical POC - this user or users will help the GitLab Professional Services Engineering team gain the necessary technical resources and access to aid your team in the GitLab implementation.
* Additional Stakeholders - please also identify any other stakeholders such as business and product stakeholders.
My team and I look forward to working with the team at [Customer Name], and we'll be in touch soon!
XXX XXX
Manager, Professional Services
GitLab
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
Cookie Policy
User ID: 30bbe583-183d-46fe-944f-c17bd59ab899
This User ID will be used as a unique identifier while storing and accessing your preferences for future.
Timestamp: --
Strictly Necessary Cookies
Always Active
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, enabling you to securely log into the site, filling in forms, or using the customer checkout. GitLab processes any personal data collected through these cookies on the basis of our legitimate interest.
Functionality Cookies
These cookies enable helpful but non-essential website functions that improve your website experience. By recognizing you when you return to our website, they may, for example, allow us to personalize our content for you or remember your preferences. If you do not allow these cookies then some or all of these services may not function properly. GitLab processes any personal data collected through these cookies on the basis of your consent
Performance and Analytics Cookies
These cookies allow us and our third-party service providers to recognize and count the number of visitors on our websites and to see how visitors move around our websites when they are using it. This helps us improve our products and ensures that users can easily find what they need on our websites. These cookies usually generate aggregate statistics that are not associated with an individual. To the extent any personal data is collected through these cookies, GitLab processes that data on the basis of your consent.
Targeting and Advertising Cookies
These cookies enable different advertising related functions. They may allow us to record information about your visit to our websites, such as pages visited, links followed, and videos viewed so we can make our websites and the advertising displayed on it more relevant to your interests. They may be set through our website by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant advertisements on other websites. GitLab processes any personal data collected through these cookies on the basis of your consent.