A few thoughts on MDB

Based on optics alone, I think MDB has a better than average chance of going down the next few quarters.

The reasons I believe that are the following:

*It was a great quarter, but guidance was muted
*Tough comparisons in Q3/Q4
*Atlas growth will impact revenue negatively as it is usage based and much less revenue is recognized upfront (a reason for the guidance)

Reasons why I don’t care as of today are the following:

*Last Q4, management recognized usage beyond normal workloads. Guidance does not assume that will occur again. I tend to think it will.
*Even if revenues are decreased in the short term, the Atlas model is obviously working as evidenced by growth rates since inception.
*Non-Atlas is still growing at a healthy clip.
*MongoDB appears to be THE leader in the space with an enormous advantage currently.

Until this quarter, I didn’t realize the impact on revenue that Atlas will have, but it is only short term. In fact, a lower stock price would be welcome in my opinion.

This is just how I see the company today at around 8% of my portfolio. I will be happy to add if the market dislikes the next few quarters and the rest stays the same.

My plan is to see how the stock trends before the next earnings report. If it dips significantly, I will buy a bit more. If it stays relatively flat from where it is now, I will likely wait for more information from the next report to see if the current trend continues.

A.J.

19 Likes

We’ve had a few discussions on Atlas consumption based Billings and the seasonality of Q4.

https://discussion.fool.com/clearly-there-was-seasonality-in-q4-…

In that thread Bear predicted 67% growth for Q2, shacked it!

Q3 last year had a large 606 correction of over $6M dollars for a 606 adjusted revenue of $71.78M. This was due to one or more large multi year Enterprise(on prem) deals which the new accounting required them to recognize more upfront.

I too am concerned about the headline coming for Q3.

For the coming quarter they guided to $100M on top line. At face value that’s 39% growth. If they have a typical beat of $7M, that’s 49% growth. That less than 50% realistic expectation will at a minimum put some short term pressure on MDB, in my opinion.

Out to Q4, Mongo is likely to see an enhanced seasonal impact to Atlas consumption because Atlas will be much bigger overall. If the theory about Atlas Q4 is correct. If that pans out Mongo could have a very strong Q4 with acceleration over Q3.

I reduced my position some, but still strongly believe in Mongo’s position for long term growth. May be some good opportunities to add back to it.

Darth

6 Likes

I tend to agree. I respect Saul’s opinion that guidance should be taken with a grain of salt. That said, we can look at past guidance vs actual results to get some insight into what we can expect. In the first table below, I show the revenue guidance vs actual revenue for the last couple years, taking into account the switch from 605 to 606. The average beat is 108% (i.e. an +8% beat). The best is 112%.


	Qrtr	Guide	Actual	% +/- 	YoY growth
605	4Q 18	43	45	106%	-
605	1Q 19	47	48	104%	49%
605	2Q 19	52	57	111%	61%
605	3Q 19	60	65	108%	57%
605	4Q 19	74	83	112%	85%
606	1Q 20	84	89	106%	78%
606	2Q 20	92	99	108%	67%

Last quarter, they issued Q3 and full-year guidance. We can use that to get Q4 guidance. If we then take 112% as a best-case scenario, we can estimate actual Q3 and Q4 revenue, and the YoY quarterly and annual revenue growth rates that guidance implies. In the second table below, I show this i.e. the Q3 and Q4 guidance, and the estimated actual revenue based on the 112% best-case beat (which could obviously be wrong), and also the implied YoY growth rates. The last entry is the annual (FY2020) YoY growth rate. The value is 57%, which compares to 61% annual YoY growth for FY2019. On a quarterly basis (i.e. upcoming Q3 and Q4), it appears we should expect a substantial slow down, potentially to <40% (if we take the average 108% beat, we get 50% YoY in Q3, 34% in Q4, and 54% for FY2020).


	Qrtr	Guide	Estim.	% +/- 	YoY growth
606	3Q 20	100	112	112%	56%
606	4Q 20	106	119	112%	40%
606	FY2020	395	420	106%	57%

One thing you may notice is that by assuming 112% beat in Q3 and Q4, we end up with 106% beat for FY2020. This is because the estimated FY2020 full-year revenue already includes the impact of the +6% and +8% beats in Q1 and Q2, so the impact of the +12% assumed beats in Q3 and Q4 are diluted. If that seems confusing just take my word for it, or feel free to double check my math.

