During the Growth team [fast boot](https://about.gitlab.com/handbook/engineering/development/growth/fast-boot/) in Vancouver we uncovered a handful improvements that could be made to version.gitlab.com this epic encapsulates the work we did to complete those improvements. ## Problem Our internal customers from Sales and Account management did not have an easy way to quickly find basic usage information on the accounts they manage e.g. seat used vs seats licensed We did conduct internal customer interviews to identify this opportunity here are the problem demos we were able to act on (thank you @bdowney) * P1: Self-hosted [usage for upsell process and user workflow](https://drive.google.com/open?id=1tqS54h3HpBrZqOYZXeFCBk8pXDx5D4cg) * P2: Self-hosted [True-up process and user workflow](https://drive.google.com/open?id=1vtQ1dNkFDVUNdxxEmSx6Pe8Y8IucTfVX) ## Solution We are solving this by doing 2 things 1. Exposing as much of the information we can via periscope in [this dashboard](https://app.periscopedata.com/app/gitlab/511474/WIP:-Overused-Licenses) 1. Improve version.gitlab.com and license.gitlab.com Update version.gitlab.com's host page with an updated table that enables internal customers to quickly identify accounts that have either used more seats **or** have not used the full amount of seats they originally signed up for. ## Issues, MRs and Contributors ##### DATA Issues: * https://gitlab.com/gitlab-data/analytics/issues/2593 ##### Growth Issues: * https://gitlab.com/gitlab-org/growth/engineering/issues/24 * https://gitlab.com/gitlab-org/growth/engineering/issues/26 * https://gitlab.com/gitlab-org/growth/engineering/issues/33 * https://gitlab.com/gitlab-org/growth/engineering/issues/34 * https://gitlab.com/gitlab-org/growth/engineering/issues/35 #### Version issues: * https://gitlab.com/gitlab-services/version-gitlab-com/issues/165 * https://gitlab.com/gitlab-services/version-gitlab-com/issues/187 * https://gitlab.com/gitlab-services/version-gitlab-com/issues/186 * https://gitlab.com/gitlab-services/version-gitlab-com/issues/188 #### Infrastructure Issues: * https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/8035 * https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/7961 ##### Merge Requests: * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/212 * https://gitlab.com/gitlab-org/gitlab/merge_requests/18095 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/205 * https://gitlab.com/gitlab-org/gitlab/merge_requests/17717 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/218 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/215 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/216 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/217 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/213 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/214 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/211 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/202 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/207 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/210 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/204 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/199 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/208 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/193 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/200 * https://gitlab.com/gitlab-org/version-gitlab-com/merge_requests/209 * https://gitlab.com/gitlab-org/license-gitlab-com/merge_requests/107 * https://gitlab.com/gitlab-services/version-gitlab-com/merge_requests/206 * https://gitlab.com/gitlab-services/version-gitlab-com/merge_requests/224 ##### Teammates contributing: @dstull @jackie_fraser @eli_kastelein @pcalder @bmarnane @bdowney @brendan