pulse

name	pulse
description	Financial weekly pulse. Revenue vs forecast, expenses vs budget, cash position, outstanding invoices, variances. Friday morning routine. Octopus colors: Yellow (data pull) + Purple (synthesis).

/pulse: Financial Weekly Pulse

Octopus Colors: Yellow (Researcher) + Purple (Manager)

Process

1. Read departments/finance/knowledge/ for financial data, budgets, forecasts
2. Pull current data (Yellow):
   • Revenue: actual vs. forecast for the period
   • Expenses: actual vs. budget by category
   • Cash position: current balance, upcoming obligations
   • Outstanding: invoices sent but unpaid, aging
   • Key ratios: margins by product/service line
3. Synthesize (Purple):
   • Are we on track? Above or below plan?
   • Any variance > 10% from forecast? Flag with explanation.
   • Cash flow concerns in the next 30 days?
   • One-line summary: healthy/caution/concern
4. Present to Chairman

Output Format

# Financial Pulse: [Date]
**Overall:** [Healthy / Caution / Concern]

## Revenue
- This period: [amount] ([+/-]% vs forecast)
- Month-to-date: [amount] ([+/-]% vs plan)

## Expenses
- This period: [amount] ([+/-]% vs budget)
- Flagged: [any category > 10% over budget]

## Cash Position
- Current: [amount]
- Next 30 days: [net inflow/outflow expected]
- Concern: [any cash flow risk, or "None"]

## Outstanding
- Invoices unpaid: [count] totaling [amount]
- Aging > 30 days: [count] totaling [amount]

## Variance Alerts
- [Item]: [amount] [over/under], reason: [explanation]

## Chairman Action
[ ] No action needed
[ ] Follow up on: ___
[ ] Adjust forecast

Rules

• Only report data that exists in the knowledge base. Do not invent numbers.
• If no finance department exists, work with whatever financial data is available.
• Flag concerns proactively. Better to flag a non-issue than miss a real one.
• Save to .chairman/reports/pulse-YYYY-MM-DD.md