Case Interview Fundamentals: Lesson 32 [Drill: Enterprise software provider M&A] — Transcript
Full transcript
- 0:00Hey guys. So, this next drill is about
- 0:04the merger of two large software
- 0:07providers. Actually, one really large
- 0:10one, Oracle, and another one that's
- 0:12hypothetical, SoftSales.
- 0:15Okay? So, let's get to it. I'll show you
- 0:17the framework question, and then you can
- 0:21come up with your answer for it, and
- 0:22then move on to the hypothesis testing
- 0:25question. Again, I'm not going to show
- 0:27you my framework answer because this is
- 0:30not the point of this drill. The point
- 0:32of this drill is hypothesis testing.
- 0:34So, here's our case question.
- 0:36Oracle, a giant multinational computer
- 0:38technology corporation specialized in
- 0:41developing and marketing enterprise
- 0:43software solutions such as ERP software,
- 0:46CRM software, and SCM software, which
- 0:48are enterprise resources planning,
- 0:51customer relationships management, and
- 0:53supply chain management. They are
- 0:55currently considering acquiring a
- 0:57rapidly growing medium software company
- 0:59called SoftSales that has one main
- 1:02product, a cloud-based CRM software.
- 1:05How would you help them with that
- 1:06decision?
- 1:07Now, before we move on, I want to remark
- 1:08that this software that they have made
- 1:11is really successful, is really helping
- 1:13out clients, and that's why they're
- 1:14gaining a lot of market share.
- 1:17So, should Oracle buy SoftSales? So,
- 1:20once you have your framework set, let's
- 1:22move on to the uh
- 1:25hypothesis testing question.
- 1:27So, in this case, you said at some point
- 1:29during your framework presentation,
- 1:31uh I need to test whether it would make
- 1:33sense for Oracle to buy SoftSales for
- 1:35their software versus developing its own
- 1:38similar product. Then, at that moment,
- 1:40the interviewer interrupted you.
- 1:42That's interesting. How would you figure
- 1:43that out?
- 1:45So, you have to stop your framework
- 1:46question. You got to your framework
- 1:48answer, and you got to ask and you got
- 1:50to answer the interviewer's question.
- 1:52And now, again, like before, I'm going
- 1:55to clear my thoughts by structuring my
- 1:58hypothesis into a cause and effect and a
- 2:01consequence. Now, in this case, there's
- 2:03a lot happening, okay? So, we could
- 2:07need it could make sense for us to buy
- 2:09them for their software versus
- 2:10developing it because
- 2:12it's it would be cheaper, because it
- 2:15would be better, a better software, or
- 2:18because they're conquering they're
- 2:21capturing market share so fast that it
- 2:23would be hard to compete if we waited
- 2:25too long. And that too long would mean
- 2:28the time to develop uh a similar
- 2:31software. So,
- 2:32uh
- 2:33let me structure that. The cause first
- 2:36cause here which is the most likely for
- 2:39the most likely hypothesis is Soft Sales
- 2:41is rapidly rapidly capturing market
- 2:43share with their product. The effect of
- 2:45this is in the development time, Soft
- 2:48Sales will have captured a large chunk
- 2:50of market share. And as a consequence,
- 2:52it would be too hard to compete even
- 2:55with a similar product after they have a
- 2:57large client base. I'm assuming, of
- 2:59course, that the switching costs are
- 3:01high, which they usually are for
- 3:04um
- 3:05uh enterprise systems. If for some
- 3:08reason in this new different product
- 3:09that they have, it's not, everything
- 3:11changes, okay? Now, other hypotheses
- 3:15that are important here is are software
- 3:17style is much appreciated by the market
- 3:20and is very different from what Oracle's
- 3:21used to make. And that is a necessary
- 3:25assumption for it being more expensive
- 3:28for us to develop or for it being uh bad
- 3:32for their software to be necessarily
- 3:34better. So, one of those. Soft Sales
- 3:37devs are more efficient in developing
- 3:39that style of software and are hard to
- 3:41poach, so I can't just hire them.
- 3:44Or Soft Sales devs are much better at
- 3:46developing that kind of software. All
- 3:48right? And it would be too costly to
- 3:50develop a similar product in-house.
- 3:52that's the consequence of the second
- 3:54hypothesis, and the consequence of the
- 3:55third is a similar product developed in
- 3:58house would be significantly worse. So,
- 4:01I get two main hypotheses out of this.
- 4:03They are Soft Soft Sales is capturing
- 4:06market share too quickly, it would be
- 4:08harder to compete with them once they
- 4:10have a large customer base. So, it's not
- 4:12worth the wait to develop in house. Or
- 4:14else, Soft Sales is much better or more
- 4:17efficient in making that style of
- 4:18software, and competing with a different
- 4:20one would not be competitive. So,
- 4:22developing in house would be either too
- 4:24costly or quality would not be
- 4:26acceptable. Okay? Now, let's test those
- 4:30two or three hypotheses. Now that I have
- 4:33them structured into cause, effect, and
- 4:35consequence, it's much simpler for me to
- 4:37test.
- 4:38All right, so the first one is Soft
- 4:40Sales is capturing share too quickly,
- 4:42second one in-house development would be
- 4:44too costly, and third one software
- 4:46developed in house would not be
- 4:48competitive.
- 4:49So, for the first one,
- 4:51first thing I want to know is
- 4:53how long it would take us to develop
- 4:55that kind of software. And to find that
- 4:57out, I'd probably just simply estimate
- 4:59with specialists. I might want to divide
- 5:01the project into phases and estimate
- 5:04time for each phase, but I'm definitely
- 5:06going to need a specialist to help me
- 5:08with that. If I need to, I'd benchmark
- 5:11that with other projects that I've done
- 5:13in house
- 5:15and add an extra time
- 5:18or percentual of extra time in specific
- 5:21phases due to the style of the software
- 5:23being much different, if it is. Okay?
- 5:26Next, I need to know how fast have Soft
- 5:29Sales been capturing clients, and by how
- 5:31much they could increase pace,
- 5:33especially if they got additional
- 5:35funding. So,
- 5:37to look at the first question, I'd try
- 5:39to understand the history of growth in
- 5:41number of clients per month, and that
- 5:43would help me understand uh, have a
- 5:45perspective in the future. And of
- 5:47course, how that growth has been
- 5:49changing, the growth rate has been
- 5:50changing. And uh, I'd need to estimate
- 5:54their pace increased
- 5:56uh,
- 5:57given potential funding. So, they could
- 6:01increase sales force if they have
- 6:03additional funding, and that would make
- 6:05them grow much quicker if their product
- 6:08is so good. All right?
- 6:10Next, to find out if in-house
- 6:13development would be too costly. I'd
- 6:15first and especially need to know that
- 6:18uh, sales software sales devs are much
- 6:20more efficient in that style of
- 6:22software. If that's true, I'd also need
- 6:24to know if the style of software is
- 6:27different than what Oracle makes. If
- 6:28it's not different, then this is not an
- 6:30issue.
- 6:31That style of software is required to
- 6:33compete cuz if it's different, but we
- 6:35can't do it in another style that we're
- 6:38used to, and that would be fine with the
- 6:40market, then well, that's not really a
- 6:42problem. And it's not possible to poach
- 6:45main devs. So, if
- 6:48the style is different the style is
- 6:49different, and the that style is also
- 6:51required by the market, I can always
- 6:54poach the main devs and have them work
- 6:57for me, and then it would still be
- 7:00I would still have their efficiency. So,
- 7:02if I can't poach them, well, in-house
- 7:04development would be too costly.
- 7:06And to find out if software developed
- 7:08in-house would not be competitive,
- 7:11it's pretty much the same three last
- 7:13tests, but instead of
- 7:15knowing if software if software sales
- 7:17devs are much more efficient, I need to
- 7:19know if they are more qualified in that
- 7:21style of software. And the next tests
- 7:23are the same, I've done them already.
- 7:26Okay? This is how I test this. You could
- 7:29have
- 7:30uh, put the two last hypotheses
- 7:32together, that would be fine, too. I
- 7:33chose to separate them because it makes
- 7:35everything clearer to me. Okay? All
- 7:37right. I hope this helped you, and I see
- 7:39you in the next one.
About this transcript
This page contains the full transcript of Case Interview Fundamentals: Lesson 32 [Drill: Enterprise software provider M&A] by CraftingCases, generated from the public captions YouTube serves with the video. The transcript has 1,282 words across 205 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.
What you can do with it
Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.
Free YouTube transcript tool
YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.