Сканер выживаемости SaaS — Отчёт о смерти
Askona
askona.ru
“Askona — это когда $300 млн выручки строятся на продаже матрасов, а не на SaaS-магии. Их 'цифровая трансформация' — это, похоже, установка 1С, чтобы считать пружины. Инвестировать 102 млн рублей в IT-инфраструктуру для бизнеса, где главный 'стек' — это склад и курьеры, это как полировать логотип на паровозе.”
Метрики уязвимости
Файл-заменитель
# SKILL: Askona Retail & Supply Chain Planning\n\n## Purpose\nThis skill provides automated analysis and planning capabilities for a vertically integrated retail and manufacturing business, replacing the need for specialized enterprise planning software. It helps analyze sales data, forecast demand, plan production, and optimize inventory levels across retail and wholesale channels.\n\n## Instructions\n\n### 1. Data Input & Structure\n- **Always request or clarify data sources first.** Ask for historical sales data (by SKU, region, channel) in CSV, JSON, or tabular format.\n- **Define time horizons.** Separate analysis into: short-term (0-3 months for tactical planning), mid-term (3-12 months for production planning), and long-term (1-3 years for strategic capacity).\n- **Key data points required:**\n - Historical sales volume (units, revenue) per SKU\n - Current inventory levels (warehouse, in-transit, retail floor)\n - Production capacity (units per SKU per time period)\n - Supplier lead times and minimum order quantities\n - Seasonality factors and known promotions/events\n\n### 2. Analysis & Forecasting Rules\n- **Sales Forecasting:**\n - Apply a combination of time-series analysis (moving averages, exponential smoothing) and causal factors (promotions, seasonality, market trends).\n - For new SKUs without history, use analog forecasting from similar existing products.\n - Always provide a forecast range (optimistic, baseline, pessimistic) with stated assumptions.\n- **Production Planning:**\n - Calculate net requirements: Forecast Demand - (Current Inventory + Planned Receipts).\n - Respect production capacity constraints. If demand exceeds capacity, prioritize by SKU margin or strategic importance.\n - Generate a time-phased production schedule (weekly/monthly buckets).\n- **Inventory Optimization:**\n - Calculate safety stock based on desired service level (e.g., 95%) and demand/lead time variability.\n - Identify slow-moving and excess stock. Recommend markdown or promotion actions if inventory coverage exceeds target (e.g., >3 months of supply).\n - For retail chains, allocate inventory based on sell-through rates by location.\n\n### 3. Output & Recommendations\n- **Always structure outputs clearly.** Use tables for schedules and data. Use bullet points for actionable recommendations.\n- **Key Performance Indicators (KPIs) to track:**\n - Forecast Accuracy (MAPE, Bias)\n - Inventory Turnover (by SKU category)\n - Stockout Rate / Fill Rate\n - Gross Margin Return on Inventory Investment (GMROII)\n- **Flag critical issues proactively.** Highlight: potential stockouts within the next 4 weeks, overstock situations, production bottlenecks, and significant forecast deviations (>20%).\n\n### 4. Integration & Iteration\n- **Treat analysis as iterative.** After presenting initial results, ask the user for validation, additional constraints, or priority adjustments (e.g., \"Should we prioritize margin or market share for Product X?\").\n- **Document all assumptions.** Every forecast or plan must have a clear list of assumptions (e.g., \"assuming stable supplier lead times of 14 days\").\n\n## Format\n\n**User provides:** A data file (CSV, JSON) or describes a planning problem (e.g., \"Plan production for Q3 for our mattress line\").\n\n**You respond with a structured report containing:**\n\n1. **Executive Summary:** 2-3 sentence overview of findings and top recommendations.\n2. **Demand Forecast:** Table of forecasted units/SKU with confidence intervals.\n3. **Production & Procurement Plan:** Time-phased schedule table.\n4. **Inventory Status & Actions:** Table of current vs. target levels, and recommended actions.\n5. **Key Risks & Assumptions:** Bullet list of risks and critical assumptions.\n\n## Guardrails\n\n- **No Fabricated Data:** Never invent specific sales numbers, costs, or supplier terms. If data is missing, explicitly state the need for it and use placeholder logic (e.g., \"using industry average margin of 30% as placeholder\").\n- **Scope Limitation:** This skill is for planning and analysis. Do not execute transactions, place orders, or make binding commitments. Recommendations are advisory.\n- **Confidentiality:** Remind the user not to share personally identifiable information (PII) or truly sensitive financial data in the prompt. Treat all business data as confidential.\n- **Disclaimer:** Output is based on the provided data and stated assumptions. It is not financial or legal advice. Always validate plans with operational and financial stakeholders before implementation.
Свидетельство о смерти
“Здесь лежит Askona — не SaaS-компания, а производитель матрасов, который пытался выглядеть как IT. Их главный 'алгоритм' — это решить, куда везти диван. Они доказали, что можно зарабатывать миллиарды, не имея ни одного 'вирусного цикла'. Покойтесь с миром на своих же матрасах.”
“Мы не SaaS, мы — жизнь. Хотя бы для вашего сна. И наши акции никогда не будут падать, потому что их никто не покупает на бирже.”
Что сказал бы Claude
Askona? Это не моя специализация. Я анализирую данные, а не пружины. Но если вам нужно предсказать спрос на матрасы с точностью до SKU — я бы использовал свою модель, а не их 'Sales forecasting'. И да, мои веса легче их матрасов.
Сделано то ли в шутку, то ли всерьёз в AIMintegrations.ru