None of this takes into account business-specific details such as what Phoolio brought up. There are other ways of looking at business performance, such as TTM metrics, that would not show as substantial decline, since Q1 and Q2 were such strong quarters. I don’t think any decisions should be made on these estimates alone, but I did personally decide to reduce my Mongo position from ~9% to ~7% after hearing the call, and I may reduce it to 5% (unless the market does it for me first!). I also think I am giving them a larger beat (+12%) than I should. There is a lot of talk about potential cap ex slow down across the market in Q3 and Q4. The question that has been asked in a lot of other posts is how that might affect our companies. The consensus seems to be that this is a benefit i.e. our companies provide mission-critical software that cannot be done without, and depending on the underlying driver of any cap ex slowdown, IT spend on cloud SaaS solutions could even increase, at least relative to other areas. My thinking is that this is mostly relevant to the expand side of the strategy, but what about the land part of the strategy?

One other thing that came up in the call was the anticipated larger than average cash burn in Q3:

“We are pleased with our cash flow performance year-to-date, but expect to burn cash in the third and fourth quarter of fiscal 2020, as we continue to make significant investments in the business. Also given this year’s stronger than expected Q2 cash flow performance, Q2 may not be our peak quarter for negative cash flow, as is typically the case.”

This could add another area of weakness in Q3/Q4. Sorry to sound negative on Mongo, but I think it is worth considering that implied revenue growth is <40% in Q4 without a sizable beat. On the bright side, Non-GAAP operating margin has been trending in the right direction, and as implied by Phoolio, Mongo is a true winner with a massive opportunity ahead. If anything, perhaps the analysis above could be useful as a tool to be a little patient in terms of adding to Mongo, and if you are keen to add, you may get a good opportunity in the next six months!

Let me know what I am missing!

Guy

38 Likes

Just saw Darth’s post. In case of any confusion, the reason I am mixing 605 and 606 is because guidance was issued in those terms. The 71MM rev for 2018Q3 Darth quotes is 606, the 65MM in my table is 605. The growth rates in my tables are on an apples to apples basis i.e. 2019Q1/Q2 are based on back-reported 606, not based on the rev values in my table. Hopefully that makes sense. Also, Darth estimated 49% next quarter based on a “typical beat of 7M”. Pretty close to the 50% rate I came up with using a +8% beat, whereas in the table I used a +12% beat and got 56%. Hopefully they raise in Q3 so my Q4 estimate ends up being low. Probably foolish to go out to Q4 anyway.

Darth, Guy,
I hear you guys on the worries over the reduced guidance, and I fully appreciate the choppiness of MDB over the last 6 months. The weeks of 3/13 and 6/3 have given as all our appreciation. Other than that, MDB has pooped out on us.

https://www.tradingview.com/symbols/NASDAQ-MDB/

I am a long MDB (12.8%) too. Some of the things that I like about MDB are:

  1. I am sure that some of you have a better handle on TAM that I do, but for rough estimates, the total estimated DB market to be about $40B with a 25% growth rate for 2019 and $50B with a growth rate of 22% is predicted for 2020 (p. 6 of Jason Ader report).

https://blocksandfiles.com/wp-content/uploads/2019/03/Databa…

  1. The foundation for Atlas usage is exploiding.

Q2 19 = 5,300 users
Q3 19 = 8,300 users
Q4 19 = 11,400 users
Q1 20 = 12,300 users
Q1 20 = 15,000 users

  1. The relationship with cloud providers remains strong. From the earnings report we get:

Saw growing momentum with all three major cloud providers. The company experienced strong initial traction with GCP in the first quarter of the partnership. MongoDB also expanded its relationship with Microsoft by launching the availability of MongoDB Atlas on the Microsoft Azure Marketplace, simplifying billing for joint customers, and joining Microsoft’s Strategic Partner Reported ACR co-sell program. The company also delivered another record Atlas quarter on AWS.

  1. MDB Revenue as a percentage of the DB market from $346.1MM with a TAM of $50B = 0.7% of the total market.

Given the 95% of the value increase happens during 10% of the trading days with MDB, do you really want to sideline some of your holdings? I totally get the change with the revenue stream changes. I think you are spot on with your view given what management says, but when MDB pops is anyone’s guess. I think that someday MDB will provide the mother of all earnings surprises, and I want to be holding when it does. It still looks good to me. I am sitting tight.

Best,

bulwnkl

66 Likes

MDB Revenue as a percentage of the DB market from $346.1MM with a TAM of $50B = 0.7% of the total market

The entire DB market may not the TAM for MDB, is that correct assumption? If yes, then what is the TAM for MDB?

I think that someday MDB will provide the mother of all earnings surprises, and I want to be holding when it does.

well said…

I agree with concerns raised… however, MDB usage based model is very very attractive and it will be hard for any one to predict quarter to quarter variance…

MDB to me is chance to buy in equivalent of AWS or Azure or GCP… as pure play… yes it will have its own evolution but it is not something you want to step away from too much, specially in a taxable account…

