How to pressure-test a bull case against a 10-K

A bull case is useful only after it has been translated from a story into claims that can be checked. ThesisCheck's methodology treats that translation as the first step: separate what the thesis says from what the public record can actually support.

This is not a buy, sell, hold, rating, sizing, or price-target exercise. The goal is to build a clean source ledger: which claims are supported, which claims face bear-case pressure, and which claims remain missing from the filing evidence.

The primary source for this workflow is the company's annual report. The SEC's Form 10-K overview describes the filing as the annual report companies file with audited financial statements, while Investor.gov's 10-K reading guide highlights sections investors commonly review.

Start with the claim map

Write the bull case as a short list of claims before opening the filing. Each claim should be specific enough that a source can support or fail to support it.

Good claim-map entries look like this:

• Revenue growth is being driven by a named segment, not only by price increases.
• Margin expansion depends on operating leverage rather than one-time cost cuts.
• The company has enough liquidity to fund the plan without near-term refinancing pressure.
• The risk factors do not describe a dependency that would break the core thesis.

Weak entries are harder to verify: "management is excellent," "the moat is strong," or "the market is wrong" can be useful intuitions, but they need to be converted into observable evidence.

Read the 10-K in evidence order

The 10-K is long, so read it in the order that matches the thesis. For most bull cases, the highest-yield sections are business description, management's discussion and analysis, segment notes, liquidity, debt, and risk factors.

Use the business section to understand how management describes the company's economics. Use MD&A to compare that story with the period's results. Use the notes and risk factors to pressure-test the parts of the story that could be incomplete.

For example, a thesis about durable software growth should not stop at total revenue. It should check revenue concentration, remaining performance obligations if disclosed, margin movement, capitalized costs, customer concentration, and risk-factor language about competition or renewal behavior.

Separate support from pressure

A good source ledger does not treat all evidence as confirmation. It records different evidence roles.

• Support: a filing passage that directly backs a thesis claim.
• Bear-case pressure: a filing passage that makes the claim less complete or more conditional.
• Missing evidence: a claim that matters to the thesis but cannot be found in the reviewed filing sections.

This structure is why ThesisCheck also publishes a sample report: the output is more useful when readers can inspect the claim, source, and evidence status instead of receiving a summary verdict.

Build the internal link set

Each post in this methodology lane should connect back to the relevant hub and nearby guides. For this guide, the hub is the ThesisCheck methodology. Related spokes include the checkable thesis guide and the stock bear case analysis page.

That hub-and-spoke pattern keeps the topic useful for humans and legible for search engines: one hub explains the workflow, while each spoke handles a narrower task in the workflow.

Finish with the non-advice boundary

Pressure-testing a bull case should end with a cleaner research question, not a trading instruction. The final output can say that a claim is supported by a named source, contradicted by a filing passage, or not found in the reviewed evidence. It should not tell the reader what position to take.

That distinction keeps the workflow aligned with ThesisCheck's product boundary: descriptive, source-checked company research only.