Self-hosted trial flow design
Problem
As a user, signing up for a trial is an overly complicated process. If I am interested, I have to create a new account on customers.gitlab.com. I am not sure what why that account is necessary or how my information given to set up that account is going to be used.
As a GitLab team member, the only insight that I have into the users signing up for a self hosted instance is by viewing the information that users provide when signing up for a trial. Because we do not know where users downloaded their instance from or how they were introduced to GitLab, it is important to introduce them to the full value that GitLab provides as soon as they spin up their instance.
Designs
- Wireframes and user flow in Mural
- See designs in design tab
- Prototype
- Detailed specs in Sketch Measure
Requirements
- The first time an administrator logs into GitLab they should be given the option to sign up for a Gold trial after their account is created and their profile is complete (if their instance has access to the internet)
- Presents the features of the Gold trial with a CTA of signing up for a trial
- Allows a user to enter their trial key if they already have one
- Allows the user to skip the trial signup process
- If the user elects to signup for a trial, the user fills out first name, last name, work email address, company name, phone number, country, total number of employees, "do you have any initial questions?"
- Adds the trial key retrieved from the API to the users instance and informs the user of their trial expiration date
Edited by Emily Sybrant