In a young company, spending control usually has a name, and it belongs to the founder. Every purchase, large or small, runs past one person for a yes. It is the most natural arrangement in the world, and it works right for a while.
But now picture a company that has just crossed twenty people. The founder’s phone buzzes through the day: can I buy this tool, can I expense that flight, can the client dinner go on the card, and so on. Each answer takes a few seconds, and the founder gives it while doing three other things. Multiply that across a growing team and one of two things happens. Either the founder becomes a bottleneck, holding up purchases people genuinely need, or the yes becomes a reflex that isn’t really controlling anything. Both are the same system failing, only in different directions.
Why “Just Ask Me First” Breaks
The informal system works at the start for a good reason: the founder has all the context. They know everything. They know the budget, they know the project, they know whether the money is there or not. In short, approval is quick because the person approving already holds the whole picture in their head.
That is exactly what growth takes away. As the team, the projects, and the spending multiply, no single person can hold all the context anymore. The founder approving a purchase for a team they barely touch is not really approving it. They are trusting that someone else did the thinking. At the same time, the requests that do need a careful look get the same three-second yes as everything else, because there is no time to treat them differently. The control was never written down anywhere, so it cannot scale, and it quietly stops being control at all.
The Real Cost of the Bottleneck
It is worth being honest about what this costs, because it rarely shows up as a single obvious number. On the slow side, work waits. A marketer sits on a campaign because the ad budget needs a top-up and the founder is in meetings until five. A developer can’t start because a tool hasn’t been approved. All of them are the business paying, in lost time, for a control step that adds nothing but a pause.
On the other side sits the quieter cost. When approving becomes a reflex, spending drifts. A subscription renews at a higher price and nobody catches it, because the renewal never came up for a real decision. Or two teams buy the same tool. A contractor’s invoice gets paid a month longer than it should have. By the time any of this surfaces, usually at quarter-end, the money is gone and the person who could have stopped it was too busy waving things through to notice. The founder ends up with the worst of both worlds: the burden of approving everything, and none of the control it was supposed to buy.
What Changes When Approvals Live in the System
The fix is not more discipline from the founder. It is moving the approval out of one person’s messages and into the system where the money actually moves.
In practice that means a request goes to the right approver automatically, and only above a threshold the business sets. Small, routine purchases run freely under their limit, because slowing them down helps no one. Anything larger, a €4,000 software renewal, a new supplier, a big travel booking, routes to the person responsible for that budget before the money leaves, not after. An invoice from a contractor lands with the department head who owns that spend, instead of sitting in a shared inbox waiting for someone to notice.
The founder stops being the single point every purchase passes through, and starts setting the rules that decide which purchases need a second look. Small things move faster than they did before. Big things get a real decision from someone who has the context to make it. And because it all happens in one place, every approval leaves a record, so months later it is clear who signed off on what, and why. The point is not to add bureaucracy. It is to spend the business’s attention where it matters and nowhere else.
More Than Approvals: One Place to Run the Money
Approvals are one visible example of a larger idea: that the controls a business needs should live in the same place its money does, rather than in habits and side conversations. That is how Wallester Business is built.
From day one, a business can:
- Open a business account with its own IBAN, with no subscription needed to get started
- Create teams and departments, and set a budget for each that its spending can’t quietly exceed
- Assign roles so the right people can spend, approve, or only view
- Route spending above a threshold you set through an approval before the money moves
- Set spending limits and controls on every card, tied to a person, team, or project
- Attach receipts to transactions and sync everything with Xero or QuickBooks
- See every card, budget, and approval from one dashboard, on web or mobile
The founder who approves everything is really a stand-in for a bigger problem, which is a business running its money through memory and goodwill instead of a system. Approvals are one place that shows up. So are cards nobody tracks, budgets nobody can see, and expenses reconstructed from scratch at month-end. Each is the same gap in a different costume, and each gets harder to close the longer a business waits.
Wallester Business exists to put all of it in one place: the account, the cards, the expenses, the budgets, and the currencies, managed together rather than stitched across five tools and one very busy founder. The goal isn’t to take the founder out of the decisions that matter. It’s to stop every small purchase from being one of them, so the attention that built the business can go back to growing it.
