The thesis doesn't stop at IC. Neither does the evidence.
Most firms rebuild the case at every stage: a sourcing memo, a diligence pack, an IC deck, a value-creation plan, an exit story. SignalPattern carries one evidence chain through all of them, and every outcome feeds the next deal.
Illustrative deal · Middle-market buy-and-build
The best target on paper can be the worst one to own.
Which three add-ons fill the platform’s service gaps, and which top-ranked target should we not buy?
What surfaces
A sector watch on hiring, pricing and leadership changes surfaces 40 add-on candidates.
What we evaluate
Owners and an approach plan for each shortlisted target.
Shortlist 3 of 40. The financially strongest candidate is dropped on the ninth pass because employee-sentiment and integration-friction signals contradict its numbers.
How it moves forward
Add-on financing.
Potential capital: Unitranche lender · Co-invest LP.
Post-close integration outcomes write back against the prediction.
Validate the thesis, claim by claim.
Break the investment thesis into the claims that must hold. Each one is sourced, scored and stress-tested, with causal drivers and counterfactuals, so the IC sees what supports the deal and where it is thin, before anyone signs.
You make the bet. We make it defensible.
Know when the thesis moves, across every portco.
Always-on watches across market, competitor, regulatory and supply-chain signals. When something changes, an evidence-backed brief lands in review. Approve it, and it becomes context for the value-creation plan, the next board pack, or a fresh run of the thesis.
Every IC file answers the eight questions.
Analysis got cheap. Conviction did not. The decision file is simple enough to sign, structured enough to defend, and stays inspectable after the deal closes.
Open the decision file
Know what supports the decision.
Where did this data come from?
Every source is registered, with run-level lineage from ingest to output.
Can the claim be traced?
Every material claim opens to its source and the transform path behind it.
How confident are we?
Confidence is scored per claim and per task, and weak inputs cap everything built on them.
What are the weak spots?
Evidence gaps are flagged by task, and model disagreement is kept, not averaged.
What would change the answer?
Move the causal drivers to test a different set of assumptions. In TaskExecutor, edit the deliverable to create a counterfactual and revisit the decision.
Start with one question.
A live decision a portco faces now. Decision file, with receipts. Your operators test it. Expand it or stop. Your call.