How to use the Cloud cost review template

Start a board from it
Use this template opens a new Freero board with the Cloud cost review template on it (sign up free first). On a board you already have, open Templates in the toolbar and search for “Cloud cost review”.
Follow the instruction on the board
“Sort spend by team and service, biggest first. Look for things running that nobody uses before you tune what people do use.”
Fill in each part
- Where the money goes The biggest lines of last month’s bill.
- Waste Things we pay for and don’t use.
- Right-sizing Things bigger than they need to be.
- Commitments Steady usage we could commit to for a discount.
- Don’t touch Spend we keep on purpose.
- Agreed actions Saving, owner and date.
Bring your team and your agents
Invite people to the board or share a link, and work on it together live. The timer is in the top bar, private mode and voting in the board menu, and Claude or ChatGPT can join through Freero’s MCP server.

Work on it with an AI agent

Connect an assistant once and it works on the board with you, with your permissions: by default it reads and proposes, and people decide.

You ask: “Fill in the Cloud cost review board from these notes.”
What happens It reads the board, then proposes sticky notes for it. Nothing changes until someone on the board accepts them.
You ask: “Group what we wrote into themes and list the actions.”
What happens It proposes clusters with a title each and task cards for the actions, labelled with its name and yours.

Migration plan
Move data or traffic from an old system to a new one in safe, reversible steps, with a check before each step.
On-call handover
Hand the pager over cleanly: what happened this week, what’s still open, what to watch and what the next person needs to know.
Threat modelling session
Walk through what an attacker could do to a feature: what’s worth protecting, how it could be reached, the impact and the fix.
Service ownership map
Who owns each service, where its docs and dashboards live, how critical it is and who to call when it breaks.
Performance investigation
Work through a slowdown methodically: the symptom, measurements, a hypothesis, one change at a time and proof it helped.
Observability plan
Decide what to measure for a service: the question each signal answers, where it lives and when it should wake someone up.