1 / 12

01The customer problem

Institutional research workflow

Analyst attention—not information—is the scarce resource.

Filings, alerts, headlines, and internal notes arrive continuously. Analysts still have to decide what deserves review, rebuild history, and defend the conclusion.

Too much informationManual comparisonRepeated searchingFragmented memory

Next Current tools organize information—but they do not resolve the attention decision.

02Current tools

Useful—but incomplete

Search finds documents. Summaries compress them. The analyst still has to decide what changed and why it matters.

The opportunity is not another feed. It is a governed layer between incoming information and analyst judgment.

What current tools do well

  • Deliver filings and alerts quickly
  • Search large document collections
  • Summarize individual documents
  • Support notes and collaboration

What remains manual

  • Compare against prior language
  • Judge review priority
  • Check earlier disclosure
  • Preserve a defensible evidence trail

Product wedge: rank changed disclosures, show the historical comparison, and keep the source evidence attached.

Next Six interviews shifted the design from summary generation to evidence-backed prioritization.

03Customer discovery

N = 6 completed interviews

Trust, fit, and prioritization mattered more than another summary.

Paraphrased findings only. Titles, employers, and direct quotations are not inferred.

Interview perspective, workflow need, trust requirement, and product implication
Interviewee · perspectiveWorkflow problemTrust requirementProduct implication
Matthew G. Surprenant
Search, Q&A, usability
Retrieval frictionAnswers trace to evidenceSource-linked excerpts
Bilal Mustafa
Systematic, cross-asset
Noisy prediction targetClaims match evidenceSeparate product from alpha
Matt DiCenso
Fundamental workflow
Manual prioritizationHistorical contextRank changes, show prior text
Joseph Marks
Innovation framing
Problem too broadTestable valueNarrow the beachhead
Redmond Costello
Enterprise implementation
Workflow disruptionIntegration and securityComplement existing systems
Krishna Valluru
Data, governance, analytics
Fragile research memoryProvenance and controlGoverned evidence record
Users neededPrioritization · comparison · visible evidence · relevance · low friction
Buyers and gatekeepers neededProductivity · adoption · integration · security · auditability · governance
The product changedEvidence-first ranking · side-by-side history · institutional memory · analyst accountability

Still unvalidated: measured time savings, repeat use, willingness to pay, buyer approval, and enterprise integration.

Next The interviews challenged a broad trading hypothesis that the empirical work had already put under pressure.

04The original hypothesis

The first experiment

Could news and filing language add incremental investment signal?

The original project treated document information as a potential input to return and risk prediction.

News + filingsPoint-in-time documents
Language featuresModel representations
Incremental signal?Locked empirical test
Investment outcomeReturn or downside risk

Claim under test

Added documents improve out-of-sample prediction.

Evidence standard

Locked comparisons, issuer-disjoint samples, and point-in-time inputs.

Decision rule

Do not turn a null or inconclusive result into a product claim.

Next The locked tests did not support the alpha claim—and the project preserved that result.

05The negative results

Disciplined innovation

The market claims were not supported. The evidence-processing capability was.

Negative and null results were preserved rather than tuned away.

Not supported

Incremental news or 10-K alpha

Adding 10-K information did not improve the existing 8-K and inexpensive-news model.

Not supported

Better expected-language reconstruction

The prior 10-K alone predicted the next filing’s representation better than augmented models.

Inconclusive

Disclosure-change downside risk

The product found evidence-backed changes; the bounded risk test did not establish a reliable signal.

Final research classificationINSUFFICIENT_EVIDENCE

Next The null result became a design input: refine the problem, not the statistics.

06The product pivot

Evidence changed the project

The research did not prove alpha. It revealed a better innovation opportunity.

Hypothesis tested. Result rejected. User problem refined. Solution redesigned. Next experiment defined.

Original ideaPredict returns
Empirical testLock the comparison
Null resultReject the claim
Customer discoveryListen for workflow pain
New problemFocus analyst attention
Working productEvidence-linked changes
Analyst pilotTest workflow value

Evidence changed the project rather than being tuned away.

Next The redesigned workflow turns a filing into a ranked, evidence-linked research record.

07How the workflow works

The MVP

From new filing to review-ready evidence in six steps.

