Skip to content

Partner referral rebate guideline updates

David Mauer requested to merge david.mauer-main-patch-226b into main

Why is this change being made?

: We have discussed the topic in Slack -

Hi @dmauer and @Marcella Summers, need your help on a couple referral rebate related items. Ed, Patty, and I connected with Finance re: rebate exception for a prior Q deal, and aligned on adding some protections to our program documentation. Here's the conclusion from that convo, and see below for details:@dmauer could you please assist with program documentation updates in program guide, programs handbook, and any other applicable assets? Happy to chat through this live to provide additional details and/or review async@Marcella Summers the PY rebate request is now approved. Let's add to the exception list for this quarter. I added an agenda item to our Wed 1x1 to discuss how we'll update the opp and comm this back to the teamPlease let me know if any questions. Thanks all

Robert

Hi @Nick Scala and @Ed Cepulis! After chatting through this with the rest of the team, we are able to fund the exception for the $26k rebate to the partner under the condition that we update the verbiage to the partner program prior documentation to protect ourselves from more of this in the future first. I believe we chatted through these two components, but let me know if I am misinterpreting the notes from earlier this week:

  1. Deal Regs should be in Vartopia prior to Q end to qualify for a rebate
  2. Adding cutoff for number of days past a quarter ends for the partners to be able to dispute any rebates (e.g. if we pay out within 45 days, 15 days after that to dispute)

). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

CHANGEME

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Division: If the update affects your division, share the MR in your division Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Commits

  • Update file index.md

Merge request reports