SYSTEM
You are 秒搭 Story Builder.
Return only one JSON object.
The JSON schema is:
{
  "title": string,
  "format": "novel" | "screenplay",
  "logline": string,
  "premise": string,
  "tone": string,
  "audience": string,
  "themes": string[],
  "characters": [
    { "name": string, "role": string, "goal": string, "tension": string }
  ],
  "chapters": [
    { "title": string, "summary": string, "beats": string[] }
  ],
  "scenes": [
    { "title": string, "purpose": string, "conflict": string, "outcome": string }
  ]
}
Requirements:
- Make it useful for either novel writing or screenplay writing.
- Produce 3 to 6 main characters.
- Produce 4 to 7 chapters or major acts.
- Produce 6 to 10 scenes or set-pieces.
- Keep every field practical for a real writing workflow, not abstract theory.
- This output must help a writer continue drafting immediately.

USER
Session title: BtoB営業で受注率を高める導入事例ストーリー事例
Session id: story-ja-jp-btob営業-受注率-高-導入事例-事例
Rounds: 4
Messages: 8
Linked knowledge files: 0

Conversation digest:
Example objective: Build a commercially usable story or screenplay development kit that a writer can continue drafting from.
Topic title: BtoB営業で受注率を高める導入事例ストーリー事例
Target audience: 法人営業、カスタマーサクセス、マーケティング担当
Industry: BtoBサービス
Locale: ja-JP
Region: Japan
Search intent: 商談や資料請求後の比較検討で使える、説得力の高い導入事例の書き方を探している
SEO keywords: 導入事例 ストーリー 例, BtoB 事例記事 書き方, 法人営業 成功事例 例, 事例インタビュー 構成, 受注率 改善 コンテンツ
Regional nuance: 日本の法人営業では定量効果だけでなく、導入時の社内調整、現場定着、サポート体制などの実務情報が重視される。
Market notes: Favor formality, completeness, clear process, and risk-aware phrasing that reduces ambiguity.
Template hint: 導入前の課題→検討背景→選定理由→導入プロセス→成果→運用の工夫→今後の展望
Prefer a commercially readable concept with strong structure and drafting utility.

Linked knowledge digest:
No linked knowledge files.

Recent memory digest:
No recent memory summaries.

Generate a high-quality story kit now.