7links

Note: This analysis is based solely on the self-reported description provided by the authors. No external verification, traction data, or financials are available.

The description states that 7links is a private relationship atlas. It organizes direct connections into islands such as family, friends, school, and work. Secondary connections remain visible but dimmed, and selecting someone reveals their branch and connection back to the user. It also includes features like relationship notes, event reminders, search, and a "Bridge Finder" that shows how two people are connected.

The tool uses React, TypeScript, Vite, D3, react-force-graph, Supabase Auth, and Vercel for its implementation. The interface is described as using custom layouts to keep direct connections organized while arranging secondary connections into readable trees.

Inference: The product appears to be a graph-based visualization tool for personal relationships, with an emphasis on privacy and user control over connection visibility.

The description states that 7links was inspired by Kazakh culture, specifically the tradition of Жеті ата (Zheti Ata), which emphasizes remembering seven generations of ancestors. This cultural inspiration is used to frame the product’s positioning as a tool that brings traditional values into modern relationships.

The product claims to help users "remember the connections, so you can focus on the people", suggesting an emotional or personal value proposition rather than a productivity one.

Inference: The positioning is rooted in cultural heritage and personal relationship management, not business or professional use. It is unclear whether this has evolved from an initial idea to a more refined vision.

The description does not clearly define the target customer or ideal customer profile (ICP). It describes 7links as a tool for organizing personal relationships and mentions that it supports "family, friends, school, and work" connections. However, no specific user persona or segment is identified.

Inference: The product appears aimed at individuals who value personal relationships and may be looking for tools to manage them more effectively, but the exact audience is not defined.

There is no evidence in the description of a business model or pricing strategy. The project is described as a hackathon submission with no mention of monetization, subscriptions, or paid features.

Inference: No commercial model is evident from the self-reported description.

The product was built using:

• Frontend: React, TypeScript, Vite
• Backend/Database: Supabase Auth
• Visualization: D3, react-force-graph
• Deployment: Vercel

It includes features like:

• Graph visualization of relationships
• Search and event reminders
• Bridge Finder to show connection paths
• Privacy-first contact importing (mentioned as a future feature)

Inference: The tech stack suggests a modern web-based application with graph visualization capabilities. The use of Supabase implies a backend-as-a-service approach, but no details on scalability or data handling are provided.

The project is described as a hackathon submission to the OpenAI 2026 hackathon. It has:

• A team of two members
• No evidence of revenue, customers, or adoption
• No mention of user testing, feedback loops, or product iterations

Inference: The product is in an early prototype stage with no demonstrated traction or market validation.

The description does not provide any information on competitors. It does not reference existing tools for managing personal relationships or social networks.

Inference: No competitive landscape is evident from the self-reported description.

• No commercial traction or revenue: The product is a hackathon submission with no evidence of adoption or monetization.
• Unclear market need: There is no indication that users have expressed demand for such a tool.
• Limited team size: Only two members are listed, which may limit execution speed and scalability.
• Privacy and data handling: While privacy is mentioned as a feature, no details on how data is stored or protected are given.
• No pricing or monetization strategy: No indication of how the product will be monetized.

Inference: The lack of traction, unclear market need, and absence of a business model are significant red flags for commercial viability.

1. What specific user problem are you solving, and how do you know people care about it?
2. Have you conducted any user research or interviews to validate demand?
3. How do you plan to monetize the product, if at all?
4. What is your roadmap for scaling beyond a prototype?
5. What are the technical challenges in handling larger networks or syncing data across devices?
6. Are there any existing tools that already solve this problem, and how does 7links differ?