Kashi · J-StarX Pitch v3 2026-06-09 ← package
★ 締切 2026-06-22 · 残り 13 日

J-StarX SV Extended Program v3

PITCH_DOCTRINE.md (= 同 session 2026-06-09 生成) 完全準拠。 v2 の 8 violation 修正済、 forbidden registry 16 phrase 0 hit。

使い方: 30 秒 = 申込フォーム短文用 / 60 秒 = エレベーター・偶然遭遇 / 3 分 = J-StarX 申込ビデオのメイン / 5 分 = 面接・Demo Day backup。 Application form の各質問にはセクション「Application Q&A」 をそのまま貼る。
30 秒

申込フォーム短文用

30s · ~300字
「日本では、 退職代行サービスが普及している。 社員が第三者に金を払って辞めてもらう。 これは、 組織内の対話が崩壊している可視的な症状です。 Kashi は会議の構造 (= 誰が誰に話し、 質問が循環したか) を計測し、 内容は読まない、 感情も読まない、 個人をスコアリングしない。 LLM ではアーキテクチャ的にできない 監査可能 + 再現可能 + 内容不問 の 3 性質を持つ。 EU AI Act Annex III §4 に最初から適合する設計。 6 年前、 自分が取締役を務めた小さな会社で、 良い人材が静かに去っていくのを見続けた。 そのため、 私が作る」
短縮版 · ~200字
「Kashi は職場の同期型会議の構造を計測する。 内容不問、 感情不問、 個人スコアリングなし。 LLM では構造的にできない 3 性質 (監査可能・再現可能・内容不問) と、 EU AI Act Annex III §4 への初期設計適合。 6 年前から個人で追っている問題」
60 秒

エレベーター

60s · ~110w

In Japan, resignation agencies are now a thing — employees pay third parties to quit for them. To me, that's the visible symptom of communication breakdown companies notice too late.

Six years ago I watched it from a board seat — the best people left quietly while every dashboard said fine. So I'm building Kashi: we analyze the structure of how teams talk — turn-taking, who gets interrupted, who stops speaking — never content, never emotion.

Our moat is three architectural properties LLMs structurally cannot match: auditable, reproducible, content-blind. The doctrine is baked into our data layer, not into a prompt.

Pre-pilot, 908 tests, 25% reply rate on customer discovery. Filipino-Japanese, Keio business undergrad, building with a co-founder-level teammate.

Kashi helps companies see warning signs before silence becomes resignation.

pace 110-120 wpm OK · 息継ぎ最低 2 回 · 「solo founder」「deterministic」「Article 5(1)(f)」 0 hit
★ 3 分 · J-StarX 申込メイン

3 分 pitch (~330w / 3:00 at 110wpm)

3min · ~330w

Hi, I'm Justine, and I'm building Kashi.

In Japan, we now have something called resignation agencies — where employees pay a third party to quit their job on their behalf. I see it as the visible symptom of a deeper dialogue breakdown inside organizations. Companies communicate more than ever, but cannot see when communication is starting to break down. By the time HR or executives notice, the best person has already mentally left.

I'm building Kashi because I lived this. Six years ago I joined the board of a small company in Japan and watched our best people leave, quietly, while every dashboard said fine. I'm Filipino-Japanese, finishing Keio business school, building with a co-founder-level teammate. No one else I know sits in both cultures and has spent six years staring at this exact gap.

Kashi analyzes the structural patterns in synchronous meetings — turn-taking, who gets interrupted, who stops speaking. Never content. Never emotion. Never employee scoring.

Why won't GPT eat us? Three architectural reasons.

One — our moat is three properties LLMs structurally cannot match: auditable, reproducible, content-blind. LLMs are probabilistic by design — same input, different output — opaque, and read content by design. For regulated workplace use, those aren't feature gaps — they're regulatory deal-breakers.

Two — longitudinal baselines require persistent state, role-bounded storage, k-anonymity, audit logs. By the time a GPT wrapper builds equivalent state, we have N years of baseline they don't have.

Three — our doctrine is baked into the data layer: SQL + RLS + contracts physically exclude individual scoring, ranking, HR decisions. A GPT prompt can be rewritten next month. Ours can't. Moat is what we refuse to do, and the fact that we can prove we can't do it, not just that we don't.

Our regulatory lane is EU AI Act Annex III §4 — workplace AI monitoring as high-risk. We were designed to comply from day one.

Our outcomes are concrete: in the named ICP — Tokyo knowledge-work SMBs of 50 to 500 — pilots target Signal-to-Action within SLA above 80%, voluntary turnover reduction of 10 to 20 percent, employee NPS above 7.

Success has three phases: 5 paid pilots in 12 months; 50 customers in 24 to 36 months, 30 via 産業医 / 社労士 / coach reseller channel; in 5 years, the default trusted lane when regulation lands.

Pre-pilot — 908 tests, 25% reply rate on customer discovery.

Kashi helps organizations see the warning signs before silence becomes resignation. Thank you.

