Strategic Acquisitions vs Product Tuck-Ins
Strategic acquisitions vs product tuck-ins: a deal buys a market or a feature, and pricing them the same is how acquirers overpay. A fit matrix and real deals.
The question of strategic acquisitions vs product tuck-ins is the most expensive category error in technology M&A, and most of the cost is paid at the moment of pricing. A strategic acquisition buys a market position. A product tuck-in buys a feature, a team, or a specific capability. They are not the same transaction, they should not carry the same valuation logic, and confusing the two is how acquirers overpay by an order of magnitude.
The tell is not the dollar figure. It is what the deal is supposed to change. A strategic acquisition changes the map: it adds a new business, a new customer base, or a new revenue line the acquirer could not reach on its own. A tuck-in changes the roadmap: it accelerates a feature the acquirer was already building or hiring toward.
This piece reads that distinction through real, recent deals. Salesforce paid $27.7 billion for Slack (closed 2021). Microsoft paid $68.7 billion for Activision Blizzard (closed October 2023). Adobe announced $20 billion for Figma and walked away (terminated December 2023). Google runs a quiet stream of smaller capability buys. Every company figure ties to a filing or a press release. The framing is analytical: how to classify and price a deal, not what to do about any stock.
Key takeaways
- Category is destiny. A strategic acquisition is priced on market position and ecosystem; a tuck-in is priced on feature value or team cost. Mispricing the category is the core M&A error, and it happens at signing, not at integration.
- The roadmap-vs-map test. If the target is a standalone path to a market the acquirer cannot otherwise reach, it is strategic. If the acquirer’s roadmap simply absorbs the target’s product, it is a tuck-in.
- Strategic deals are large and visible. Salesforce-Slack at $27.7 billion (Salesforce Form 8-K, December 1, 2020) and Microsoft-Activision at $68.7 billion (Microsoft Form 8-K, October 13, 2023) bought positions, not features.
- Adjacent-market strategic deals carry antitrust risk. Adobe’s $20 billion Figma deal was announced in September 2022 and terminated in December 2023, with a break-up fee disclosed on Adobe’s FY2024 10-K. Regulatory defensibility is part of the thesis, not a footnote.
- Tuck-ins go unnoticed by design. Smaller capability and team acquisitions are priced on cost replacement, rarely disclose terms, and are usually the more disciplined deals because the price matches what is bought.
What separates a strategic acquisition from a product tuck-in?
A strategic acquisition buys a standalone market position, ecosystem, or revenue stream, and a product tuck-in buys a feature, team, or specific capability the acquirer folds into an existing product. The first is priced on a business thesis. The second is priced on cost replacement or a small subset of revenue.
The reason this matters is mechanical. When you classify a deal as strategic, you justify a large multiple on the target’s revenue or its market value, because you are paying for a position you could not build in time. When you classify it as a tuck-in, the ceiling is roughly what it would cost to build the feature or hire the team yourself, plus a premium for speed. Pay a strategic multiple for a tuck-in and the deal cannot return its cost. The same disclosure discipline that separates signal from narrative in how to read a tech S-1 like an operator applies to a deal announcement: the press release is the story, the integration plan is the truth.
How do you tell whether an announced deal is strategic or a tuck-in?
Look at three signals: whether the target survives as a standalone product or brand after close, whether the acquirer’s roadmap absorbs the target’s product or expands around it, and whether customer overlap is minimal, which points strategic, or significant, which points tuck-in. Salesforce kept Slack as a named product line and integrated gradually, the strategic pattern. A company that announces a large acquisition and retires the product within a year priced a tuck-in wrong.
The cleanest way to apply those signals at announcement is to ask one question. What is this transaction supposed to change?
If it changes the map, it is strategic. The acquirer is adding a business it did not have: a new customer base, a new product category, a new revenue engine that stands on its own. Slack gave Salesforce an enterprise communication surface it did not own. Activision gave Microsoft a gaming content library and player network it could not have built organically at that scale or speed.
If it changes the roadmap, it is a tuck-in. The acquirer was already building toward the capability and chose to buy time instead of spending it. The target’s product gets folded into something larger, its brand usually disappears, and within a year or two it is a feature, not a company.
The signals that distinguish them are observable at announcement:
- Brand survival. Does the target keep its name and product line, or get absorbed.
- Roadmap relationship. Does the acquirer build around the target or build over it.
- Customer overlap. Minimal overlap points strategic; heavy overlap points tuck-in or consolidation.
- Pricing basis. A multiple of the target’s standalone revenue or market value points strategic; a cost-to-replicate or team-cost basis points tuck-in.
Case study: Salesforce and Slack, a $27.7 billion strategic deal
Salesforce announced the Slack acquisition on December 1, 2020 at $27.7 billion in cash and stock, including assumed net debt (Salesforce Form 8-K, December 1, 2020), and closed it on July 1, 2021. By every signal in the roadmap-vs-map test, this was strategic.
Slack was not a feature Salesforce was building toward. It was a standalone enterprise communication platform with its own brand, its own user base, and its own seat-based revenue stream. Salesforce was buying a position in the daily-active-workplace surface, the place employees live during the workday, which its CRM did not occupy.
The pricing reflected the category. A $27.7 billion valuation on a company with roughly $900 million in annual revenue at announcement is a multiple that only makes sense if you are paying for market position and a future platform, not for a bolt-on feature. That is the strategic premium: the number is justified by what the asset becomes inside the acquirer, not by its standalone economics.
The integration pattern confirmed it after close. Salesforce kept Slack as a named product line rather than dissolving it into the CRM. Integration into the broader platform happened gradually, the deliberate pace that signals an acquirer protecting a position rather than harvesting a feature. The enterprise lock-in logic behind owning the daily workplace surface is the same dynamic dissected in Microsoft Copilot and enterprise lock-in: the platform that owns the surface where work happens controls the funnel for everything adjacent.
The operator lesson is that a strategic price demands a strategic integration. If Salesforce had absorbed Slack into the CRM as a chat feature and retired the brand, the $27.7 billion would have been a tuck-in price paid for a tuck-in outcome, which is the definition of overpaying.
Case study: Microsoft and Activision, a $68.7 billion strategic deal
Microsoft announced the Activision Blizzard acquisition on January 18, 2022 at $68.7 billion all-cash and closed it on October 13, 2023 (Microsoft Form 8-K, October 13, 2023), after nearly two years of global regulatory review. This is the largest deal in the comparison set and an unambiguously strategic one.
Microsoft was not buying a feature for Game Pass. It was buying a content library, owned intellectual property, and a player ecosystem: franchises Microsoft could not replicate by building studios from scratch in any reasonable timeframe. The thesis was expansion of the gaming total addressable market and the services revenue that sits on top of it.
The pricing basis is the strategic tell. A $68.7 billion valuation is underwritten by the standalone value of Activision’s franchises and the players attached to them, plus the option value of pulling that content into a subscription distribution model. None of that is a roadmap acceleration. It is a new position in owned content that Microsoft did not have. The services-margin logic that makes owned content so valuable inside a larger platform is the same engine examined in Apple Services as the margin engine inside iPhone: high-margin recurring revenue layered on an installed base.
The length and intensity of the regulatory process underline how strategic the deal was. Regulators do not spend two years on a tuck-in. The scrutiny itself is evidence that the transaction changed the competitive map rather than a single product roadmap.
One caution belongs here for balance. Microsoft conducted workforce reductions in its gaming division after closing. That is a reminder that even a correctly classified strategic deal carries integration cost and human consequence, and that the strategic narrative does not automatically translate into a clean post-close outcome. A strategic price buys a position; it does not guarantee the position is operated well.
Case study: Adobe and Figma, a $20 billion strategic deal that died
Adobe announced the Figma acquisition on September 15, 2022 at roughly $20 billion in cash and stock, and terminated it on December 18, 2023 after regulatory challenges in Europe and the United Kingdom. Adobe recorded a $1 billion break-up fee charge tied to the termination, disclosed in its Form 10-K for the fiscal year ended November 29, 2024.
This was a strategic deal by classification: Figma was a standalone collaborative design platform with its own brand, its own users, and a market position in browser-based design that Adobe did not own. The pricing, a reported $20 billion against a company an order of magnitude smaller in revenue, was a strategic-position price, not a feature price.
The failure is the instructive part. Design tools and Adobe’s creative software are adjacent markets, neighbors rather than the same market, and that adjacency is exactly what gave regulators an opening. The concern was that Adobe was buying a fast-growing competitor in a neighboring category to neutralize it. A strategic thesis in an adjacent market has to survive the question of whether it is expansion or elimination.
The $1 billion break-up fee is the cost of a strategic conviction that lacked a regulatory case strong enough to close (Adobe Form 10-K, FY2024). The lesson is precise: in adjacent-market strategic M&A, antitrust defensibility is part of the thesis, not a closing formality. A deal that reads as eliminating a future competitor will draw the scrutiny that a deal expanding into genuinely new territory does not. The same competitive-positioning logic that shapes platform rivalries in Google’s AI strategy is a distribution war shapes which acquisitions clear: regulators read the map the same way operators do.
The tuck-in reality: why small deals go unnoticed
The deals that fill the bottom of the M&A funnel are tuck-ins, and they are designed to be invisible. Google’s typical acquisition targets a specific technical capability or a team, often in AI or security, and is priced on cost replacement and bolt-on potential rather than standalone revenue. Terms are frequently undisclosed.
These are tuck-ins by definition. The acquirer is not buying a market position; it is buying a head start on a capability it was already building or hiring toward. The acqui-hire variant is the purest form: the product may be shut down entirely, and the value is the team and its expertise folded into an existing roadmap.
Illustrative note: the small-deal price ranges discussed here are qualitative patterns drawn from press reporting (Google Official Blog, TechCrunch, VentureBeat, 2023-2026) and are not tied to a specific disclosed transaction value. Treat them as a pattern, not a figure.
The reason tuck-ins go unnoticed is that the pricing matches the purchase, so there is no story to tell. A small price for a small, specific capability is unremarkable. The discipline is built in. The danger appears only when an acquirer wraps a tuck-in in a strategic narrative and pays a strategic price for it, which is the failure mode the next sections address.
The Acquisition Fit Matrix
The framework that ties this together is the Acquisition Fit Matrix, an original analytical asset you can run against any announced or contemplated deal. It classifies a transaction across five dimensions and forces the category decision before the price decision. The point of naming it is reuse: the same five rows triage a $20 billion platform deal and a $40 million acqui-hire with the same logic.
| Dimension | Strategic acquisition | Product tuck-in |
|---|---|---|
| What is bought | A standalone market position, ecosystem, or revenue stream | A specific feature, team, or technical capability |
| How it is priced | Multiple of standalone revenue or market value (the position) | Cost to replicate or replace the team, plus a speed premium |
| Integration risk | High and slow; the asset is protected and run semi-independently | Lower and fast; the asset is absorbed into an existing product |
| The success test | Does the new position generate revenue the acquirer could not reach alone | Does the feature ship faster and cheaper than building it |
| The failure mode | Overpay for a position that the acquirer then absorbs like a feature | Pay a strategic price for what is really a feature buy |
Run the real deals through it. Salesforce-Slack: a standalone communication position, priced on market value, protected as a named product line after close. Strategic, and integrated like one. Microsoft-Activision: an owned content library and player network, priced on standalone franchise value. Strategic. Adobe-Figma: a standalone design position priced strategically, which failed on the integration-risk row before it could even be tested, because antitrust risk is a form of integration risk the matrix surfaces. A Google capability buy: a specific team or technology, priced on replacement cost, absorbed fast. Tuck-in.
The deal table makes the contrast concrete:
| Deal (source) | Announced value | Category | Outcome |
|---|---|---|---|
| Salesforce-Slack (Salesforce Form 8-K, Dec 1, 2020) | $27.7 billion | Strategic | Closed July 1, 2021; Slack retained as product line |
| Microsoft-Activision (Microsoft Form 8-K, Oct 13, 2023) | $68.7 billion | Strategic | Closed Oct 13, 2023 after extended regulatory review |
| Adobe-Figma (Adobe Form 10-K, FY2024) | $20 billion | Strategic (adjacent) | Terminated Dec 2023; break-up fee charged |
Sources: Salesforce, Inc. Form 8-K (December 1, 2020); Microsoft Corporation Form 8-K (October 13, 2023); Adobe Inc. Form 10-K (fiscal year ended November 29, 2024).
Why mispricing the category is the core error: every other M&A mistake is downstream of it. A strategic price on a tuck-in cannot be recovered through good integration, because the asset was never worth the position price. A tuck-in budget on a strategic bet starves the integration that justifies the deal. The matrix forces you to decide what you are buying before you decide what to pay, which is the only order that protects the price.
The four-question M&A filter
For operators who need a faster pass than the full matrix, the Acquisition Fit Matrix collapses into four questions. Answer them before signing, in this order.
- Is the target a standalone path to my total addressable market? If yes, it is strategic and a position-based price is defensible. If no, it is a tuck-in and the ceiling is build-or-hire cost plus speed.
- Does my roadmap absorb or replace the target’s product? Absorb-and-protect points strategic. Replace-and-retire points tuck-in. If you plan to kill the product within a year, you are buying a team or a capability, not a company.
- What customer overlap exists? Minimal overlap means the target reaches customers you do not, which is strategic value. Heavy overlap means you are consolidating or buying a feature, and the consolidation case has to clear an antitrust bar.
- What happens to the target’s brand, team, and org after close? Independence points strategic. Full absorption points tuck-in. The post-close org chart is the most honest statement of what the deal actually was.
If you cannot answer all four before signing, you are pricing on narrative rather than on deal logic, and narrative is the most expensive input in M&A.
The bear case: when tuck-ins masquerade as strategic
The strongest objection to this framework is that the categories are cleaner on paper than in a boardroom, and the skeptics get something real here. A motivated acquirer can construct a strategic narrative around almost any target, and the narrative is what justifies the price.
This is the masquerade failure mode. A deal that is functionally a tuck-in, a feature buy or an acqui-hire, gets wrapped in a story about market position, ecosystem, and platform expansion. The story raises the acceptable price from a replacement-cost basis to a strategic multiple. The matrix says price it as a feature; the boardroom prices it as a position; the gap is the overpayment.
Two forces make this worse. The first is competitive fear. When a rival is rumored to be circling the same target, the acquirer reframes a defensive tuck-in as a strategic must-have, and the price inflates to match the new story rather than the unchanged asset. The second is sunk-cost momentum on a failing integration. Once a strategic narrative is public, walking away admits the category was misjudged, so the acquirer keeps funding the integration to protect the story. Microsoft’s post-close gaming workforce reductions are a reminder that even a correctly classified strategic deal carries hard integration costs; a misclassified one carries those costs without the position to justify them.
Here is the honest weighing. The framework does not prevent a determined acquirer from telling itself a strategic story about a tuck-in. What it does is make the story falsifiable. The four questions and the five matrix rows produce a written record of the classification before signing, which means the post-close reality, did the product survive, did it reach new customers, did the position materialize, can be checked against the thesis. The matrix is a discipline, not a guarantee. Its value is that it makes the category decision explicit and auditable, which is exactly the step a masquerade skips.
Where this breaks: scale, timing, and competitive desperation
A framework this clean deserves its own counterexamples, because real M&A is not always made under rational conditions.
Emergency acquisitions distort the categories. When a company faces an existential threat, a platform shift it missed, a competitor about to lock up a market, the normal pricing logic suspends. A deal that the matrix would classify as an overpriced tuck-in can be rational as insurance against a worse outcome. The framework prices the asset; it does not price the cost of not owning it in a crisis.
Market panic can justify a strategic premium that looks irrational in hindsight. In a moment of category-defining urgency, paying above the position price to secure a scarce asset before a rival does can be the correct call, even though the same price looks like overpayment once the panic passes. The hard part is telling strategic conviction from fear-based buying in real time, when both produce the same large number.
Scale changes the math. For the largest acquirers, a deal that would be strategic for a smaller company is a rounding error, and the discipline of the matrix matters less because the downside is contained. A $200 million capability buy inside a company with hundreds of billions in revenue does not need the same scrutiny as the same deal would inside a startup. The framework is most useful precisely where the deal is large relative to the acquirer.
Timing can invert the classification. A tuck-in bought early, before a capability becomes a market, can become the seed of a strategic position later. The category is not always fixed at signing; some tuck-ins grow into positions, and the matrix captures the deal as it was, not as it might become.
None of this overturns the framework. It bounds it. The Acquisition Fit Matrix is the right default discipline because most deals are made under normal conditions where mispricing the category is the dominant error. The exceptions, emergencies, panics, and slow-burning option bets, are real, and the operator’s job is to name when a deal is one of them rather than letting the exception quietly become the excuse for every overpayment.
What operators should take from this
If you evaluate inbound or outbound M&A as a founder, operator, or analyst, the transferable skill is not memorizing deal values. It is forcing the category decision before the price decision. Here is the playbook, five concrete moves you can run on the next deal that crosses your desk.
- Classify before you value. Run the Acquisition Fit Matrix on the target before anyone proposes a number. Decide strategic or tuck-in on what is bought, then let the category set the pricing basis. Pricing first and classifying second is how the narrative captures the deal.
- Write the integration plan as part of the thesis. A strategic price commits you to a strategic integration: protect the brand, run it semi-independently, reach new customers. If your integration plan is to absorb and retire the product, you are buying a tuck-in and should pay a tuck-in price.
- Stress-test the customer-overlap row for antitrust. Heavy overlap in an adjacent market is where strategic deals die. Before signing an adjacent-market deal, ask whether a regulator would read it as expansion or as eliminating a future competitor, the question that ended Adobe-Figma.
- Price the failure mode, not just the thesis. For a strategic deal, model the cost of absorbing the asset like a feature, the overpayment scenario. For a tuck-in, model the cost of the team walking after the earn-out. The downside is where category errors show up first.
- Audit the deal against its written classification post-close. Twelve months after closing, check the org chart and the product. Did the brand survive, did it reach new customers, did the position materialize. The honest comparison between the signed thesis and the post-close reality is the only way to get better at classification.
The discipline that separates good acquirers from expensive ones is not better forecasting. It is refusing to let the narrative set the category. The same operator instinct that reads a margin line as destiny in why gross margin is destiny in SaaS, and that reads a revenue base for hidden fragility in customer concentration risk in SaaS filings, reads a deal announcement for what it is actually buying. Position or feature. Map or roadmap. Get the category right and the price follows; get it wrong and no integration can save it.
Methodology: how to classify a deal with the Acquisition Fit Matrix
- Inputs: the announced deal value and structure, the target’s standalone revenue and brand status, the acquirer’s stated integration plan, the customer-overlap profile, and the regulatory posture. All sourced from the press release, the relevant 8-K, and the acquirer’s later 10-K disclosures.
- Assumptions: that the acquirer’s stated integration intent is honest at announcement, and that disclosed deal values include the full consideration (cash, stock, and assumed debt). Both are checked against the closing 8-K and subsequent filings, not assumed from the press release.
- Sensitivity: the classification flips on two rows. If brand survival and roadmap relationship both point to absorption, a deal priced as strategic is a mispriced tuck-in. A single adjacent-market overlap can move a clean strategic deal into antitrust jeopardy, as Adobe-Figma showed.
- What this misses: the matrix classifies a deal as it is signed, not as it evolves. A tuck-in can grow into a position, and an emergency deal can break the pricing logic entirely. The matrix is a triage, not a verdict; the slow judgment about timing and competitive context is still the operator’s.
Where this framework is vulnerable
The Acquisition Fit Matrix is decisive at the moment of classification, but it has real limits that an honest operator names rather than hides.
Classification can be gamed by the acquirer’s own narrative. The matrix relies on the acquirer’s stated integration intent, and that intent is a choice management can describe favorably. A company can claim it will protect a target’s brand to justify a strategic price, then quietly absorb it after close. The written classification helps, but only if someone audits it later.
The categories blur at the edges. Some deals are genuinely both: a strategic position acquired partly for a specific capability inside it. The matrix forces a primary classification, and a deal that sits exactly on the boundary can be mispriced in either direction. The four questions resolve most cases, but not all.
Private-deal opacity hides the tuck-in baseline. Because tuck-in terms are usually undisclosed, the replacement-cost baseline that should anchor a tuck-in price is hard to verify from outside. An analyst can classify the category but rarely confirm whether the price matched it, which limits the matrix as an external scoring tool versus an internal decision tool.
Time changes the answer. A deal correctly classified as a tuck-in at signing can become a strategic position years later if the capability becomes a market. The matrix captures the deal as it was, and a snapshot framework cannot price optionality that only resolves with time.
None of this breaks the framework. It bounds it. The matrix is the fastest way to make the category decision explicit and to put a defensible pricing basis underneath a deal. What it cannot do is force an acquirer to be honest with itself, or price the value of an asset that only becomes strategic in a future the matrix cannot see. That judgment is still the operator’s, and it is the part that does not reduce to a table.
Analysis, not investment advice. Figures are drawn from the public filings and announcements cited inline by company and form type (Salesforce Form 8-K, December 1, 2020; Microsoft Form 8-K, October 13, 2023; Adobe Form 10-K, FY2024). Frameworks here are for understanding how to classify and evaluate acquisitions and their tradeoffs, not for making buy or sell decisions.
Want the full toolkit for evaluating deals like this, the Acquisition Fit Matrix, the four-question filter, and the strategic-vs-tuck-in scorecard used above? It’s in the Tech Business Analysis Playbook.
Sources
- Salesforce, Inc. Press Release, December 1, 2020 (Slack acquisition, $27.7 billion); Salesforce, Inc. Form 8-K, December 1, 2020
- Microsoft Corporation Press Release, January 18, 2022 (Activision Blizzard, $68.7 billion); Microsoft Corporation Form 8-K, October 13, 2023 (closing)
- Adobe Inc. Press Release, September 15, 2022 (Figma, $20 billion); Adobe Inc. Form 10-K, fiscal year ended November 29, 2024 (termination and break-up fee)
- Google Official Blog and TechCrunch/VentureBeat reporting, 2023-2026 (small team and capability acquisitions, illustrative)
- Gartner, Mergermarket, and SEC EDGAR filings (M&A valuation multiples, strategic vs. tuck-in, illustrative ranges)
Figures are drawn from public filings and primary documents, cited inline by fiscal period. Analysis only, not investment advice.
Frequently asked questions
What is the difference between a strategic acquisition and a product tuck-in?
A strategic acquisition buys a standalone market position, ecosystem, or revenue stream and is priced on that business thesis. A product tuck-in acquires a specific feature, team, or technical capability and is priced on cost replacement or a small subset of revenue. The distinction matters because paying a strategic price for what is really a tuck-in is a common way to overpay, and treating a genuine strategic bet like a tuck-in starves it of the integration budget it needs.
How do you tell whether an announced deal is strategic or a tuck-in?
Look at three signals. First, does the target operate as a standalone product or brand after the deal closes. Second, does the acquirer's roadmap absorb the target's product or expand around it. Third, is customer overlap minimal, which points strategic, or significant, which points tuck-in. Salesforce kept Slack as a named product line and integrated gradually, the strategic pattern. A company that announces a large acquisition and kills the product within a year priced a tuck-in wrong.
What did the failed Adobe-Figma deal teach about strategic M&A?
Adobe's December 2023 termination of its $20 billion Figma acquisition showed how antitrust risk compounds a thesis in adjacent markets. Design tools and creative software are neighbor markets, not the same market, which gave regulators an opening. The break-up fee Adobe recorded on its FY2024 10-K is the cost of a strategic conviction that lacked the regulatory case to close. The lesson is that strategic acquisitions in adjacent markets need antitrust defensibility, not just a clean product narrative.
Why does Google's pattern of small AI acquisitions matter to the strategic vs. tuck-in debate?
Google's typical deal targets a specific technical capability or team and is priced on cost replacement and bolt-on potential, not on standalone revenue, which makes it a tuck-in by definition. When executives compare these quiet deals to a $27.7 billion Slack acquisition, they sometimes confuse the frequency of small deals with the logic of big ones. The small deals are often the disciplined ones precisely because they are priced rationally for what they actually buy.
What is the operator playbook for evaluating an M&A target?
Ask four questions before signing. Is the target a standalone path to my total addressable market, where no points to a tuck-in. Does my roadmap absorb or replace the target's product, where replace points to a tuck-in. What customer overlap do we have, where minimal points strategic and high points to integration risk. What happens to the target's brand, team, and org after close, where independence points strategic and absorption points to a tuck-in. If you cannot answer these, you are pricing on narrative.
Colson Founder & Tech Business Analyst
Colson is the founder of ColsonSuperApps LLC and a multi-product software operator, shipping a consumer SaaS platform, a B2B SaaS product, and a portfolio of mobile apps. He writes siliconcent from the operator's chair — dissecting the same unit economics in public filings that he runs internally: CAC payback, LTV/CAC, net revenue retention, and gross margin.
- Founder, ColsonSuperApps LLC
- Operator of a consumer SaaS platform, a B2B SaaS product, and a mobile app portfolio
- Reads 10-Ks, S-1s, and proxies as primary sources