# Your AI Weekly Business Review

Visualize → Automate → Optimize

Give your assistant a repeatable job: compare this week with last week, check spending, find what is stuck and prepare one improvement. Includes the same dashboard starter so you can try it immediately.

START: Download https://switchboards.ai/downloads/assets/business-starter.zip and open START-HERE.txt.

## 1. See what a useful review looks like

DO: Open dashboard.html from the starter folder. Look at monthly software: €115. Clip tool B is marked unused and costs €39/month. Clip tool A does the same job and is used.

SEE: A concrete decision: review whether to keep Clip tool B. Cancelling it would reduce listed commitments to €76/month, or €468/year less. This is a potential reduction, not money already saved.

WHY: The review joins your goal with your spending. It does not give you generic advice to ‘be more productive’.

## 2. Keep a before and after

DO: On your first run, export your dashboard JSON as last-week.json. Keep business.json as this week’s source. Put both in your Cowork folder. For the exercise, use the supplied last-week.json and this-week.json.

SEE: The sample moves from €720 to €900 spent on Oak. The extra €180 has ID e4. Software commitments stay at €115. No cancellation has happened.

WHY: Two dated snapshots let the assistant explain what changed instead of guessing from one screenshot.

## 3. Run the review in Claude Cowork

DO: Open Claude Desktop, choose the starter folder in Cowork and paste 02-weekly-review.md. This prompt asks Claude to compare both snapshots and save its output. It also asks for one useful draft action it can complete locally.

SEE: weekly-review.md shows the €180 increase, Oak €100 over its spending limit, the possible €39/month reduction and one proposed priority. needs-you.md holds only decisions or access that need you.

WHY: A useful assistant should prepare work, not hand you a longer to-do list.

## 4. Repeat it, then add delivery

DO: First run the review yourself once. If you want it weekly, ask Cowork to schedule the same task for Friday at 09:00 in your time zone and confirm the task exists in its schedule list. Ensure the task can access your source files at run time. The starter does not install a schedule for you.

SEE: A saved recurring task with the right inputs and output location. Run it manually once from the schedule list. Telegram is an optional next connection, not included in this download.

WHY: A schedule starts the work. File access supplies the facts. Telegram only delivers the result; it is not the brain.

## 5. Make an improvement and measure it

DO: Decide which clipping tool you want. If you actually cancel one, update the records with the effective date and keep a note of confirmation. Ask Claude to record the decision and compare next week’s costs. For the practice version, use the clearly labelled sample decision prompt.

SEE: A dated decision, its reason and a measurable follow-up. The review distinguishes a recommendation from a completed action.

WHY: Next week the assistant checks whether the decision helped. That is the feedback loop.

## Build prompt

Work in this selected folder. Read BRAIN.md and business.json. Inspect dashboard.html. First explain the three most useful findings in this sample. Then create weekly-review.md and needs-you.md. Use expense IDs to avoid counting records twice. Project fees are not profit; compare recorded project costs against spendLimit. Calculate software commitments separately. Suggest one improvement tied to the goal. Complete one allowed local draft action: write an Oak delivery-plan.md that offers two ways to keep work within scope. Put only decisions requiring my judgment into needs-you.md. Do not contact clients or cancel anything. After that, ask me for my business details so you can adapt the dashboard. Keep the dashboard functional, mobile-friendly and able to import/export JSON. Do not embed credentials or external requests.

## Weekly review prompt

Read BRAIN.md, last-week.json and this-week.json in this folder. Compare records by ID. Save weekly-review.md with: what changed; recorded project spending versus its limit; recurring tools with overlapping purposes or reported non-use; one improvement tied to the business goal; the exact evidence and calculation. Distinguish potential reductions from realised savings. Write needs-you.md for approval decisions only. Create one useful local draft: an Oak recovery-plan.md, with two choices for getting the project back within scope, their tradeoffs, and the question the owner must answer. Use only supplied amounts; list missing figures. Finish by telling me the files you actually saved. On later runs, read prior decisions and check whether the chosen change improved the numbers.