-
-
BlindSpot Logo
Inspiration
Three different stocks. One shared supplier.
That is the idea behind Blindspot. Owning NVIDIA, AMD, and Broadcom might look like spreading your investments across separate businesses. But their company reports reveal a connection: all three disclose relationships with TSMC, the chip manufacturer.
I wanted to make those connections easier to see. An investor should not have to search through hundreds of pages just to begin understanding what links the companies they own.
#What it does#
Blindspot turns disclosed supplier relationships into an interactive map of your portfolio.
Enter your holdings and their dollar amounts, then reveal the connections. In the example portfolio, NVIDIA, AMD, and Broadcom account for $6,000 of a $10,000 total. Blindspot shows that those holdings share a disclosed supplier relationship with TSMC.
That 60% describes the value invested in connected companies not a prediction of losses.
Click a connection to see the supporting quotation, filing date, and original company report. Compare companies side by side to investigate shared suppliers. Open Coverage to see which evidence is published and which research still needs review.
The goal is simple: help people understand what connects their investments, with evidence they can check themselves.
How we built it
I built a web interface using HTML, CSS, and JavaScript, connected to a Python backend.
The backend matches manually entered holdings to published supplier relationships, calculates connected holding values, and returns the results for the interactive graph. Calculations use integer cents to keep dollar amounts consistent.
Each published relationship links to evidence from a public company filing, including the quotation, reporting period, and original source. The research workflow separates candidate relationships from published evidence so that an unreviewed claim does not automatically appear in portfolio results.
The application is deployed on Render and available through the custom domain blindspot.miami.
Challenges we ran into
The hardest problem was understanding what a company report actually says.
Mentioning another company does not necessarily establish a supplier relationship. It could describe a customer, competitor, former partnership, or future agreement. The product therefore needs to preserve the context behind every connection.
Another challenge was making the numbers understandable. Money invested in a connected company is not the same as money that would be lost during a supplier disruption. Blindspot makes that distinction explicit.
Finally, I had to bring the interface, backend, evidence workflow, hosting, and custom domain together into a working demo.
Accomplishments that we're proud of
I built a working journey from a list of holdings to a shared supplier graph to the original supporting evidence.
The most satisfying moment is seeing three familiar company names converge on one supplier and then clicking through to understand why.
Blindspot also makes incomplete coverage visible. It distinguishes published evidence from pending research and avoids treating missing information as proof that a company has no dependencies.
What we learned
I learned that the difficult part of a research product is not drawing a connection. It is establishing what that connection means and helping someone verify it.
I also learned how much clear presentation matters. A simple graph can make a complicated relationship understandable, but only if its labels, calculations, and evidence are precise.
What's next for Blindspot
The next step is to expand reviewed coverage across more companies, suppliers, and industries.
Future versions could monitor new filings, highlight changes in disclosed relationships, and explore dependencies further down the supply chain.
The goal remains the same: you know which companies you own. Blindspot helps you see what connects them.
Log in or sign up for Devpost to join the conversation.