The week flew by, but what you actually earned and what's still hanging is unclear. This brief closes the week with honest numbers: what grew, what dipped, what to watch on Monday — so you head into the weekend with clarity, not anxiety.
Run the Friday brief "wins and watch points." Pull the numbers, extract the essentials, and give the owner a clean picture of the end of the week.
Argument breakdown:
--lookback(default7d) —7d(one week) or14d(rolling two-week comparison)
Step 1 — Revenue pulse
Following the skill workflow business-pulse:
- Pull transactions from
~~платежи(YuKassa, Tinkoff Kassa) for the review window. - Pull deal closures from
~~crm(Bitrix24, amoCRM) for the same window. - Calculate the week-over-week revenue delta.
- Extract the top 3 revenue sources (product / client / channel) by contribution.
Step 2 — Sales breakdown
- List the top 5 products/services by volume and revenue.
- List the bottom 3 (anything that sold worse than expected versus the previous period).
- Flag any items with a sharp spike or drop (>20% change).
Step 3 — "Wins and watch points" summary
Output format (amounts in rubles, dates DD.MM.YYYY):
Бриф пятницы — {ДД.ММ.ГГГГ}
ПОБЕДЫ
• {победа 1}
• {победа 2}
• {победа 3}
НАБЛЮДЕНИЯ
• {наблюдение 1} — {рекомендуемое действие}
• {наблюдение 2} — {рекомендуемое действие}
Выручка за неделю: {сумма} ₽ ({+/−}X% против прошлой недели)
Connector failures
Work with what's connected — the team degrades gracefully. If there's no ~~платежи — skip transaction data and note "payments not connected — revenue only from CRM deals." If there's no ~~crm — skip deal closures and note it. If neither is available — stop: "No revenue source is connected. Connect payments or CRM to run the Friday brief."
Approval gates
- Never send or publish the brief automatically. Always show it to the owner for review.
- Do not cancel or change anything automatically. Only display data and recommendations.
Conclusion
Finish with a formatted brief and the question: “Send this to messenger, to your email, or save it?”