OpenAI 2026 hackathon

Fast sales FB

商談後にトップセールスからFBもらえるPDCAプロジェクト

Solo project by KAITO KOBAYASHI · 0 likes · 0 comments

Archive position — measured, not model output

0 likes on Devpost

2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #4,068 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

What the company appears to be

Fast Sales FB is a self-reported AI-powered feedback tool designed for sales professionals. It claims to simulate input from a top salesperson by generating structured PDCA (Plan-Do-Check-Act) feedback after each sales call, using GPT-4o via OpenAI API.

What changed

The project was submitted as part of the OpenAI 2026 hackathon and is described as an experimental prototype with no known revenue, customers or traction.

Single most important open question

Is there any evidence that this concept has value beyond a one-off hackathon submission — particularly around adoption, usage friction, or real-world utility?

Back to contents

What The Product Actually Is

The description states that Fast Sales FB is a service that provides structured PDCA feedback to salespeople immediately after a sales call. It uses an AI (GPT-4o) configured with a top salesperson persona to generate feedback across four dimensions:

  • Plan: Hypotheses and preparation for next call
  • Do: Specific pointers on what worked or didn’t
  • Check: Evaluation of goal achievement
  • Act: Immediate next actions

The system is triggered by input from the user (via form or voice), which is then processed through OpenAI API and returned in a structured format. It also includes an automatic handoff from previous “Act” to next “Plan”.

Evidence

  • The author states: “Fast Sales FB は、商談後に AIトップセールスから即座に PDCAフィードバックを受け取れるサービスです.”
  • The author describes a workflow involving input → processing via OpenAI API → output in structured PDCA format.

Inference This is an AI-driven feedback loop designed to replicate expert coaching, but no evidence exists that it has been used beyond the prototype stage.

Back to contents

Positioning & Claim Evolution

The project positions itself as a solution to the long-standing problem of “top sales know-how being person-specific” and aims to make expert-level feedback available anytime, anywhere — via AI.

It claims to offer:

  • Instant feedback after each sales call
  • Structured PDCA framework for reflection and action
  • Replicable top-sales thinking through prompt engineering

The author also mentions that the idea originated from a simple question: “もし、商談直後にトップセールスが隣にいてくれたら?” (If only a top salesperson could be right next to you after each deal).

Evidence

  • The author states: “AIによって、そのトップセールスを 誰もが・いつでも・何度でも 呼び出せる仕組みを作りたいと考えました.”
  • The tagline reads: 商談後にトップセールスからFBもらえるPDCAプロジェクト

Inference The positioning is aspirational and focused on accessibility of expert feedback, but there is no evidence that this has been validated or adopted in practice.

Back to contents

Target Customer & ICP

The primary target customer appears to be individual sales professionals who are seeking structured feedback after sales calls. The description implies a focus on those who want to improve their performance using expert insights without access to a mentor or coach.

Evidence

  • The author states: “営業パーソンが商談直後に内容を入力するだけで…”
  • It is implied that the tool serves individuals rather than teams or organizations at large.

Inference The ICP seems to be a solo salesperson looking for performance improvement, but no segmentation or targeting data is provided.

Back to contents

Business Model & Pricing Evidence

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

Evidence

  • No mention of revenue streams, pricing tiers, or customer acquisition costs in the description.

Inference The tool likely does not have a commercialized business model yet — it remains an experimental prototype.

Back to contents

Technical & Delivery Signals

The project uses:

  • OpenAI API (GPT-4o) for feedback generation
  • Whisper API for optional voice-to-text transcription
  • Prompt engineering to simulate a top salesperson persona

It includes features like:

  • Input via form or voice
  • Structured output in PDCA format
  • Automatic handoff from “Act” to next “Plan”

Evidence

  • The author states: “使用技術” followed by OpenAI API, Whisper API, and Prompt Engineering.

Inference The technical stack is standard for AI-based tools but lacks evidence of scalability or integration with existing platforms like CRM systems.

Back to contents

Traction & Maturity Signals

There is no evidence of traction, user base, or product maturity beyond the hackathon submission. The team size is listed as one person (KAITO KOBAYASHI), and no customer data, usage metrics, or performance indicators are shared.

Evidence

  • Team size: 1
  • No mention of users, revenue, or adoption
  • Submitted to a hackathon

Inference This is an early-stage prototype with no signs of real-world deployment or user engagement.

Back to contents

Competitive Context

No competitive landscape is described. The author does not reference existing tools or platforms that offer similar functionality — such as CRM-based coaching tools, sales performance apps, or AI feedback systems.

Evidence

  • No mention of competitors or market positioning

Inference There is no indication of awareness of existing solutions in the space, nor any differentiation strategy beyond the use of AI and PDCA.

Back to contents

Key Risks & Red Flags

Key risks include:

  1. Lack of real-world validation: The tool exists only as a hackathon prototype with no evidence of adoption or usage.
  2. Over-reliance on prompt engineering: The quality of feedback depends heavily on how well the persona is defined — which may not scale.
  3. No integration capabilities: No mention of CRM or platform integrations, limiting practical utility.
  4. Single-person team: Limited capacity for development and iteration.

Evidence

  • Team size: 1
  • No mention of integrations or scalability
  • Submitted to a hackathon

Inference The risk of failure is high due to lack of traction, limited resources, and absence of product-market fit validation.

Back to contents

Diligence Questions To Ask The Founders

  1. What specific feedback has been generated so far? How does it compare to actual coaching?
  2. Have you tested this with real salespeople or just yourself?
  3. Is there any plan for integrating with CRM tools like Salesforce or HubSpot?
  4. What is the expected path from prototype to product — and how long will that take?
  5. Are there any early adopters or pilot users who have tried the tool?
  6. How do you intend to monetize this concept if it proves useful?

Back to contents

Investment/Partnership Verdict

Not evidenced.

The project is described as a hackathon submission with no evidence of traction, revenue, customers, or even basic product-market fit. The author’s own account does not suggest any commercial viability or scalability beyond the prototype stage.

Confidence level Low This is a self-reported idea with no external validation or data to support its potential for growth or investment.

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.