1/9
These flashcards summarize key negotiation levers and important concepts related to MongoDB ISV partnership agreements.
Name | Mastery | Learn | Test | Matching | Spaced | Call with Kai |
|---|
No analytics yet
Send a link to your students to track their progress
What are Atlas Credits in MongoDB ISV partnerships?
Limited time-bound credits offered for development, migration, or early production to reduce switching risk.
What does Technical Validation and Architecture Review provide?
Formal architecture validation and performance guidance to de-risk scale and enterprise readiness.
What is the 'Powered by MongoDB' designation?
A brand usage grant that enhances ecosystem visibility and helps ISVs build trust with customers and investors.
What is meant by Priority Access in MongoDB ISV partnerships?
Offering faster escalation paths, roadmap visibility, or early access to features important to the ISV's workload.
What does the Startup-to-Scale Graduation Path entail?
A defined progression from early ISV status to Tier 2 or Tier 1 with increased support as consumption grows.
How do Reference Architectures and Templates assist ISVs?
They provide proven patterns for building applications, reducing build time in multi-tenant SaaS, AI workloads, or regulated industries.
What is Joint Customer Validation in the context of MongoDB ISVs?
Support for pilots or lighthouse customers to demonstrate production readiness and encourage adoption.
What benefits does Ecosystem Distribution offer ISVs?
Inclusion in MongoDB’s partner ecosystem to increase visibility to Atlas-first customers.
What is the purpose of Migration Support in an ISV agreement?
To provide guidance and tooling for moving from another database to Atlas without service disruption.
What should not be led with in MongoDB ISV negotiations?
Permanent discounts, revenue share, heavy go-to-market commitments, and custom pricing.