What changes in the day-to-day work?
GitLab's customer-success handbook focuses on adoption and customer outcomes; its support handbook describes technical assistance. A smaller team may combine the two, so ask how the internship divides planned account work and incoming requests.
| Work dimension | Customer success | Support |
|---|---|---|
| Problem | A department is not completing the workflow it bought | A request disappears when the user changes departments |
| Useful investigation | Find the adoption obstacle and the person who can resolve it | Reproduce the failure and isolate the conditions |
| Possible output | An account plan with an owner and next action | A reproduction note, escalation or tested help article |
Measure the customer's task, not just logins
Suppose three departments need an approval workflow before a reporting deadline. The customer owns 100 seats, but ten coordinators might do all the required work. Ten effective users could meet the objective; a high login count would not prove that the reporting cycle works.
Write: ‘Department B has not completed an approval cycle because its coordinator cannot configure the final step. Next action: the implementation owner tests the configuration with the coordinator.’ That is more useful than an unexplained red account-health label.
Make a support handoff reproducible
For the disappearing-request problem, record the steps, expected behavior, actual behavior and relevant version. Separate what the user reported from what you reproduced. Include the business consequence: the failure blocks the department's reporting deadline.
Practice on a fictional system or your own project. A good sample contains a clear reproduction and a tested resolution or escalation. It does not need private customer messages, credentials or account records.
Example: 105% revenue retention can coexist with customer losses
A fictional business begins the year with ten customers and $100,000 of annual recurring revenue. Two customers representing $8,000 leave. Continuing customers reduce subscriptions by $5,000 and expand by $18,000. Follow only the starting customers; exclude revenue from new customers.
| Measure | Calculation | Result |
|---|---|---|
| Customer retention | 8 / 10 | 80% |
| Gross revenue retention | ($100,000 − $8,000 − $5,000) / $100,000 | 87% |
| Net revenue retention | ($100,000 − $8,000 − $5,000 + $18,000) / $100,000 | 105% |
Expansion outweighs the lost revenue, but two customers still left. The figures do not explain why they left or prove that any customer-success activity caused the expansion. Keep those questions separate from the calculation.
Choose a sample that matches the internship
For customer success, prepare the account plan and explain one adoption obstacle. For support, write the reproduction note and have someone follow your help article without spoken assistance. Show the revision you made after they got stuck.
Ask the manager how much time involves tickets, onboarding, analysis and customer meetings, and who reviews an intern's work. A mixed role may be useful, but you should know what mix you are accepting. Describe your sample at its actual scale rather than claiming ownership of a renewal or enterprise account.