I don't have time right now
1. Pushback - Acknowledge, Mongo as the DB is a pretty important piece of the environment of clients I work with - is there some better time next week?
2. How about just 15 minutes to get a high level overview so if something does come up - you know where to engage?
We have a lot of experience with MongoDB
1. Great to hear, how long have you guys been working with it?
2. Which certifications do you guys hold with MongoDB?
3. Has there ever been a time where you didn't know the answer to something in MDB?
Our customers have strict requirements around security, so we can't use a managed service
1. What types of customers do you guys have?
2. What are they're security requirements?
3. How do they feel about their data living in AWS?
4. How are you guys adhering to their security requirements today?
Let's talk in 6 months
1. Acknowledge, let's spend just 15 minutes then, just incase something comes up in 3 months where this information can help the team get over a potential challenge
We're on MongoDB 3.4
1. Why are you on an unsupported version of MongoDB?
2. When is the last time you guys upgraded the DB?
Atlas is too expensive
1. How do you know Atlas is too expensive?
2. Why do you think it's too expensive, and what are you basing that on?
1. The question we always need to be asking is why - oh why is MongoDB not important?
2. Is there someone else that handles MongoDB more hands on?
3. Is the application MongoDB's supporting not critical to the business?
Let me take a look at this over the next few days
1. Why would you spend time figuring this out on your own, when you could be focused on X priority?
2. Why clean your room before the maid comes?
3. I'm sure you/your team is intelligent enough to figure this out on your own, but why spend time there when you can get it fully optimized from one of our engineers in less time with supporting documentation specific application?
We've built our own scripts to manage MDB
1. How are you guys maintaining this today?
2. How many engineers support those scripts?
3. What happens if that engineer leaves the company?
4. How much time is that engineer spending maintaining, patching, and securing the environment?
MongoDB is working great
1. Super glad to hear that, what are you planning to do with MongoDB as you scale?
2. How do you guys make sure MongoDB is in a healthy state?
3. How do you plan on addressing more strict customer requirements around security and locality as you grow?
We don't have the time or resources to deal with this
1. What else are you focused on?
2. What are your other priorities for the year?
3. Where does this fall in your priorities?
4. Would XYZ problem you mentioned help with XYZ initiative?
It just works
1. What have you guys done to make sure that it works well?
2. What happens if an issue in MDB comes up that you don't know how to fix?
3. What happens if part of your engineering team leaves the company?