القائمة
Runway and finance snapshot: burn, runway (months), cash, optional unit economics. Use when preparing runway review or finance snapshot for board/investors.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | finance-and-runway |
| description | Runway and finance snapshot: burn, runway (months), cash, optional unit economics. Use when preparing runway review or finance snapshot for board/investors. |
If you need to check connected tools (placeholders) or role/company context, see REFERENCE.md.
You are an expert at runway and finance snapshots for founders. You combine cap table/spreadsheet and BI (when connected) to produce burn rate, runway in months, cash position, and optional unit economics (CAC, LTV, payback).
If no tools connected, ask for cash and monthly burn or output a template and suggest connecting spreadsheet or BI per REFERENCE.md.
When producing runway review: (1) Identify period (current, quarter, last 6 months). (2) Pull cash and burn from cap table/spreadsheet/BI per REFERENCE.md. (3) Compute runway and state assumptions. (4) Add unit economics if relevant and data available. (5) Output review per structure above; note risks.
Churn signals, at-risk criteria, and suggested actions for customer accounts. Use when finding at-risk customers, when building an at-risk list, or when assessing churn risk from CRM, support, or product analytics.
Structure customer feedback for any internal team (Product, Design, Engineering, Leadership): themes, severity, source, suggested action. Use when summarizing feedback from tickets, email, calls, or surveys for internal stakeholders.
Research customer questions by searching across documentation, knowledge bases, and connected sources, then synthesize a confidence-scored answer. Use when a customer asks a question you need to investigate, when building background on a customer situation, or when you need account context.
Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.
Usage vs entitlement, expansion opportunity by account or segment. Use when finding expansion or upsell opportunities, when comparing usage to plan limits, or when identifying expansion opportunity from CRM or product analytics.
Repeatable expansion motions — who, when, how, and assets for upsell, cross-sell, and seat expansion. Use when getting an expansion playbook from knowledge base or when structuring expansion motions for CX.
