Setting up budgets per team in 10 minutes

This takes about 10 minutes and you only need to do the first setup once. After that it's a number you adjust, not a process you run.

1. Start from last month's actuals, not a guess

Open the Teams view in the console. Every team already shows 30-day spend, because Verybear has been logging usage since the first desk connected. Set each team's monthly budget around 15–20% above their trailing spend: enough room for growth, tight enough that a real spike still shows up.

Engineering runs more and heavier tasks than Marketing. Support runs a huge volume of small ones. Don't use one number for every team. That's how you end up either throttling your busiest team or giving your quietest one a budget they'll never approach.

2. Set the alert threshold once, for everyone

The org-wide alert threshold (default 80%) applies across every team budget, so you only set this once. At 80%, the team and your AI team get a signal while there's still runway to look at why, not a surprise at 100% when the only option left is to cut something off.

3. Decide what "close to budget" actually does

A budget alert is information, not a kill switch: Verybear never silently blocks someone mid-task because a number crossed a line. What it does is put the spend in front of a human with context: which flows are driving it, whether it's one person running something unusually heavy, or just organic growth. You decide the next step, every time.

4. Review monthly, adjust quarterly

Budgets aren't a one-time setup. Revisit them monthly for anything that tripped an alert, and do a full pass quarterly as teams grow or flows change. A new high-effort flow for Engineering will shift their baseline more than three months of organic growth will.

That's it. Ten minutes to set numbers that give every team owner a live view of their own spend, and give Finance a dashboard that updates itself instead of a spreadsheet someone rebuilds every month.