Skip to content

CustomersDot upgrades: weekly historical table

Problem to solve

Similar to &5872, the Sales team needs access to historical license utilization data.

Intended users

As a Sales Rep, I need to quote my customer for their renewal or coterm. To do it effectively, I need to know their max_historical_user_count and billable_user_count not just for today, but for the preceding 3-12 months. This is important as customers will tend to add/remove licenses, especially drastically cut licenses right before the renewal to make it look smaller. I need to have the confidence to quote them what's fair to them and fair to GitLab.

Requirements:

  1. Weekly snapshot data
    1. max_historical_count
    2. billable_user_count
  2. It must tie exactly to the Customers Portal so we avoid quoting the customer inaccurate amounts; specifically, "as a Sales Rep, I need my quote to match what the customer sees in their Portal"
  3. Reporting types - shows usage for last 12 month
    1. Tabular (week | billable_user_count | max_historical_user_count |
    2. Trend line visualization using the tabular data above, and graphed week-over-week with current and max historical count
  4. V2: Reporting asks
    1. Ability to set date fields to run the tabular and trend so I can look at a specific date range (i.e., "2021-07-01 TO 2021-10-31")

Further details

Needs to apply to both self-managed and SaaS subscriptions.

Permissions and Security

Sales currently has read-only access to CustomersDot, so this will suffice.

Documentation

Availability & Testing

What does success look like, and how can we measure that?

Success metrics:

  1. Faster and accurate quoting because the rep understands the current and projected needs of the customer
  2. Less back and forth with the customer, and no more asking the customer for screenshots (unless in an offline instance)
  3. Better customer experience
  4. Increased rep productivity because less time is spent in cumbersome processes looking at multiple sources
  5. CustomersDot can be the SSOT for the true and accurate license count

What is the type of buyer?

Is this a cross-stage feature?

Conditional release requirements

How should this feature impact existing customers?

Billing constraints or considerations

Links / references

This work is dependent on grouputilization shipping work outlined in &5872 first. The in-app, database accounting and BE work needed to present the data in a timeline.

Communication Plan

  • PM to put together a message about the change
  • PM to communicate changes to CS Ops
Edited by Teresa Tison