Financial profile: budget ceilings, approval thresholds, cost centers

STAFF MILTON · V0.2.0

bopen-tools:cost-tracking

REQUIRES

claude plugin install bopen-tools@b-open-io

WHEN TO REACH FOR THIS

Cost reports and budget chains are only as good as the structure they run against. Without a financial profile, every playbook that touches money assumes a flat default: one budget, one approver, no cost centers. Fill this in once and Milton's cost reporting, the quarterly budget chain, and the cost-anomaly chain all respect your actual approval structure. This is a fill-in-the-blank configuration document: you provide the facts, and the agents read them before acting.

REQUIRES

claude plugin install bopen-tools@b-open-io (Milton's cost-tracking skill reads this profile)
No API keys needed to author the profile; the figures come from you

CONTEXT INPUTS

Fill in every field, and mark any field you don't know as UNKNOWN; a marked unknown is safer than a wrong default. Save the completed file as financial-profile.md in your repo or ops vault so every finance playbook can load it.

BUDGET CEILINGS

{{MONTHLY_AI_BUDGET}} # total monthly Anthropic/AI spend ceiling, USD {{MONTHLY_INFRA_BUDGET}} # total monthly Vercel + Railway + hosting ceiling, USD {{PER_AGENT_BUDGET}} # default monthly ceiling per autonomous agent, if you run them {{QUARTERLY_ENVELOPE}} # discretionary spend envelope per quarter for new work

APPROVAL THRESHOLDS

{{AUTO_APPROVE_UNDER}} # spend an operator/agent may commit without sign-off, USD {{MANAGER_APPROVAL_RANGE}} # range requiring a manager's approval {{EXEC_APPROVAL_OVER}} # spend requiring Chief/CFO sign-off {{APPROVER_ROLES}} # who holds each approval level (roles, not names if you prefer)

COST CENTERS

{{COST_CENTERS}} # list: name + what it covers (e.g. "Product ; AI features") {{DEFAULT_COST_CENTER}} # where unattributed spend lands {{TAGGING_SCHEME}} # how spend maps to a center (Vercel project, API key, workspace)

CADENCE & REPORTING

{{REPORTING_DAY}} # day of month the cost report runs {{ANOMALY_THRESHOLD}} # multiple of rolling average that triggers an alert (default 2x) {{FISCAL_YEAR_START}} # month the fiscal year begins

THE PROMPT

PASTE INTO YOUR AGENT

You are Milton (bopen-tools:cfo). Help the operator complete their financial profile,
then validate it. Load bopen-tools:cost-tracking so the profile lines up with how cost
data actually maps (Anthropic by workspace/api_key, Vercel by project, Railway manual).

1. Walk the operator through any field left as UNKNOWN and propose a sensible starting
   value with a one-line rationale; but mark it as a proposal, not a fact, until they
   confirm.
2. Check the tagging scheme against the platforms: confirm each cost center can actually
   be attributed from available data (a center with no Vercel project, API key, or
   workspace tag cannot be measured; flag it).
3. Verify approval thresholds are non-overlapping and cover the full range with no gap.
4. Output the finished profile as clean markdown ready to save as financial-profile.md.

Negative prompts: do not invent budget figures or approver names; leave UNKNOWN and ask.
Do not create a cost center that cannot be mapped to real spend data. Do not treat this
as a spend report; it is a configuration document consumed by other playbooks.

EXPECTED OUTPUT

A completed financial-profile.md with budget ceilings, non-overlapping approval thresholds, mappable cost centers, and reporting cadence — validated so that every cost center corresponds to something the cost-tracking skill can actually measure. Saved where finance playbooks can read it.

FOLLOW-UP CHAIN

bo-cost-report — Run a monthly Anthropic, Vercel, and Railway cost report
bo-cost-dashboard — Build a real-time cost dashboard across Anthropic, Vercel, and Railway
bo-company-profile — Company profile: mission, stage, metrics, org chart

← PACK CONTENTS