| name | powerbi-revenue-digital-twin |
| description | Use when designing or running a Power BI revenue digital twin for sales forecasting, target-gap simulation, backlog-to-invoice scenarios, what-if revenue paths, budget attainment, and forecast-to-cash decision support from an open Power BI Desktop model or exported forecast CSVs. |
Power BI Revenue Digital Twin
Use this skill when the user wants to move beyond a static sales forecast into scenario simulation: "How do we still hit budget?", "What if delivery slips?", "Which backlog must convert?", or "Which customers/products close the revenue gap?"
Workflow
- Start read-only. Use the open Desktop model through
Invoke-PowerBIAIForecast.ps1 or existing forecast CSVs. Do not write to PBIX/PBIP unless explicitly requested.
- Establish the current target gap by month: AI forecast, roll forecast, budget, actual-to-date, open backlog, expected backlog revenue.
- Build scenario levers:
- backlog acceleration or delay
- conversion probability changes
- customer/product demand uplift or erosion
- working-day and holiday impact
- budget or roll target constraint
- supply or delivery risk
- Produce at least three scenarios:
- base case from the current AI forecast
- target case showing what must change to hit budget or roll
- risk case showing likely downside if weak backlog or volatile segments slip
- Rank the smallest set of customer/product/month changes that explain or close the gap.
Required outputs
forecast_monthtarget_metric such as Budget or Rollcurrent_ai_forecasttarget_gaprequired_backlog_conversionrequired_residual_demandtop_gap_driversscenario_namescenario_forecastscenario_probabilityexplanation
Quality gates
- Mark a scenario
not_actionable when it depends on segments already flagged advisory_only, biased, or sparse without human validation.
- Separate controllable levers from non-controllable statistical demand.
- Never present a single scenario as truth; show assumptions and sensitivity.