Delivery notes — 3min:
• Pace ~110 wpm (Justine natural ~94 wpm)、 録画して時間調整
• Pause: "resignation agencies" 後 2 拍 / "I lived this" 前 1 拍 / "Three architectural reasons" 後 1 拍 / "Moat is what we refuse..." を 意図的にスローダウン
• トーン: Origin = soft personal / Moat 3-beat = sharp confident list-like (= 暗記レベル) / Outcomes = matter-of-fact NOT excited / Success = numerical calm
★ Alchemist 詰められた 3 質問の v3 回答

Application form Q&A (= pre-built)

J-StarX 申込フォームの各質問にこれをそのまま貼る。

Q. What is your moat / defensibility?
Three architectural properties LLMs structurally cannot match. One — auditable, reproducible, content-blind. LLMs are opaque, probabilistic, and read content by design. Two — longitudinal baselines require persistent state, role-bounded storage, k-anonymity. By the time a GPT wrapper builds equivalent state, we have N years they don't. Three — our doctrine is baked into the data layer: SQL + RLS + contracts physically exclude individual scoring, ranking, HR decisions. A prompt can be rewritten next month. Ours can't. The moat is what we refuse to do, and the fact that we can prove we can't do it, not just that we don't.
Q. What outcome do customers get?
Three concrete outcomes within the named ICP (Tokyo knowledge-work SMBs of 50-500). (a) Signal-to-Action SLA achievement above 80% (= manager executes the indexed Playbook move and logs the action within 14 business days). (b) Voluntary turnover reduction of 10 to 20% during pilot, measured against the customer's own 12-month baseline. (c) Employee NPS above 7, gated on 60%+ adoption of the worker-first 24-hour dashboard.
Q. What does success look like?
Three phases. Phase 1 (12 months): 5 paid pilots, ICP-matched, SLA achievement 80%+, NPS 7+, at least one renewal contract. Phase 2 (24-36 months): 50 paid customers — 30 of them arriving through 産業医 / 社労士 / coach reseller channels — 10,000 meetings per month analyzed structurally, EU Annex III §4 compliance verified by independent counsel. Phase 3 (5 years): when workplace-AI regulation lands across EU and Japan, Kashi is the default trusted lane for compliance-grade dialogue diagnostics — because we made the architectural choice on day one not to be weaponizable.
Q. What problem are you solving?
Japanese mid-sized companies are losing their best people to silent communication breakdown. Resignation agencies (退職代行) are the visible symptom: employees pay third parties to quit on their behalf. By the time HR notices, the person has already mentally left. There is no objective, structural early-warning system in this layer today.
Q. What is your unique solution?
Kashi measures the structure of synchronous knowledge-work meetings — turn-taking, interruption asymmetry, question circulation, who-returns-to-whom — using a system that is auditable, reproducible, and content-blind. We never read content. We never score individuals. We never predict who will quit. We detect structural antecedents of dialogue breakdown, paired with a co-authored Manager Playbook bound by a 14-business-day documented-action SLA.
Q. Why you / why now?
I lived this. Six years ago I joined the board of a small company in Japan and watched our best people leave, quietly, while every dashboard said fine. I'm Filipino-Japanese, finishing Keio business school, reading both Japanese indirectness and Western directness from the inside. Building with a co-founder-level teammate. No one else I know sits in both cultures and has spent six years staring at this exact gap. As for why now — EU AI Act in force from February 2025 with Annex III §4 covering workplace AI monitoring; Japan's パワハラ防止法 in force for SMEs since 2022; and the resignation-agency phenomenon is a now-visible symptom of the cost of ignoring this layer.
Q. What is your current traction?
Pre-pilot. 908 reproducible tests pass. 25% reply rate on customer discovery outreach (~28 contacts). Turn-3 organic convergence with three practitioners on the core metric (= they reached for "questions circulate or stop at whom" in their own words without prompt). Recruiting 産業医 / 社労士 / coach co-authors for the Manager Playbook. Drafting Annex III §4 legal memo with EU labor / AI counsel.
Q. What support do you need from the program?
(a) Investor introductions in the Bay Area for regulated B2B SaaS specifically. (b) Operator introductions for our reseller-channel hypothesis — coaches, EAP providers, organizational psychologists in US and Japan. (c) Legal-counsel referrals for EU Annex III §4 memo and US workplace AI litigation hold. (d) Diaspora founder network (Filipino-American + Japanese-American) for talent and design-partner pipeline.
提出までの 13 日

Timeline

Dateアクション
06-09v3 完成 (= この doc) + Justine 冷静に read
06-10 ~ 1260s + 3min を 1 日 5x cold で muscle memory 化
06-13 ~ 15自己録画 → 自己評価 → 弱点 identify (Q1/Q2/Q3 で詰まる箇所 listing)
06-16 ~ 19J-StarX 申込フォーム書き出し (= Application Q&A をベースに)
06-205min full の最終リハ + form 全 question 完成
06-21Justine 最終 review + 提出準備
06-22★ J-StarX 提出 (締切日)
提出前チェック

Pre-submission checklist

v3 doctrine self-test 結果: 16/16 forbidden phrase が pitch body 内で 0 hit を達成 ✅。 PITCH_DOCTRINE.md §7 完全準拠。