9 ms·
Gitlab’s Startup Acquisition Process
- breck 4y agoThis is awesome. Kudos to Gitlab for open sourcing this.
- LoverKiddo12 4y ago[dead]
- diceduckmonk 4y ago> The call must include the Product champion and may also include Stage Leaders I was not familiar with these roles before this article. Are they more colloquially known in the M&A world ?
- jsty 4y agoFrom the context Product Champion would seem to be using "champion" as in the B2B sales world - usually someone advocating the purchase of a particular vendor's solutions, here someone inside GitLab advocating to buy a particular company.
- dnsmichi 4y agoGitLab team member here. "Stage leaders" is specific to GitLab, referring to the stages of the DevOps lifecycle [1]. Stages are part of the product hierarchy definition [2], with sections, stages, groups, categories, features. Maybe the term is similar to "product group leader" in other areas. FYI, created a merge request to link the product handbook from the acquisitions handbook, providing more context on stage leaders. [3] [1] https://about.gitlab.com/handbook/product/categories/#devops-stages https://about.gitlab.com/handbook/product/categories/#devops... [2] https://about.gitlab.com/handbook/product/categories/#hierarchy https://about.gitlab.com/handbook/product/categories/#hierar... [3] https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/120118 https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_request...
- rubidium 4y agoThey’re roles (intentionally flexible in the who) ascribed for the particular acquisition target. In M&A you have 2 main stages, the (1) find interesting targets and confirm they’re interesting, and (2) the purchase and integration. The champion will often lead (1) but if they’re too busy may have a defined stage leader to make sure the trains keep moving well. In the later stage of (2) the stage leader will typically be someone with experience integrating companies. It’s an art. I wouldn’t say they’re agreed on definitions, but I got what they meant from my exposure to M&A.
- ankit70 4y agoFeels like created on Workflowy/RoamResearch with nested bullets. Great!
- ericb 4y agoPretty cool that they shared the process. A couple things that seem interesting to me: * Giving the acquirer the cap table early on seems to go against the advice I've seen. * This is a ton of time investment for a company that has no idea if an offer will be forthcoming, or if it would be in a ballpark where a deal would happen? The acquiree is supposed to go through 12 stages of diligence a code review, detailed financials, employee review, give out their roadmap, customers, vendors, cap table, source code, financial assets all before seeing any hint of what the offer will be or whether there will be one? Is that right? Wouldn't getting an idea of whether you're in the same neighborhood be sensible before demanding so much?
- moneywoes 4y agoSeems like they could just steal a lot of info and then build their own version through this process
- cs02rm0 4y agoDoes seem odd to expect to share code early and a risk to share it with any interested party. I mean, it's someone else's code, your engineers are going to say it's rubbish, it needs a full rewrite and throwing away, warn us up front before you even think about acquiring such terrible code, etc. But if it's a built a company to the point of raising sufficient revenue/profit it's surely good enough.
- jacquesm 4y agoIt is. Normally you only do that after you agree on the terms and that means there is a deal unless something horrible is found during DD. And if your code is terrible simply disclose it then likely the requirement will go away. But if you claim it is super good but you only have juniors on staff you can expect to be quizzed.
- jacquesm 4y agoYes, this happens. So be very much on your guard about this and make sure that you trust whoever you talk to and if you can't trust them then you can ask a trusted party to do the review for you and pass that to whoever claims to be interested. There are many variations to this kind of 'vendor dd', you can prepare it beforehand or you can push to have the process modified until it is to your liking depending on how desirable you are.
- mbesto 4y agoSince this documentation heavily refers to Technical Due Diligence processes, I thought I'd offer an "AmA" since this is what I do for a living (personally have conducted 400+ Tech DD projects). Disclaimer - I'm not a GitLab employee and they are not a client of mine, but their documented processes are very synonymous with what I do.
- wslh 4y agoExcellent topic, my company also does technical due diligence. Even so, beyond acquisition, regarding investments we see that founders networking and promises take over technical capabilities. Not the same for pure acquisitions. Shameless plug: [1] It would he great if the HN community could comment more about this topic beyong the Gitlab's article. [1] Fundamental Analysis of Web3 Technologies: https://blog.coinfabrik.com/fundamental-analysis-of-web3-technologies/ https://blog.coinfabrik.com/fundamental-analysis-of-web3-tec...
- ericb 4y agoThanks! * What are the most common gotchas? * What tools do you use to do the technical due diligence? * What would you suggest to prepare for it? * What would acing it look like?
- Closi 4y agoI'm not OP, but when I experienced due dilligence the thing I found counter-intuitive was that 'looking really good at everything' isn't actually the best approach. As an example - it might be better that the company doing Due Dilligence finds you awful at sales during the DD phase, because they will see that you got revenue despite poor sales technique and they will see it as an easy target for improvement / 'to generate value'. Companies want to identify ways that they would be able to help the company they are aquiring. Not sure if this applies to Technical DD, but thought it was interesting enough to share!
- jacquesm 4y agoYes, that's called 'hidden upside'. You can of course also disclose this before DD. As a rule, surprises during the DD process are to be avoided if you can, even positive ones (because you may lose out on a bid from a party that would have bid if they had been aware of it). source: yaddp.
- FearlessNebula 4y agoWhy does everything need to be acquired these days? Why do we consolidate everything into a few big companies? Why can’t we just have technology spread out across multiple players.
- jen20 4y agoBecause VCs need returns, and many of these companies wouldn’t even exist without VC money.
- jacquesm 4y agoOr because founders want to diversify. A founder is a non-diversified investor...
- hummus_bae 4y ago[dead]
- datasert 4y agoGitlab's Handbook [0] (which this article is part of) is an invaluable resource for any first time founders. This is one of the best contribution of Gitlab to the community in my opinion. [0] https://about.gitlab.com/handbook https://about.gitlab.com/handbook
- rfrey 4y agoWow - I can see why Paul Graham at one point talked about how exploring an acquisition can kill a company. Even at the "preliminary diligence" stage, a small company will have invested at least a month of the founder's time AND basically given away the keys to the kingdom - all their schemas, processes, customer lists, and contracts. I know there would be non-disclosures in place, but it's easy to imagine a company less scrupulous than Gitlab basically cratering a potential competitor without the resources to go after them in court.
- ignite 4y agoI don't know if this is still a common thing, but this definitely used to happen.
- iamdamian 4y agoIt seems that Amazon did something similar under the guise of becoming an investor: https://news.ycombinator.com/item?id=23929044 https://news.ycombinator.com/item?id=23929044
- bberenberg 4y agoYes there is a risk of this. But, with modern tooling, you don't need to do this to accomplish the same goals. It's not hard to figure out the high level approach of what someone else is doing. It's not hard to figure out a significant number of their customers. There are entire companies that exist to answer these questions for you. Ultimately, if you're looking to sell your company, you will have to trust the acquirer. This isn't a GitLab thing, it's just the name of the game. I wrote a bit about selling my company a year ago [1] and it was similar, except a lot of the diligence happened post LOI / Term Sheet. In hindsight, I kind of wish it had happened earlier. [1] https://www.nothingeasyaboutthis.com/lessons-from-selling-a-bootstrapped-company-to-a-pe-backed-company/ https://www.nothingeasyaboutthis.com/lessons-from-selling-a-...
- fatnoah 4y agoHaving gone through an acquisition by a different company, I can say that this process almost exactly matches the process I went through. It was definitely a lot of work that ate up tons of time. It also wasn't something that could be discussed with most of the company, so now you add a few months of "acting funny" to the mix and it's a challenge and a half.
- jasonjei 4y agoThis is a great process write up, but I was surprised how little was addressed about existing target company customer support and communication. There is ample support for internal stakeholders, but what about customers of the target company? I have found that as a customer of products acquired by larger companies, the customers of products being acquired and integrated into a larger product are often forgotten and sidelined.
- mkeeter 4y agoOne interesting tidbit from the handbook: A good acquisition target company should be "willing to sunset old customers within 90 days or less, with an option to transition to GitLab" [1] Given the pattern of startups being acquired, announcing "nothing will change", then sunsetting their original product [2], it's interesting to see this spelled out so plainly. [1] https://about.gitlab.com/handbook/acquisitions/#acquisition-target-profile https://about.gitlab.com/handbook/acquisitions/#acquisition-... [2] https://ourincrediblejourney.tumblr.com/ https://ourincrediblejourney.tumblr.com/ is the canonical repository of these emails
- robertlagrant 4y agoThat tumblr site is great. Twitter has been busy.
- deleted 4y ago[deleted]
- paultopia 4y agoForgot step 6, layoffs.
- pdq 4y agoThis is an impressively thorough and quite insightful M&A overview. However, it is completely one-sided toward the buyer (ie GitLab). As a seller, I'd be wary of going through even a fraction of the pre-term-sheet diligence and disclosure, without getting to a ballpark on acquisition price (or price methodology) beforehand. Also, they don't mention, but having escrow set up as an insurance in case the acquirer backs out also seems necessary (ie % of the deal held with third party). Otherwise you are basically giving away all your company secrets and time, and if they back out, you get nothing. I'd guess YCombinator has something equivalent from the seller side. It would be great if they shared their M&A handbook at some point in the future, although I understand it's probably considered "secret sauce".
- fountainofage 4y agoIt's basically don't waste your time with corp dev. http://www.paulgraham.com/corpdev.html http://www.paulgraham.com/corpdev.html You hit the nail on the head that it's way too much work when there's not even a contingent offer on the table. A real buyout would come in with either a stated sum, or a methodology for how that sum will be calculated.
- tapotatonumber9 4y agoCan anyone expand “MVC” as used in this guide? It appears as “Outline a simple integration timeline for those features, considering an MVC release on the first month …” I’m only familiar with this meaning Model-View-Controller. In this context I’d probably expect “POC”.
- sjhewitt 4y ago"Minimal Viable Change" https://about.gitlab.com/handbook/product/product-principles/#the-minimal-viable-change-mvc https://about.gitlab.com/handbook/product/product-principles...
- tapotatonumber9 4y agoThank you! This might be a useful term of art to bandy about my current work situation.
- dnsmichi 4y agoThanks a lot for helping :-) I've created an MR to link MVC in the handbook: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/120169 https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_request... (GitLab team member here)