Skip to content
Snippets Groups Projects

Arranging customer conversation on EE feature requests

Merged Chad Malchow requested to merge feature_request_sales into master
3 unresolved threads

Suggested process for sales and product to work together to collect customer needs on EE feature request. This need came up via a conversation in this issue, https://gitlab.com/gitlab-org/gitlab-ee/issues/1187, with @victorwu and myself.

Edited by 🚄 Job van der Voort 🚀

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
300 300 If you hear a feature request from a customer, you should follow the normal
301 301 procedure: you create an issue, label it correctly. Let's say the customer requests an enhancement to Issues. You know by reading above that you'll have label this with `Discussion` and you can mention or reach out to Victor to expedite this if warranted.
302 302
303 Salesperson for organizations asking for Enterprise Edition feature request, shall work with product manager to arrange conversation to further explore feature request and desired outcome. The process will be:
304
305 * Sales schedules 1 hour zoom meeting with product manager, customer and themselves. Call recorded if customer gives permission.
306 * Product Manager creates any addiotnal questions beyond what is below, they would like answered
  • Victor Wu
  • 300 300 If you hear a feature request from a customer, you should follow the normal
    301 301 procedure: you create an issue, label it correctly. Let's say the customer requests an enhancement to Issues. You know by reading above that you'll have label this with `Discussion` and you can mention or reach out to Victor to expedite this if warranted.
    302 302
    303 Salesperson for organizations asking for Enterprise Edition feature request, shall work with product manager to arrange conversation to further explore feature request and desired outcome. The process will be:
    304
    305 * Sales schedules 1 hour zoom meeting with product manager, customer and themselves. Call recorded if customer gives permission.
    • If sales can give the product manager a link to the customer in SFDC as part of the pre-meeting planning, then the PM can probably quickly see where the customer is at in the funnel, see some previous notes/engagements/meetings, and should be able to come up with a pretty good set of questions.

    • Please register or sign in to reply
  • Victor Wu
  • 301 301 procedure: you create an issue, label it correctly. Let's say the customer requests an enhancement to Issues. You know by reading above that you'll have label this with `Discussion` and you can mention or reach out to Victor to expedite this if warranted.
    302 302
    303 Salesperson for organizations asking for Enterprise Edition feature request, shall work with product manager to arrange conversation to further explore feature request and desired outcome. The process will be:
    304
    305 * Sales schedules 1 hour zoom meeting with product manager, customer and themselves. Call recorded if customer gives permission.
    306 * Product Manager creates any addiotnal questions beyond what is below, they would like answered
    307 * What version of GitLab are you currently using? CE / EES / EEP?
    308 * How are you currently doing source code management? GitLab merge requests or another tool? How about CI/CD?
    309 * How are you currently doing issue management? How are you using HP ALM? Agile/Kanban? What do your sprint/iterations look like? 1 week? 1 month? 2 months?
    310 * What is the integration like between issue management and source code management?
    311 * How do teams manage multiple repos? Does a team typically work on repo at a time? Or do they work on multiple repos at the same time?
    312 * Sales sends questions to customer prior to meeting.
    313 * Meeting is created in Salesforce.com
    314 * Sales creates a google document for notes from call with customer. Google Doc shared with product manager and sales manager
    315 * Sales and product manager schedule 15 minute pre-meeting to share what we know about the customer thus far as not to waste time asking questions we already know the answer to. Notes from this pre-meeting are added to the google document.
    316 * Sales adds a link to the google document under the account object as a note.
    • Should we specify any follow-up steps post-meeting?

      Typically I end up sending docs and issue links to the customer, cc-ing the sales rep. And I create / update any issues that need to be. Maybe this is so obvious it doesn't need to be documented.

    • Please register or sign in to reply
  • 🚄 Job van der Voort 🚀 unmarked as a Work In Progress

    unmarked as a Work In Progress

  • mentioned in commit 60f73095

  • Please register or sign in to reply
    Loading