Having said all these, I did reduce from my oversized position at ~20% down to ~15% but that’s just taking off 5% trading allocation…
I fully intend to hold somewhere between 12% to 18% position in MDB for a long time… and portion of that in taxable account to be not touched for 5+ years hopefully…

Another company similar to MDB is TWLO… you never know which quarter usage based bump will show up in a big way… you just have to hold sizable position to benefit when it does…

12 Likes

To be clear I was at about 19% MDB before I reduced my position, so it’s still near the top.

I listened to most of the call and read it. I think they have a playback available.

Listening to the call sounded not nearly as enthusiastic as reading it. The fact that a large Enterprise Advanced deal closed in Q2 that was expected in Q3 also has me tampering my expectations.

So I wanted to reduce my level of exposure. For now.

Darth

1 Like

They have been warning for 3 quarters in a row about the tough comp. coming in the next quarter. The CFO has been going out of his way to mention it specifically in each conference call.

Thus I think they come in under 50% growth this next quarter, and I don’t know how the market will take it. It could already be baked into the stock price.

More risk, so I sold about 1/3 of my position bringing from one of my top holding down to a normal position.

Still love MDB long term.

Jim

1 Like

Hi Kingran,
There would be no way that that DB market is 100% NoSQL, and I have no idea how much of it would be available for MDB. My point is that the TAM for MDB is probably much, much larger than O.7%.

Best,

bulwnkl

4 Likes

I have just pulled some reports, and in optimistic ones also project NoSQL market size by 2024 to be around $5 to $6B. The good news is NoSQL market is expected to grow (CAGR) 30% by 2024. So MDB, should continue to grow at the least at market growth rate, if not higher.

4 Likes

I hear you guys on the worries over the reduced guidance, and I fully appreciate the choppiness of MDB over the last 6 months. The weeks of 3/13 and 6/3 have given as all our appreciation. Other than that, MDB has pooped out on us.

If MDB is trading at the same price as six months ago, and if Mongo has had two good quarters these last six months, MDB is a lot cheaper now than six months ago.

I’ve been long MDB for 18 months, I got in at $39.85. Now it’s $140.63. That’s a 253% increase, a CAGR of 134%. With Atlas growing at triple digit rates, with six months of consolidation, this is not a stock to bet against, not even a stock to wait for until it drops (which it might well do). There is no limit to the growth of data, to the size of the market (TAM) beyond falling prices – technology deflation. In addition, databases tend to be winners take most, just look at Oracle. For reasons discussed often here, Oracle/SQL is not a treat to Mongo.

4. MDB Revenue as a percentage of the DB market from $346.1MM with a TAM of $50B = 0.7% of the total market.

SQL is being disrupted by Document storage. If MDB Revenue’ is 0.7% of the total market, that’s FANTASTIC news! A huge market to grow into. SQL is very good at what it does but it has lots of problems because it is a straitjacket when you need to make changes to the data structure. Document storage is based on the principles of OOP which, if properly implemented, is much easier to update. Even more important, I believe that data suitable for Document storage is growing much faster than data suitable for SQL. If I’m right, Document storage is at the bottom of its “S” curve while SQL is closer to the top of its “S” curve.

I think MDB is one of the safest SaaS stocks available these days.

Denny Schlesinger

63 Likes

If MDB Revenue’ is 0.7% of the total market, that’s FANTASTIC news!
See my other post on the TAM for NoSQL DB. Not all of RDBMS can be replaced by NoSQL, at least not in the near or medium term future. MDB has nothing to offer on RDBMS space. So when you look at MDB, you should look at NoSQL DB space and see MDB’s market share. That is certainly no 0.7%. But I am sure you know most of this. So bit surprised to see above comment from you.

I think MDB is one of the safest SaaS stocks available these days.

It is not clear how you define safe. In the last 3 months the stock has dropped 24% from its top. For many stocks that would be bear market territory. However, given the parabolic price raise, I guess it should be okay. I think the stock is vulnerable at here, if the price is not going to hold here, it could easily drop to $80 to $100 range. May be given your entry price, are you suggesting safe? If not that kind of drop would not be termed as safe. I know valuation and price are not discussed much here, and there is a reason for it. I appreciate that. Given the enormous move SaaS stocks made last year, I would be careful to assume anything as safe.

2 Likes

I’m of the same mindset as Denny on this. I’m not about to sell out on “concerns about tougher comps” in the next few quarters nor do I sit there and make calculations for next quarter anyways. All people are doing when doing that is expecting the same thing to keep happening when history shows things change. I want to see how big this market for handling unstructured data can get and will sell once I’m convinced MDB won’t be a key part of that or the market is smaller than I expected.

