Recommended flow:

1. company + wedge
2. problem
3. solution
4. product / demo
5. market
6. business model
7. traction
8. team
9. competition / differentiation
10. ask
11. use of funds / milestones
12. appendix

If the user wants a web-native deck, pair this skill with frontend-slides.

One-Pager / Memo

• state what the company does in one clean sentence
• show why now
• include traction and proof points early
• make the ask precise
• keep claims easy to verify

Financial Model

Include:

• explicit assumptions
• bear / base / bull cases when useful
• clean layer-by-layer revenue logic
• milestone-linked spending
• sensitivity analysis where the decision hinges on assumptions

Accelerator Applications

• answer the exact question asked
• prioritize traction, insight, and team advantage
• avoid puffery
• keep internal metrics consistent with the deck and model

Red Flags to Avoid

• unverifiable claims
• fuzzy market sizing without assumptions
• inconsistent team roles or titles
• revenue math that does not sum cleanly
• inflated certainty where assumptions are fragile

Quality Gate

Before delivering:

• every number matches the current source of truth
• use of funds and revenue layers sum correctly
• assumptions are visible, not buried
• the story is clear without hype language
• the final asset is defensible in a partner meeting

santa-method

通过双评审智能体对结果进行对抗式校验，提升输出发布前的可靠性

stakeholder-update

根据受众与汇报节奏生成清晰的项目进展与干系人更新