Key takeaways
- Headcount is a weak proxy; transaction volume and number of spenders are better.
- Cost centres and role templates become mandatory around the first specialised teams.
- Delegated administration prevents finance becoming a ticket queue.
What actually changes
Between 20 and 200 people the founder stops seeing every receipt. Policy has to move from verbal norms to encoded rules. Approval chains appear. Reporting has to answer “which team, which vendor, which month” without a spreadsheet rebuild.
Operating pattern that works
- Role templates for cards instead of bespoke limits.
- Team budgets with a finance-set ceiling.
- Exception queues instead of line-by-line approval.
- A close calendar with named owners.
Frequently asked questions
Keep reading
Sources and further reading
Every factual statement on this page is checked against primary documentation. Terms change frequently, so confirm details with the provider before acting on them.
- Brex — official websitePrimary source for current product names, availability and terms.
- Brex Support CenterOfficial help documentation, including account access and card administration topics.
- Visa — commercial payment solutionsNetwork-level background on commercial card products and data levels.
- Consumer Financial Protection Bureau — credit card resourcesBackground on card terminology, billing cycles and consumer-vs-commercial distinctions.
- FDIC — deposit insurance and pass-through coverageReference for how deposit insurance applies, including through third-party arrangements.
Independent resource notice
Brex Online is an independent publisher. We do not provide account access, financial services, card applications, payments or official customer support, and we are not affiliated with, endorsed by or operated by Brex.
Brex and related marks are trademarks of their respective owners and are used here only to identify the subject of this reference project.