Snowflake Partner Network (SPN) Registration Form - Complete Reference

Purpose: Complete reference guide for all SPN registration form questions and available options
Last Updated: January 22, 2026
Use: Reference when registering deals in Snowflake Partner Network


Form Structure

The SPN registration form is a multi-step process with the following sections:

  1. Customer Info (Step 1)
  2. Engagement Details (Step 2)
  3. Form Confirmation (Step 3)

Step 1: Customer Info

Required Fields

Customer Company Name*

  • Text input field
  • Example: EY or Ernst & Young

Customer First Name*

  • Text input field
  • Example: Claire

Customer Last Name*

  • Text input field
  • Example: [Customer’s last name]

Customer Work Title*

  • Text input field
  • Example: Partner, Executive Partner, Managing Director

Opportunity Description and Details*

  • Large text area
  • Should include: Problem statement, Brainforge’s solution, key differentiators, scope, territory

Customer Use Case*

  • Multi-select from available options:
    • Data Engineering
    • Platform
    • AI
    • Analytics

Customer Website*

  • Text input field
  • Example: ey.com

DUNS#

  • Optional text input field
  • Leave blank if unknown

Customer Company Email*

  • Text input field
  • Customer’s email address

Work Phone*

  • Text input field
  • Customer’s work phone number

Company Address Type*

  • Dropdown selection
  • Options: USA, [Other countries]

Street Address 1*

  • Text input field
  • Customer’s primary office address

Street Address 2 (Optional)

  • Text input field
  • Additional address information

City*

  • Text input field
  • Example: Dallas, Houston

State*

  • Dropdown selection
  • Example: Texas

ZIP Code*

  • Text input field
  • Customer’s ZIP code

Step 2: Engagement Details

Services to be Provided*

Type: Multi-select (Available Options → Selected Options)

Available Options:

  • Advisory
  • Implementation
  • Led Workshop
  • POC (Proof of Concept)
  • Referral
  • RFP (Request for Proposal)

Typical Selection for Brainforge: Implementation (primary), potentially Advisory or POC depending on engagement type


Will the opportunity lead to a new capacity contract between Snowflake and the end customer or is this an existing Snowflake customer that will draw down from an existing Snowflake capacity contract?*

Type: Required dropdown

Options:

  • [Dropdown menu - specific options not fully visible in image]
  • Likely includes: “New Customer”, “Existing Customer”, “Expansion”, etc.

For EY: Likely “Existing Customer” since EY has MSA with Snowflake already


Predicted Total ACV (USD)*

Type: Required text input

Description: “Snowflake’s Anticipated ACV for Referral and Engagement Registrations”

Guidance: Enter the total Annual Contract Value Snowflake expects from this opportunity


Predicted First Contract Size*

Type: Required text input

Default Value: $50,000.00

Guidance: Enter the size of the first contract/initial purchase


Product Edition*

Type: Required text input

Default Value: Enterprise

Options: Likely includes Standard, Enterprise, Business Critical, etc.


Intended Channel*

Type: Required dropdown

Options:

  • Direct
  • Resell
  • MSP (Managed Service Provider)

Typical Selection for Brainforge: Direct (we’re the implementation partner, not reselling)


Customer Existing Data Warehouse Tool

Type: Multi-select (Available Options → Selected Options)

Purpose: Identify the data warehousing solutions the customer is currently using

Available Options (partial list):

  • Actian: Cloud Data Wa... (truncated)
  • AWS: Athena
  • AWS: EMR
  • AWS: Redshift
  • Cloudera: CDP
  • Cloudera: HDP
  • [Additional options likely available in full list]

Selection Guidance: Select all tools the customer currently uses. For EY, this would depend on their current tech stack.


Customer BI Tool

Type: Multi-select (Available Options → Selected Options)

Purpose: Identify the business intelligence tools the customer currently utilizes

Available Options (partial list):

  • Birst
  • Business Objects
  • Chartio
  • Domo
  • Excel
  • GoodData
  • [Additional options likely available in full list - likely includes Tableau, Power BI, Looker, etc.]

Selection Guidance: Select all BI tools the customer uses. For EY, this would depend on their current analytics stack.


Customer ETL Tool

Type: Multi-select (Available Options → Selected Options)

Purpose: Identify the Extract, Transform, Load (ETL) tools the customer is currently employing

Available Options (partial list):

  • Abinitio
  • Alooma
  • Alteryx
  • Azure Data Factory
  • Confluent/Kafka
  • Dell Boomi
  • [Additional options likely available in full list - likely includes Informatica, Talend, Fivetran, etc.]

Selection Guidance: Select all ETL tools the customer uses. For EY, this would depend on their current data pipeline tools.


Customer Data Science Tool

Type: Multi-select (Available Options → Selected Options)

Purpose: Identify the data science platforms or tools the customer uses

Available Options (partial list):

  • Alteryx
  • AWS Sagemaker
  • C3.ai
  • Databricks
  • Dataiku
  • DataRobot
  • [Additional options likely available in full list - likely includes Jupyter, R, Python platforms, etc.]

Selection Guidance: Select all data science tools the customer uses. For EY, this would depend on their current ML/AI stack.


Should Snowflake contact you or the listed Customer first? (Initial Contact)*

Type: Required dropdown

Options:

  • Partner (Brainforge)
  • Customer (Direct to customer)
  • [Possibly other options]

Typical Selection for Brainforge: Partner - we want to coordinate the introduction and ensure proper positioning


Step 3: Form Confirmation

Purpose: Review and confirm all entered information before submission

Actions:

  • Review all entered data
  • Submit registration
  • Cancel if needed

Common Patterns for Brainforge Registrations

Typical Service Selection

  • Primary: Implementation
  • Secondary (if applicable): Advisory, POC

Typical Channel Selection

  • Most Common: Direct (we’re the implementation partner)

Typical Initial Contact

  • Most Common: Partner (we coordinate the introduction)

Product Edition

  • Most Common: Enterprise (default, appropriate for most enterprise customers)

Notes for Future Registrations

  1. Customer Info Section:

    • Always confirm exact customer contact details before filling
    • Use full company name if different from common abbreviation
    • Include territory/region in opportunity description
  2. Engagement Details:

    • Be specific about services - select all that apply
    • ACV should reflect Snowflake’s expected revenue, not Brainforge’s
    • First contract size should be realistic initial purchase
  3. Tech Stack Questions:

    • Research customer’s current stack before registration
    • Select all relevant tools (multi-select allows multiple)
    • If unknown, can leave blank or select “Unknown” if available
  4. Initial Contact:

    • Choose “Partner” to maintain control over introduction timing
    • Coordinate with Snowflake AEs before customer contact

  • Strategic Plan: If archived, link from knowledge/plans/ or the partnerships folder; avoid machine-local .cursor/plans/ paths in shared docs.
  • Steve’s Meeting Insights: 01-steve-meeting-insights.md
  • Partner Playbook: ../partner-playbook.md
  • Rep Engagement Playbook: ../rep-engagement-playbook.md

Last Updated: January 22, 2026
Maintained By: GTM / Partnerships Team