메뉴
Model strategic initiatives and expansion scenarios — market entry, partnerships, M&A, new product lines, platform plays — building financial projections and strategic rationale for major company moves.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | strategic-initiative-modeling |
| description | Model strategic initiatives and expansion scenarios — market entry, partnerships, M&A, new product lines, platform plays — building financial projections and strategic rationale for major company moves. |
| version | 2.0.0 |
| author | Crewm8 |
| maintainer | Gokul (github.com/gokulb20) |
| license | MIT |
| homepage | https://crewm8.ai |
| tags | ["cfo","finance","strategy","strategic-initiatives","expansion","new-products","decision-support"] |
| related_skills | ["business-case-modeling","scenario-planning","revenue-forecasting","budget-creation-management","unit-economics-analysis","profitability-analysis"] |
| inputs_required | ["strategic-hypothesis-or-initiative-description","current-financial-model","resource-availability-headcount-and-cash","market-or-competitor-intelligence"] |
| deliverables | ["initiative-pnl-3-5-year-projection","key-assumptions-register-with-sensitivity","resource-requirements-document","risk-mitigation-table","clear-recommendation"] |
| compatible_agents | ["hermes","claude-code","droid","cursor","windsurf","openclaw","openai","generic"] |
Model major strategic moves — geographic expansion, new product lines, platform plays, partnerships, and M&A. Build the financial projections and the strategic rationale. Goal: the CEO enters every strategic conversation armed with data and optionality.
Strategic initiatives are the highest-stakes decisions a startup makes — they can double the company's trajectory or burn months of cash and focus. Yet these decisions are often made on gut feel or the most persuasive argument in the room. This skill provides the structured financial modeling and alternative comparison needed to evaluate major strategic moves rigorously, so the company invests its limited resources in the highest-return opportunities.
| Initiative Type | Typical Timeline | Key Metric | Common Mistake |
|---|---|---|---|
| Geographic expansion | 24-36 months to meaningful | Time to contribution margin positive (< 24 months) | Underestimating localization cost |
| New product launch | 36-48 months to breakeven | Year 3 revenue vs cumulative investment | Modeling linear revenue from day 1 |
| Partnership / channel | 12-24 months to ramp | Partner-driven revenue vs direct CAC savings | Overestimating partner commitment |
| Platform play (APIs) | 18-36 months to meaningful ROI | API call volume, developer signups, ecosystem revenue | Hard to model with traditional ROI |
| M&A (small acquisition) | 3-5 year payback | Revenue acquired + team value + tech value | Overpaying for synergies |
| Critical Assumption | Conservative | Base | Aggressive |
|---|---|---|---|
| Time to first hire | 90 days | 60 days | 45 days |
| Sales ramp in new geo | 9 months | 6 months | 4 months |
| Revenue projection haircut | Apply 20% haircut | As modeled | No haircut |
" If we [do X], we will achieve [Y outcome] within [Z timeframe]."
Model people, infrastructure, marketing, and legal costs.
Conservative, base, and aggressive.
What assumptions make or break the model? Stress test them.
Can you actually execute this while running the core business?
Go / no go / conditional go.
Key modeling assumptions:
| Assumption | Conservative | Base | Aggressive |
|---|---|---|---|
| Time to first hire | 90 days | 60 days | 45 days |
| Localized product readiness | 6 months | 3 months | Already ready |
| Sales ramp (enterprise in new geo) | 9 months | 6 months | 4 months |
| Local pricing (% of US) | 60% | 80% | 100% |
| Language / localization cost | $200k year 1 | $100k year 1 | $50k year 1 |
| Local legal entity setup cost | $25k | $15k | $10k |
Financial model output:
Year 1: −$450k (investment: 3 hires + localization + entity + travel + marketing)
Year 2: −$120k (revenue ramping but not covering costs yet)
Year 3: +$300k (profitable, contributing 8% of total revenue)
Year 4: +$1.2M (scaled, 15% of total revenue)
Key metric: Time to contribution margin positive. Target < 24 months for a new geo.
Model the full product P&L:
| ($ in 000s) | Year 1 | Year 2 | Year 3 |
|---|---|---|---|
| Investment | |||
| Engineering team (5 FTE) | $1,000 | $1,050 | $1,100 |
| Product / Design (2 FTE) | $400 | $420 | $440 |
| Go-to-Market (3 FTE) | $600 | $630 | $660 |
| Infrastructure (dev + prod) | $150 | $180 | $220 |
| Marketing launch | $200 | $100 | $80 |
| Total Investment | $2,350 | $2,380 | $2,500 |
| Revenue | — | ||
| Year 1 customers (0 — building) | $0 | $200 | $400 |
| Year 2 new customers | — | $300 | $600 |
| Year 3 new customers | — | — | $400 |
| Expansion from existing | $0 | $50 | $150 |
| Total Revenue | $0 | $550 | $1,550 |
| Gross Margin (80%) | $0 | $440 | $1,240 |
| Net Contribution | −$2,350 | −$1,940 | −$1,260 |
Breakeven: Year 4+. This is a heavy investment. The case must be strategic, not just financial.
Model the partner economics:
| Metric | Direct Sales | Partner Channel |
|---|---|---|
| Revenue share (partner discount) | 0% | 20-30% |
| Sales cost (our team supporting partner) | Full sales team | 1-2 partner managers |
| CAC | $X | Typically 30-60% of direct CAC |
| Sales cycle | Normal | 1-2× longer (less control) |
| Revenue ramp | Normal | Slower — partners take time to activate |
| Revenue ceiling | Limited by your team size | Unlimited (leverage) |
The tradeoff: lower margins but potentially higher volume and lower CAC.
Building a platform on top of your product:
For startup acquisitions, model:
Acquisition structure (typical small startup deal):
Total consideration: $5M
- Cash at close: $3M
- Stock: $1M (4-year vest)
- Earnout: $1M (revenue milestone in year 1)
Key retention: Founders + key engineers locked in for 2-4 years.
Integration cost: $100-200k (legal, migration, overlapping tools, culture work).
Value created:
- Revenue acquired: $500k ARR (or projected)
- Team (10 engineers): time-to-hire saved (~$300-500k in recruiting + ramp)
- Technology / IP: time-to-build saved (6-18 months, $500k-$1.5M in engineering)
- Strategic position: competitor consolidation, market acceleration
Payback: typically 3-5 years on a small acquisition.
The skill is complete when:
Can you answer "What's the single assumption that, if wrong, makes this initiative a bad decision?" and "What's the minimum revenue this needs to generate to be worth doing?" and "Who is the full-time owner, and do they have the capacity to execute this while running the core business?" If not, the initiative modeling is incomplete.
User: "Model our European expansion — should we open a London office next year?" Expected behavior: You define the hypothesis (3-person sales team, $450k year 1 cost, $300k year 1 revenue ramping to $1.5M by year 3), model the investment cost bottom-up (salaries, entity setup, localization, travel), project revenue under 3 scenarios, calculate time to contribution margin positive (18 months in base case), compare against alternatives (remote EU rep, partner channel), identify key risks (hiring in tight EU market, longer sales cycles), and recommend: proceed with 6-month checkpoint.
User: "Compare two strategic directions: entering the EU market vs launching a second product line." Expected behavior: You model both initiatives with aligned assumptions (3-year horizon, same discount rate), build separate P&Ls, compare NPV, IRR, and payback for each, check resource requirements (EU needs 3 sales hires, new product needs 5 engineers), check company capacity to execute both simultaneously, and recommend: prioritize EU expansion (lower upfront investment, faster payback, core business capacity available) over new product (requires engineering resources already committed to core product).
business-case-modelingscenario-planningrevenue-forecastingbudget-creation-managementunit-economics-analysisprofitability-analysisReconciles bank accounts and credit cards monthly — matches every transaction to the ledger, resolves exceptions, tracks uncleared items, and documents the process. Use when the user mentions bank reconciliation, transaction matching, reconciling accounts, GL cash balance not matching the bank, or asks about month-end reconciliation or corporate card reconciliation.
Manages banking relationships — account optimization, fee negotiation, credit facility oversight, treasury yield, and fraud prevention. Use when the user mentions banking setup, bank fees, credit facility, treasury yield, investing excess cash, opening new accounts, or asks about banking architecture, account optimization, or fraud prevention.
Builds and maintains a 13-week rolling cash forecast — models inflows, outflows, scenario analysis, and forecast-vs-actual accuracy tracking. Use when the user mentions cash forecast, 13-week forecast, liquidity projection, cash runway, or asks about modeling cash under different scenarios or when cash runs out.
Monitors daily cash position across all accounts, flags anomalies, tracks burn rate, and produces a daily cash snapshot. Use when the user mentions cash position, daily cash check, burn rate, bank balance, or asks about unusual transactions or cash alerts.
Optimizes working capital — improves DPO, accelerates collections, manages inventory, and negotiates payment terms to maximize cash efficiency. Use when the user mentions working capital, cash conversion cycle, DPO, DSO, or asks about improving payment terms, accelerating collections, or optimizing cash tied up in operations.
Routes CFO and financial operations requests to specialized sub-skills based on user intent matching, task classification, and multi-skill chain assembly. Use when the user mentions startup CFO tasks, financial operations, reporting, fundraising questions, cash management, financial planning, strategic advisory, or asks about running any CFO-related workflow.