J-StarX SV Extended Program v3
PITCH_DOCTRINE.md (= 同 session 2026-06-09 生成) 完全準拠。 v2 の 8 violation 修正済、 forbidden registry 16 phrase 0 hit。
申込フォーム短文用
エレベーター
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.
3 分 pitch (~330w / 3:00 at 110wpm)
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.
• 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
Application form Q&A (= pre-built)
J-StarX 申込フォームの各質問にこれをそのまま貼る。
Timeline
| Date | アクション |
|---|---|
| 06-09 | v3 完成 (= この doc) + Justine 冷静に read |
| 06-10 ~ 12 | 60s + 3min を 1 日 5x cold で muscle memory 化 |
| 06-13 ~ 15 | 自己録画 → 自己評価 → 弱点 identify (Q1/Q2/Q3 で詰まる箇所 listing) |
| 06-16 ~ 19 | J-StarX 申込フォーム書き出し (= Application Q&A をベースに) |
| 06-20 | 5min full の最終リハ + form 全 question 完成 |
| 06-21 | Justine 最終 review + 提出準備 |
| 06-22 | ★ J-StarX 提出 (締切日) |
Pre-submission checklist
- Q1 MOAT を 45 秒以内に cold で言える (= 鏡前実演)
- Q2 OUTCOME に buyer-side 定量 metric が 3 つ以上 (= SLA 80% / -10-20% turnover / NPS 7+)
- Q3 SUCCESS が Phase 1/2/3 定量化 (= 5/50/規制施行時 default lane)
- 「deterministic」 0 hit / 「Article 5(1)(f)」 0 hit / 「solo founder」 0 hit (= 自動 scan 済)
- Forbidden registry 16 phrase 全て 0 hit (= 自動 scan 済)
- Hook → Origin → Vision (= founder voice) ≤ 35%
- Spec / 908 tests / traction が最後に
- 「Kashi は退職を予測」 系 overclaim 0 hit