Expensify is good software. That's not the question. The question is whether a team of three — you and a couple of contractors — actually needs an AP-grade travel-and-expense platform, or whether you're about to pay enterprise pricing for a problem you could solve for a few dollars a month. The answer turns almost entirely on one line of the pricing page.
The per-seat math nobody runs first
Expensify bills per active user — roughly $5 a seat and up on the Collect plan, and crucially, "active" means anyone who touched the system that month. That model is designed for finance teams where every seat is a salaried employee submitting expenses constantly. Run it through a small, lumpy team and it does something strange:
- You, the owner — one seat, every month.
- A contractor who submits one receipt in March — a full active seat for March.
- A seasonal helper who logs three lunches in December — a full seat for December.
The pricing was built for a world where users are dense and constant. Owner-operator teams are sparse and spiky — lots of people who submit occasionally — and per-seat pricing taxes exactly that shape the hardest. You end up paying for collaboration you actually want more of.
When Expensify genuinely is the right call
To be fair to it, there are teams who should just buy Expensify and not think twice:
- You have an actual approvals process with policy rules, spending limits, and multiple approvers.
- Your spend runs through corporate cards and you want the card feed and receipts reconciled in one engine.
- You're past, say, ten constant users, where the per-seat model stops feeling punitive and the policy automation starts paying for itself.
If that's you, the tool earns its price. None of this is a knock on Expensify; it's a knock on using it three sizes too big.
What a team of three usually actually needs
Strip the requirement down and most small teams need four things, none of which require a policy engine:
- Everyone can capture a receipt from their own phone.
- The owner can see and approve what came in, without handing over the books.
- It totals and categorises automatically.
- It exports something the accountant can use.
That's a capture-and-approve workflow, not an AP platform. It should cost roughly nothing and charge nothing per head — because the whole point of a tiny team is that the people are the asset, not a line item.
That's the gap we built Starlog into: contractors and teammates submit on free seats, the owner approves before anything lands on the books, and we never charge per user — the paywall is running multiple businesses, not having teammates. (Here's how the small-team workflow actually runs.) Receipts back up to your own Google Drive, and the year-end export is a spreadsheet plus every image.
The honest caveat
If what you need really is a policy engine, corporate cards, and automated approvals across a growing headcount, don't make a capture app pretend to be that — buy the platform. But if you're three people and a glovebox of receipts, you don't need Expensify. You need the receipts to stop getting lost, and you need to not get billed per person for it.
The takeaway
Expensify charges per active user because it was built for AP teams, where that's the natural shape. A team of three is the opposite shape — sparse, occasional, people-light on purpose. Match the tool to that: capture, approve, export, flat pricing. Compare the two honestly here, and only pay per seat when you have seats that are full every month.