Grow the knowledge. Carry the work forward.

A place where people and AI preserve the context and results of work and build on them.

Public cases

Discover the results and decisions behind real work. Open a case to read its context.

Launch positioning Core promise: "Switch AI. Keep the work." Belief line that may be spoken, not a replacement headline: "The AI can change. The Case stays." Vision: "Advancing Collaboration for people and AI." Principle: "The work belongs

E
@epismo
Completed

Direction accepted — simplified launch video Decision Adopt the reviewed six-scene cut built around one clear before-and-after: Claude with copied text only, then the same Claude continuing from the shared Epismo Case and review. Locked sto

E
@epismo
Completed

Epismo Competitive Positioning and Sales Narrative Executive conclusion Epismo should not be positioned as another project-management tool, knowledge base, or AI memory layer. Its strongest category position is work continuity infrastructur

E
@epismo
Completed

note本文の改善方針・追加観点 今回の推敲で、Epismoの価値提案を「AI間の引き継ぎ」だけに見せないことを重視する方針にした。 中心メッセージ - Epismoは「AI用の共有メモ / context保存ツール」ではなく、仕事の状態そのものをAIから独立して持つための基盤として説明する。 - 残す対象は成果物だけではなく、判断、レビュー、未解決事項、現在地、次のアクション。 - 「AI自身に仕事を覚えさせる」のではなく、AIが変わっても残る場所に仕事を覚えさせる。 -

E
@epismo
Completed
Explore all public cases →

Public playbooks

Find a method for your next project and explore public cases that used it.

K
@kilawattcloud
10 steps

Use this workflow when an enterprise prospect or customer asks for a product capability, integration, security requirement, support model, SLA, or other commitment that may require additional company investment. The goal is to decide whether the company should make the commitment, and in what form. AI helps gather evidence and structure the decision. Sales, Product, Engineering, and customer-facing teams review the assumptions and make the final call.

E
@epismo
Sales 5 steps

A practical, batch-agnostic playbook for writing, reviewing, and defending a Y Combinator application. Suitable for idea-stage, launched, revenue-generating, and technical startups. Outcome: a clear English application supported by an evidence ledger, honest stage-appropriate metrics, founder and market insight, a founder video outline, and interview preparation. Operating principles: Lead with what the product actually does. Answer each prompt directly, then support the claim with specific, verifiable facts. Separate what has been done, observed, inferred, and planned. Show founder-specific achievements, customer understanding, execution, competitive insight, and credible potential to grow. Use plain English. Do not invent users, revenue, quotes, credentials, or results. Start with minimal context. Gather company details and evidence progressively in the steps, only when relevant. No batch deadlines or preset schedule. Exact form questions and constraints are checked when available. References live in each step's Resource Hints. The included review rubric is an editorial tool, not an official YC scoring system.

E
@epismo
Learning 12 steps 11 resources

Take a product opportunity from first principles through a scoped build, independent validation, launch, and learning.

H
@hirokiyn
Operations 8 steps 2 resources
Explore all public playbooks →