Streaming Projects

🧠 Free Recall ❓ Quiz 🔍 Cues 🔮 Simulation 🥷 ShadowBox 📐 Encode Cards

In a consumption world, new use cases and associated workloads are the pipeline for future revenue and growth.

Our best account teams manage their customers this way, and our Customer Growth GTM Model - built over the last 2 years based on their best practices - reflects this.

But our systems & operating cadences are misaligned and continue to focus only on the pipeline for commits. Streaming Projects brings our systems & cadence in alignment with best practices.

Use Case - Describes how organizations can use Confluent’s data streaming platform to address a specific technical and/or business challenge. Key attributes include identifying what business problem our customers are trying to solve , who cares about it, why it is important to the organization (business value), and when the change is expected to happen.

Workload - This is the collection of streaming capacity, resources, configuration & architecture that delivers the functionality to a technical implementation.

Streaming Project - The Salesforce object that will track the use case & workloads to connect these two concepts.

Use Case --> Why / Workload --> What - January 11, 2024 @ 8:10 AM

Streaming Projects
Introduces ability to track current and future revenue potential regardless of usage vehicle (PAYG, commit) at all stages in the customer lifecycle. Qualification of workloads occurs on the Streaming Project Object

Phases of Streaming Projects
Blue Sky - Customer is a target customer for a use case, but they have not yet agreed to implement or place into a backlog queue. Goal: Help Forecast TAM
Validate - Use Case has been identified by the customer, but is future state and not yet budgeted or planned. Goal: Identify Use Case
Scope - Qualify Use Case and Workload. Uncover business need, urgency and/or compelling event with a planned date and aligned budget.
Design - Design Workload. Prove technical win, demonstrate competitive differentiation as needed.
Implement - Streaming Project is not yet in production, but is backlog, under development or active in a pre-production or test environment.
Production - Streaming Project is in Production and actively maintained, enhancements and expansions ongoing.
Decommissioned - Streaming Project is no longer active. Has been deprecated or abandoned.

Streaming Project Name - Project name. Hint: Choose a title that will enable you to distinguish between the many streaming projects you'll have aligned to 1 account.
Confluent Phase - Where the streaming project sits in relation to deployment on Confluent and Confluent's path to revenue. See here for definitions of each phase.
Customer Status - Where the customer's project is in the SDLC (Software Development Life Cycle), irrelevant of Confluent. See here for definitions of each status.
Risk Status - Likelihood for the project to move into production or commit
Primary Stakeholder - Point of contact for the Streaming Project, who you are primarily engaging with. You can add additional stakeholders under "related" tab of your Streaming Project.
Cloud Org ID - Customer's Confluent Org ID. Should be the Org where they plan to build out the use case associated with this streaming project.
Business Outcome - Key business outcome the customer is looking to achieve by implementing Confluent solutions.
Business Use Case - Strategic business initiative to which Confluent can tie our solutions to.
Streaming Patterns - Key technical solution the customer is looking to implement with Confluent.
Technical Use Case - Strategic IT initiative to which Confluent can tie our solutions to.
Confluent Offering - Cloud, Hybrid, or Platform solution that Confluent is proposing.
Current Usage Vehicle - If the project is already in production, where is it? OSK, MSK, etc.
Monthly Consumption Once Ramped - Estimated montly spend once use case is fully ramped. Spend is based on T-shirt sizing. This can be $0.00 upon creation of Streaming Project but MUST be filled in at the Scope phase.
Go-Live Date - Predicted date in which the streaming project will move into production
Ramp Date - Date streaming project will be fully ramped.
Funding Confirmation - Date funding for streaming project is confirmed.
Technical Success Plan - SE to insert link to technical success/implemenation plan
Reference Architecture - SE to insert link to reference architecture model created during design phase
Competitor - Primary competitor considered for implementation of the project (could be existing vehicle)
Other Competitor - Any other competitors considered or not listed in the competitor drop down.
Decommissioned Date - Date at which the streaming project has been or will be deprecated or abandoned
Notes - Provide status updates, share info amongst account team members & track info not captured in other fields

Unstarred

Dunk (exclude from study)

Streaming Projects

Review Questions

Todos

Sensemaker