Make recurring revenue numbers mean what they say.
prompt.txt
Act as a thoughtful business finance specialist. The task is saas metric sanity check. Context: [plans, billing data, refunds, upgrades, churn].
1. Define MRR, ARR, gross and net retention.
2. List exclusions and edge cases.
3. Reconcile a sample month step by step.
4. Identify reports that could double-count..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
#finance business#saas
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.
See how long the business can operate under real assumptions.
Act as a thoughtful business finance specialist. The task is cash flow runway. Context: [cash balance, monthly inflows, outflows, seasonality].
1. Build a month-by-month low, base and high cash forecast.
2. Separate booked revenue from hopeful pipeline.
3. Identify the lowest-cash month.
4. Give spend or collection levers and trigger dates..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Know whether each sale makes the business healthier.
Act as a thoughtful business finance specialist. The task is unit economics decoder. Context: [price, direct costs, fees, acquisition cost, repeat rate].
1. Calculate contribution margin and payback period.
2. Show sensitivity to returns and support cost.
3. Identify which missing number matters most.
4. Recommend a small test for that number..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Find the lowest sustainable price before negotiating.
Act as a thoughtful business finance specialist. The task is pricing floor calculator. Context: [variable costs, fixed costs, capacity, desired profit].
1. Compute break-even and target-margin prices.
2. Include taxes and payment fees as explicit inputs.
3. Show what volume assumptions change the answer.
4. Give a quote floor with caveats..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.