This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For a tiny business forecast, I would start with these checks: - Start from observed behavior - Write the riskiest assumption down - Choose a measurable next test If you share real material, remove anything private first and replace bracketed fields with concrete details.

Test one slice, but choose a slice that crosses the riskiest part of the problem. A tiny easy demo will only prove the easy part. Use this decision rule: - If reversing the choice is cheap, try it. - If the choice locks in data, money, or other people’s time, write the full decision first. - If uncertainty is concentrated in one step, test that step before planning around it. For a tiny business forecast, make the first test produce evidence you can compare, not just something that looks complete.

Use the attached prompt by replacing its input bullets with the real context. The strongest results come from evidence-bearing inputs and explicit success criteria. The required deliverables are: data quality report, metric table, anomalies and drivers, decision summary with reproducible method.

## Copy-ready prompt ```text Act as a treasury and FP&A leader. Answer this question: “How can finance teams build better cash-flow forecasts with AI?” Objective: design an AI-assisted cash-flow forecasting process that remains auditable. First, ask up to five concise questions needed to tailor the analysis. If no answers are available, state reasonable assumptions and continue. Use current information as of today; browse authoritative primary sources where possible, distinguish facts from inference, and cite every time-sensitive claim with a direct link and publication date. Cover: data sourc