TL;DR: A 24-person digital marketing agency in New York had a 14-page expense policy with 12 core rules and 47 documented exceptions. The finance director enforced it from memory. She caught about 60% of violations. The rest got reimbursed and discovered months later, or never. Annual cost of non-compliance: roughly $27,000-$32,000. They'd tried Expensify (couldn't handle exceptions), a simplified policy (HR pushed back), and training sessions (minimal retention). We built a four-stage agent that encodes the full policy as a decision tree, lets employees check compliance before submitting, reviews every line automatically, and dashboards violation patterns. Violation rate: 12-15% down to 2.1%. Rachel's review time: 2-3 hours per week down to 25 minutes. Agent cost: $190/month.
The Hotel and the Team Dinner
Rachel opened the expense report. Hotel charge: $412 per night. New York in October. Plausible. But was this a client meeting (allowance: $400 per night) or an internal trip (limit: $250 per night)?
Description: "NYC: client meeting + team dinner." Client rate applies. But the team dinner. Was that under the meal policy ($75 per person) or the client entertainment policy ($150 per person)? The client wasn't at dinner. But it was after a client meeting. Same trip. Different meal. The policy didn't explicitly address this.
Rachel made a judgment call. Approved it. Moved on. Seventy-nine more lines to go this week.
This is, when you think about it, a system whose enforcement mechanism is a single human's ability to recall the contents of a 14-page document with 47 contextual exceptions while simultaneously reviewing 80 line items per week. Which is to say, it's not an enforcement mechanism at all. It's a memory test administered weekly to a finance director who is also doing forecasting, payroll, vendor management, and quarterly reporting.
Rachel estimates she catches about 60% of violations. She thinks. The other 40% get reimbursed and show up in quarterly reviews (months after the money left the account) or don't show up at all. Last quarter's review found $4,200 in violations already paid out.
The irony wasn't subtle. A marketing agency (a business that builds systems and processes for clients, for money, professionally) had no system for its own expenses. Just a PDF nobody reads and a finance director working from recall.
The Agency
Digital marketing agency in New York. Twenty-four employees. SEO, paid media, content strategy, analytics. Annual revenue: roughly $3.2M. Monthly expense volume: $28,000 to $35,000.
The expense policy: 14 pages. Twelve core rules. Forty-seven documented exceptions.
I want to be specific about the exceptions, because the number sounds abstract until you see what it means in practice. Hotel limit: $250 per night. Unless it's a client meeting in a Tier 1 city ($400). Unless it's a conference with pre-approval (actual rate). Unless it's international (separate tier schedule). One rule. Four branches. Two of them subjective. Multiply that pattern across meals, travel, software, entertainment, and client gifts, and you arrive at 47 exceptions to 12 rules, which is roughly four exceptions per rule, which is roughly the point at which a "rule" stops being a rule and starts being a suggestion with extensive footnotes.
Rachel reviews every expense report manually. Fifteen to twenty minutes per report. Eight to twelve reports per week. Two to three hours of her week spent cross-referencing reality against a document she can recall about 70% of accurately.
Annual violations caught: roughly $16,800. Estimated uncaught: $11,000 to $15,000. Total annual cost of non-compliance: somewhere between $27,000 and $32,000.
Each violation is small enough to feel like rounding error. A $50 overage here. A $120 meal there. Individually manageable. Collectively, a mid-level employee's salary. Paid out in increments too small to notice and too numerous to track.
Why Nothing They Tried Worked
The PDF was well-written. Nobody reads it. Rachel tested this informally: she asked the team to name the meal limit for a non-client business dinner. Three of 24 employees got it right. This is not because the other 21 are irresponsible. It's because nobody memorises a 14-page document they reference twice a year, which is a fact so obvious it barely warrants stating, and yet the entire enforcement system was built on the assumption that they would.
They implemented Expensify. Good tool. Couldn't handle exceptions. Setting a $250 hotel limit flagged every client-meeting hotel, every conference stay, every international trip. Within two months, Rachel was overriding 40% of alerts. Alert fatigue won. She stopped checking the flags. They turned it off. Eighteen months of subscription fees for a system that made the problem noisier without making it smaller.
HR proposed simplifying the policy. Account directors pushed back. A $75 meal limit for a Manhattan client dinner is unreasonable. Simplification would either punish employees or remove guardrails entirely. Both outcomes are worse than the current mess, which is a rather depressing observation about the current mess.
Quarterly training sessions produced quarterly nodding and weekly forgetting. Managers asked to pre-approve expenses approved everything (they didn't know the exceptions either, which, again, would require memorising 14 pages, which again, nobody does).
Every approach failed for the same reason: the policy was right but complex. The tools couldn't handle the complexity. The humans couldn't remember it. Simplifying would break it. The agency was stuck between a policy too complex to enforce and too correct to simplify.
The design is next. The design, the build guide, the running costs and the take-away are free to subscribers. Enter your email below and the rest of this Blueprint opens. New ones arrive every Tuesday and Friday.
