Model the consequences of acquiring a competitor.
Run "acquire competitor X" through Cascade before the board call. Six specialist agents trace integration, antitrust, talent-flight and deal-fail paths in parallel, each node probability- and confidence-scored, so the conversation shifts from "should we?" to "given the flagged path, what is the structure?"
Run Cascade- 1
Describe the task
Cascade takes a proposed acquisition, described in plain English, and maps what the deal actually sets in motion. Six specialist agents fan out from the transaction (economic, social, technological, political, legal, and environmental) and trace the paths corp-dev teams most often under-weight: antitrust exposure, integration drag, talent flight, and the scenarios where the deal fails outright. Every node carries a probability and a confidence score, so you walk into the board call with structure under the reasoning instead of a gut feel.
The tree is only as sharp as the deal you describe. Tell Cascade who the target is and why you want it, how you plan to pay and integrate, and which risks the board will press on, and every branch stays anchored to this transaction rather than describing acquisitions in the abstract. Name the antitrust and retention concerns explicitly and the agents weight those paths first.
Model the consequences of acquiring our closest competitor, a 140-person rival in the same category, for a mix of cash and stock, effective next quarter. Trace out to third-order effects across: - Regulatory (antitrust review, likely remedies, the odds the deal is blocked or conditioned) - Integration (product overlap, platform migration, customer churn during the transition) - Talent (key-employee flight risk, retention packages, culture clash) - Deal-fail scenarios (what happens to us competitively if the deal collapses mid-review) Score every node by probability and confidence, flag the highest-risk path at each depth, and say what would have to be true for it to break bad. End with the three consequences the board is most likely to overlook.
- 2
Give Cascade context
Point Cascade at the deal and the ground it sits on: who the target is, the rough shape of the consideration, the market you both compete in, and any regulatory history in the category. With that grounding, the antitrust and integration branches reason against this specific transaction instead of a generic roll-up.
The single most useful input is the market structure you are buying into: combined share, number of remaining competitors, recent enforcement in the sector. Cascade weights the antitrust path against how concentrated the market actually becomes, which is the branch corp-dev teams most reliably under-price.
Required contextA plain-English description of the deal, the target, the rationale, and the rough considerationMarket context, the category you both compete in and roughly how concentrated it is post-dealOptional contextRegulatory history in the sector, recent reviews or blocked deals that anchor the antitrust branchA retention picture, which people are load-bearing, so the talent-flight path scores against real riskA depth setting, push the antitrust or integration branch past three orders where the board will presstarget-overview.pdfmarket-share-data.xlsxprior-deals-in-sector.csv - 3
What Cascade creates
Cascade streams the tree as it builds, so you watch the deal paths open in real time. The finished output is a navigable, probability- and confidence-scored consequence tree, every node a specific downstream effect of the transaction, with the highest-risk path flagged at each level and a short list of the consequences boards most often miss.
From Cascade: Mapped consequences of the 140-person competitor acquisition, three orders deep across four deal paths.
70%Antitrust-review path weight3rdOrder depth reached4High-risk paths flaggedHighest-risk branches4 pathsBranch Depth Consequence Breaks bad if Regulatory 2nd Combined share crosses the threshold that triggers a second-request review Post-deal category share passes 40% in the core segment Talent 3rd Two of the target’s founding engineers walk within the first two quarters Retention packages are not locked before the announcement leaks Integration 3rd Forced platform migration churns the target’s mid-market base during transition Migration runs past two quarters and support SLAs slip Most-overlooked consequences3 itemsConsequence Order Why it gets missed A conditioned approval could force divesting the overlapping product line 2nd Teams model “approved” or “blocked,” not the remedy in between The deal-fail scenario leaves the target free to sell to a larger rival 3rd Downside is scoped as “status quo,” not “competitor gets stronger” "The antitrust path carries the most weight: I score a second-request review around 70% once combined share passes 40%, and a conditioned approval is the branch teams skip. Want me to expand the remedy scenario to fourth order, or model the deal-fail path where the target sells to a larger rival instead?"
- 4
Follow-up prompts
Expand the antitrust path one level deeper
Cascade defaults to three orders, but the branch the board will press hardest can go further. Push the regulatory path to fourth order to see how a conditioned approval or forced divestiture actually reshapes the combined business.
Expand the regulatory branch to fourth-order effects. Focus on the conditioned-approval scenario: what a forced divestiture of the overlapping product line does to the deal rationale, the price we should pay, and the integration plan.
Model the deal-fail scenario on its own
The downside of a collapsed deal is rarely just the status quo. Have Cascade trace the deal-fail path where the target ends up with a larger rival, and score how much worse your competitive position gets.
Model the deal-fail scenario as its own tree: the review drags, we walk, and the target sells to a larger competitor instead. Score the second- and third-order effects on our market position versus where we are today.
Compare this deal against building instead
Acquiring is one of two futures. Run compare mode against a build-it-in-house scenario so the board sees what the acquisition uniquely causes versus organic investment.
Run a side-by-side comparison: acquire the competitor versus invest the same capital in building the capability in-house over 18 months. Diff the two trees and show what the acquisition uniquely buys and what it uniquely risks.
- 5
Tips and troubleshooting
Name the market structure, not just the target
The antitrust branch reasons from concentration. “Acquire competitor X” fans out vaguely; “combined 42% share in a category with three remaining players” lets Cascade weight the review path against a real threshold rather than a generic risk flag.
Read probability and confidence together
A 70% antitrust path at low confidence is a very different board conversation than 70% at high confidence. The confidence score tells you where Cascade is reasoning past the evidence you gave it, and exactly which branches to pressure-test with counsel before the call.
Scope the deal-fail path deliberately
Teams model approval and blockage but stop there. The most expensive branch is often the one where the deal collapses and the target strengthens a rival. Ask for it explicitly so the downside is scoped as a moving competitor, not a frozen status quo.
Ready to try it yourself?
Describe the deal in a sentence, and walk into the board call already knowing the antitrust, talent, and integration paths the room will press on.
Run Cascade