ROASfinity for agencies with many clients

One record per client

• Each client has its own store data, ad accounts, naming pattern and report template.
• A person sees only the clients they are assigned to. Someone who only reviews work reads, and does not change budgets.

Approvals in one place

• Every budget or status change is proposed with its reason, reviewed by a second person, and logged after it is applied.
• The approvals calendar shows what is waiting, what was approved this week, and what was read back and found different from the request.

Reports that match the record

• The monthly report for each client is built from the same numbers the team reviews during the month, so the client never sees a different figure.
• Gaps are written as 'not measured', and the report says which source was missing.

Standards that keep clients comparable

• One naming pattern and one UTM standard across all clients, with client-specific values only where a client needs them.
• One definition of MER and of a new customer, written down once and linked from every report.

What to set up first

• Roles for each person and each client, before any account is connected.
• The naming pattern and the UTM standard, agreed for the agency and not per person.
• The approval rule: who can approve a budget change, and whether the account owner must also see it.