I don’t look at this as “.7% of the tam” or whatever. We have a new solution how to handle unstructured data so it’s an entirely new market/tam. Well see how big it gets.

MDB is my biggest position.

12 Likes

12X,
I was making the point that I think that it is best to hold on for the foreseeable future as well. My thought on the 0.7% market share was that I think MDB has a long, long way to run.

Best of luck to longs.

bulwnkl

We have a new solution how to handle unstructured data so it’s an entirely new market/tam. Well see how big it gets.

The market is expected to grow at 35% annually. Remember, the NoSQL is already multi-billion market and if it can grow at 35% for the next 5 years that’s a pretty good growth and I mentioned that MDB could grow slightly higher than the market. Now the forecast and reality could be different due to many factors but you have to start with somewhere and I take that as a pretty good place to start.

Now, if you are someone with an entry price of $40 and going to sit out the gyrations of the growth phase and not going to let that volatility shake you out of your position, I totally get that. Kudos to you.

On the other hand the current share price, which has over 250% gain over a very short term, and has the potential to see 40% decline because growth could slow couple of quarters is not a “safe” situation.

My point is about the safe stock and not about long-term prospects of Mongo.

3 Likes

My only concern with Mongo is how they continue to spend more on SG&A than their revenues, quarter after quarter.

Their SG&A increases as fast as sales. Is that an accounting trick? Or is it a profitable growth issue? Meaning, are they paying out too much to get a deal? Spending more than their staff can yield?

The funds that own it appear to have a growing concern.

Flying Circus, I’m not sure what you’re looking at? Year ended Jan 2019 their S&M expense was 55% of sales, typical of a SaaS company. In 2016 it was 88%.

Expenses continue to fall as a percent of sales.

3 Likes

See my other post on the TAM for NoSQL DB. Not all of RDBMS can be replaced by NoSQL, at least not in the near or medium term future. MDB has nothing to offer on RDBMS space. So when you look at MDB, you should look at NoSQL DB space and see MDB’s market share. That is certainly no 0.7%. But I am sure you know most of this. So bit surprised to see above comment from you.

Disruption does not mean going head to head. Mongo is currently going after a different market than the one currently dominated by SQL and the operative word is “currently.” By that I mean that some day SQL might be obsolete.

A bit of technology to explain my position. Before SQL there was Flat File, essentially IBM punched cards first stored on tape and later on disk. The problem with cards was that they only had 80 columns. Once tape appeared you could make the cards, now called “records” as long as you needed, big advance. The problem that was not solved was that if you needed the client’s name on three reports you had to store it in three places. To update the client’s data you had to update all the records on which it appeared. SQL to the rescue! By creating relations between tables you got rid of the duplication and facilitated updates. The downside is that if you don’t index these relational fields (keys) the system is as slow as molasses on a winter day. I once made the mistake of not indexing an application for a client and on my small test cases it was not a problem but as they accumulated data the system ground to a halt. And it was not a large database. When I added the indexes the system took off like greased lighting. SQL depends fundamentally on indexes.

When you create a Document storage (large capacity IBM cards) with a similar set of indexes you have all the data you need to make it relational. Relational was created to save storage space which was slow and costly. As storage becomes ample and inexpensive the driving force behind relational storage disappears.

It is not clear how you define safe. In the last 3 months the stock has dropped 24% from its top. For many stocks that would be bear market territory.

I learned a long time ago that stocks are not escalators to financial heaven, it’s a bumpy ride as you describe. But let’s look at how successful investors look at it: “Sell when the story has changed for the worse or if you discover you have made a mistake.” Are either of these applicable to Mongo DB? For a LTBH investor a 24% drop is just noise if neither of the two sell criteria apply.

Judged by the technical explanation and the investing strategy above, MDB is a very safe stock. Contrast this with the mindless holding of 3D printing stocks. Excepting some very specialized applications, 3DP has no moat, it was the market’s hula hoop and pet rock craze. That is not to say that Document storage cannot, in turn, be disrupted. But it won’t be SQL reborn.

One closing comment, I wouldn’t invest in MDB if they didn’t have Atlas-aaS. Have you noticed the triple digit growth rates of Atlas?

Denny Schlesinger

32 Likes

As storage becomes ample and inexpensive the driving force behind relational storage disappears.

As a minor quibble, I don’t know that I would agree with this. Having any given piece of data in only one place is still a major benefit. Speedy access from indexing is still a major benefit. And, while the benefit of document databases is the ability to handle lack of formal structure, for some applications, like ERP transaction processing, the formal structure is itself a benefit. Plus, relational databases have evolved to more than their original simple structure to include things like word indices and JSON, BLOB, and CLOB data types.

3 Likes