Open the live workflow
  1. 1IngestPreserve source and filing time
  2. 2CompareMatch prior and current sections
  3. 3ClassifyCategory, direction, materiality
  4. 4Check earlier disclosure8-Ks and pre-filing headlines
  5. 5ExplainWhy it may merit review
  6. 6PreserveExport an auditable record
KHCThe Kraft Heinz Company
High materialityPreviously disclosedConfidence 0.947

Debt and refinancing language became more specific.

Added: acceleration, covenant breaches, waiver dependency, default, and access to the Senior Credit Facility.

Why review: financing access and cash-demand riskInspect evidence →

Next One frozen Kraft Heinz case shows how comparison and novelty work together.

08One real case

Kraft Heinz · 2023 10-K · Item 1A

A more specific debt warning—but not a wholly new issue.

Selected for evidence diversity and clarity, not later market performance.

Available at filing timePrior 10-K + current 10-K + strictly earlier 8-K and headline evidence

Prior filing

General refinancing risk

“Changes in financial and capital markets … may increase the cost of financing as well as the risks of refinancing maturing debt…”

Current filing

Specific covenant consequences

“The creditors who hold our debt could accelerate amounts due … [and we could be] unable to access our Senior Credit Facility.”
What changedDefault, acceleration, waivers, and facility access were added.
NoveltyPreviously disclosedAn intervening 8-K and earlier headline existed.
Analyst judgmentReconcile covenant headroom and waiver status.

Next The product demonstration is supported; alpha, adoption, and workflow benefit are not.

09Experimental extension

From evidence to a research question

A verified change can become a falsifiable research agenda—after a full-prior check.

RH demonstrates a grounded hypothesis with explicit uncertainty, not a recommendation.

Verified change
Full prior-evidence check
Economic mechanism
Falsifiable hypothesis
Skeptical review
Analyst decision
RH · PASS_HYPOTHESIS_ONLY

Evidence coverage is 1.00. The result is a research question requiring analyst and market-data checks.

DVN · PASS_HYPOTHESIS_ONLY

A second bounded case passed as a hypothesis only. Neither case produced an actionable trade view.

Human review pending

Independent evidence review and automated grounding checks are complete; formal blinded human ratings remain pending.

Open the frozen RH hypothesis · Open the frozen DVN hypothesis

Next A safe rejection can be as valuable as a publishable research question.

10Safe failure matters

EFX grounding correction

Full-prior retrieval stopped a plausible but unsupported story.

Safe rejection is a successful system outcome.

Missing context found

The selected prior excerpt omitted the already-disclosed $125M conditional top-up.

Roles corrected

$346.7M was a remaining balance; approximately $345M was a cash deposit. The quantities were not substitutes.

Mechanism pruned

Unsupported liquidity, reserve, and bondholder claims were removed.

Safe disposition

No actionable trade view was produced.

Two cases produced grounded research hypotheses. Six were safely rejected or held. None produced an actionable trade view.

View the frozen EFX grounding rejection

Next The evidence boundary remains explicit.

11Evidence boundary

Supported versus unsupported

A working product demonstration is not the same as a validated business or investment result.

Four labels keep the claims legible.

Supported
  • Reliable document processing
  • Historical comparison
  • Evidence-linked change detection
  • Point-in-time integrity
  • Reproducible classifications
Not supported
  • Incremental news alpha
  • Improved expected-language model
  • Causal prediction
  • Customer adoption
  • Willingness to pay
Inconclusive
  • Downside-risk signal
  • Economic usefulness of risk labels
Not tested
  • Analyst time savings
  • Recall and trust
  • Repeat use
  • Institutional-memory value

Next The next experiment is a controlled workflow pilot—not another unsupported trading claim.

12Pilot and discussion

Next experiment · 2–4 weeks

Can 3–6 analysts reach better-supported conclusions faster?

Compare the normal workflow with Pure News Intelligence-assisted review on a bounded set of 8-K and 10-K changes.

Primary measure

Time to identify and explain the most important change

Quality guardrails

Recall, agreement, correction burden, and evidence quality

Adoption signals

Repeat use, exports, stored-context usefulness, and preference

Questions for the professor

  • Is the customer problem focused enough?
  • Which user or buyer is still missing?
  • Which pilot metric should be primary?
  • What evidence would justify a go decision?

End Return to the overview or open the live workflow.