A financial review often starts with a spreadsheet and ends with a story about why the numbers moved. The calculation is usually easier than the explanation. Different source versions, metric definitions, and comparison periods can distort the result before the analysis even begins.

Strawberry can work across the model, approved dashboards, operating records, and meeting context while keeping sources beside the claims. That lets the companion test an explanation instead of turning the first plausible narrative into a fact.

Choose the comparison that matters

Actual versus budget answers a different question from actual versus the latest forecast or last month. Start with the company, period, audience, and decision, then use the baseline and materiality that fit that decision.

Want to try it?

Ask your Strawberry companion: “Review our latest financial performance against the right baseline, validate the figures, explain the material drivers, and show what needs attention.”

Skill

Review financial performance

Validate the figures, explain the important movements, and show what needs attention.

Make the figures comparable

  1. Confirm the accepted version of actuals and the baseline.
  2. Align periods, currencies, units, dimensions, filters, and signs.
  3. Recalculate material totals and variances.
  4. Keep accounting measures separate from management metrics when their definitions differ.

Because Strawberry can inspect the spreadsheet and the surrounding source systems in the same workspace, it can show where two reports disagree instead of silently choosing the cleaner-looking number.

Separate movement from cause

What the evidence showsHow to present it
A calculated contributionShow the formula, source figures, and any residual.
A cause supported by operating evidenceLink the contract, headcount record, sales data, usage record, or accepted commentary.
A plausible explanation without supportLabel it as a hypothesis and name what would confirm it.
Conflicting or incomplete sourcesKeep the conflict visible and avoid a final claim.

This is where connected context improves the analysis. A hiring plan, customer movement, vendor commitment, or meeting decision may explain the result, but only if it refers to the same period and business scope.

Finish with the next decision

Lead with the few movements that change understanding or action. A compact scorecard, supported drivers, open questions, and source problems are usually more useful than a complete recital of every line. If the accepted findings change the forward view, carry them into the forecast. If they need to reach a wider audience, prepare a separate update for that audience.

Skill

Build or update a financial forecast

Carry accepted performance drivers into the forward view and test the scenarios that matter.

Skill

Prepare a Status Update

Turn accepted analysis into a concise update for the intended team or leadership audience.

Once the team trusts the definitions, source mappings, materiality, and comparison logic, save that review method as a team skill. A Routine can prepare the next draft on schedule and stop when a source version, definition, entity, or period changes.

The performance review remains read-only. Strawberry does not change the budget, forecast, ledger, or source report.

How to prepare for a fundraise with AICarry the accepted financial picture into the wider investor story and fundraising process. How to build a financial forecast with AICarry accepted performance drivers into a forecast and test the scenarios that matter. How to organize invoices and receipts with AIGather the documents and exceptions that support a cleaner financial picture.
Official Strawberry skill
Copy skill file Download skill file
name
review-financial-performance
description
Review financial performance against an accepted budget, forecast, prior period, or other baseline; validate the figures, explain material drivers, and identify supported implications. Use for cash, runway, income, cost, margin, budget-versus-actual, or forecast-variance questions without changing source records.

Review Financial Performance

Turn the latest figures into a clear view of what changed, why it may have changed, and what needs attention. Keep calculated movement separate from a business explanation that the evidence does not yet support.

1. Define the comparison

Establish the company or entity, period, currency, audience, decision, and useful baseline: budget, forecast, prior month, prior year, or another accepted view. Learn the user's definitions, materiality, and sign conventions instead of imposing generic thresholds.

Identify the accepted version of actuals and the baseline. If versions conflict, resolve the choice or show the conflict before comparing them.

2. Build a comparable view

Use approved statements, spreadsheets, planning models, dashboards, billing or payment records, and operating context that could explain the result. Keep source names, links, versions, filters, and as-of dates beside consequential figures.

Normalize periods, currencies, units, dimensions, and signs. Recalculate totals and material variances. Keep accounting measures and management metrics separate when their definitions differ.

3. Explain the important movements

Prioritize the movements that could change a decision. Break them into supported drivers such as price, volume, mix, timing, headcount, rate, currency, or one-time items when the available evidence makes that decomposition useful.

Use operating records, contracts, headcount plans, sales or usage evidence, and relevant meetings to test the cause. Label an unverified explanation as a hypothesis and name what would confirm it. Show meaningful offsets and unexplained residuals rather than hiding them in “other.”

4. Deliver a reviewable result

Return the smallest useful view, which may include:

  • scope, baseline, materiality, and coverage limits;
  • a compact scorecard or comparison table;
  • material favorable and unfavorable drivers with source links;
  • cash, runway, margin, or forecast implications when relevant;
  • decisions and follow-up questions; and
  • source-quality problems, conflicts, and unresolved items.

Use strawberry/finance/build-a-financial-forecast when accepted findings should change the forward view. Use strawberry/operations/prepare-a-status-update when the accepted analysis should become a general founder or team update.

5. Reuse the accepted review

Preserve accepted definitions, source mappings, materiality, dimensions, and comparison logic after the user confirms them. A recurring review may become a Routine that prepares a draft from named sources and stops when a source version, definition, company, period, or materiality rule is unclear.

This workflow is read-only analysis. Do not change a budget, forecast, ledger, source report, or external record, or share the result beyond the accepted audience.