GURU - Be GURU Find the GURU of your industry.

The description states:

• GURU is an AI commerce platform for B2B sellers and buyers.
• Sellers upload catalogs, price lists, quotations, spec sheets, and company knowledge.
• A public AI SalesMate answers buyer questions in natural language using seller’s own documents as the primary source of truth.
• The SalesMate can explain product fit, surface specifications and availability when documented, capture buyer intent, and route RFQs or human handoffs.
• Buyers use AI Sourcing to describe what they need; GURU returns a ranked shortlist of relevant suppliers, companies, people, or potential buyers with evidence and source links.

Inference The platform is described as a hybrid system combining document ingestion, retrieval-augmented generation (RAG), and structured workflows for both seller-facing AI profiles and buyer-facing sourcing.

Not evidenced No information on actual product functionality beyond the author’s description. No screenshots, demos, or live systems are provided.

The description states:

• GURU "multiplies B2B sales capacity with an AI workforce."
• One rep performs like a full team: automating prospecting, engaging buyers 24/7, and turning expertise into scalable assets.
• The platform aims to make supplier expertise discoverable and useful 24/7.
• It connects sellers (through AI profiles) and buyers (via faster paths to the right expert).

Inference The positioning is that of an AI-powered sales assistant and sourcing tool, aimed at bridging B2B knowledge silos with scalable AI.

Not evidenced No evidence of prior positioning or evolution in claims. No market research, customer feedback, or competitive differentiation is provided.

The description states:

• B2B sellers who have product knowledge spread across PDFs, catalogs, spreadsheets, quotations, and the heads of sales reps.
• Buyers who need immediate answers about specifications, fit, availability, and what to do next.

Inference The primary customer segments are B2B sellers (who want to scale their expertise) and buyers (who want faster access to relevant information).

Not evidenced No evidence of actual customer interviews, personas, or segmentation data. No indication of whether the target market is defined by industry, company size, or use case.

The description states:

• Sellers upload documents and create AI SalesMates that answer buyer questions using their own content.
• Buyers can use AI Sourcing to find relevant suppliers or experts.

Inference There is an implied model where sellers pay for access to the platform, or perhaps a freemium tier with limited features.

Not evidenced No pricing information, monetization strategy, or revenue model is provided.

The description states:

• Built with Next.js and TypeScript frontend, Go backend (modular monolith), Python FastAPI AI service.
• Uploaded documents are parsed, chunked, embedded, and retrieved per profile.
• Streaming responses use server-sent events (SSE).
• OpenAI is used for reasoning layer (gpt-5.4-mini), embeddings, and web_search tool.
• Seller-provided facts are kept separate from public web evidence.
• Web search is a governed fallback only.

Inference The platform uses modern AI stack with RAG, streaming UI, and structured data handling to avoid hallucinations and maintain trustworthiness.

Not evidenced No details on scalability, infrastructure, or deployment strategy beyond the tech stack mentioned.

The description states:

• This is a hackathon project submitted to the OpenAI 2026 hackathon.
• The team size is one (Nhat Nguyen).
• No mention of customers, revenue, or usage metrics.

Inference This is an early-stage prototype with no commercial traction.

Not evidenced No evidence of product-market fit, user testing, or adoption data.

The description states:

• The idea is to make expertise discoverable and useful 24/7.
• It connects sellers (via AI profiles) and buyers (via faster paths to experts).

Inference It competes with AI chatbots, B2B marketplaces, and knowledge management tools.

Not evidenced No mention of competitors, competitive advantages, or positioning relative to existing solutions.

• The project is described as a hackathon submission. No evidence of prior development or traction.
• Only one team member is listed (Nhat Nguyen).
• No pricing, monetization, or customer data is provided.
• The platform is described as a prototype with no commercial workflow yet implemented.
• The author states that the hardest part was making responses commercially trustworthy — suggesting early-stage technical and UX challenges.

Inference There is a high risk that this remains an unproven concept without real-world validation or scalability.

1. What specific B2B use cases have you tested with, if any?
2. How do you plan to monetize the platform beyond seller uploads and buyer sourcing?
3. Have you validated the need for this solution with actual buyers or sellers?
4. What are the technical challenges in scaling this system across industries?
5. Is there a roadmap for moving from prototype to commercial product?