The case for project-based cards

A line producer opens a new corporate card for a feature. The card belongs to the production company, but the company is running three other jobs at the same time: a commercial, a music video, and development on the next picture. Every swipe on that one card lands in the same pile. By week two, nobody can tell whether the $4,000 at a camera rental house was for the feature or the commercial. The card did its job. It just had no idea which project it was working for.

This is the quiet problem with corporate cards for film, agencies, tours, and creator studios. The card was designed for a company that exists indefinitely, with stable departments and a fiscal year. A production is the opposite. It spins up, burns hot for a few weeks, and wraps. A campaign has a start date and a kill date. A tour ends in a parking lot in Cleveland. The work is project-shaped, and the card underneath it is company-shaped.

Company cards assume the company is the unit

Generic spend tools like the Ramp and Brex card programs are genuinely good at what they were built for: one company, departments that persist, budgets that reset annually, a finance team that owns the close. Their whole model assumes the company is the thing you're managing money for. But creative work doesn't fit that shape. The real unit of spending is the project, not the company. A single production house might carry six jobs in a quarter, each with its own budget, client, end date, and often its own loan-out and entity structure. When the card is bound to the company instead of the job, every control you actually care about, what this card can spend, until when, on what, charged to which line, lives in someone's head or a spreadsheet instead of in the card.

What a project-based card controls

A card built for a project starts from the project, not the org chart. The controls map to how a production actually runs, not to how a permanent company is organized. None of it is exotic, either: it's the same logic a UPM already applies with petty cash envelopes and a paper PO book, just enforced by the card instead of by trust and a clipboard.

• A spend limit tied to a specific line in the project budget, not a blanket monthly cap, so the gaffer's card can't quietly eat into the art department's allocation.
• An expiration date set to wrap, so the card simply stops working once the job is over, instead of living on as a forgotten liability after the unit disbands.
• Merchant and category rules that fit the department, camera rental and grip houses for the G&E card, restaurants and per-diem vendors for the production card.
• A budget code baked into every transaction, so a swipe is already coded to the project and the line before anyone touches the books.
• A named person who approves the card and its increases, so there's always an accountable human on the spend, not a policy that approved itself.

The case for one card per project

Once the card knows which project it belongs to, the messy parts of production accounting get quieter. Reconciliation isn't a forensic exercise at wrap, because every charge was already coded to a project and a line at swipe time. Cost reports to a client or a studio can be cut by project without untangling commingled charges. When a campaign or a shoot ends, you close its cards and the spending stops cold. It also changes who carries the risk: a crew card with a $2,000 limit, scoped to lodging and meals, that dies at wrap is a very different object than a company card handed to a freelancer for six weeks. You're not betting on the person; you're scoping the card. And because a named approver signs off on the limit and any bump, there's a clear chain of accountability for production cards and corporate cards for film, instead of a default policy nobody remembers setting.

Project-based, not company-based

This is the bet behind Alador: business banking and corporate cards should be organized around projects, because the creative and cultural economy already runs on projects. Every production, campaign, tour, event, and client engagement is a temporary company, and its cards should behave that way, scoped, dated, coded, and approved by a real person, then closed when the work is done. To be straight about where we are: Alador is in private beta and coming in 2026, and what's described here is what we're building, not a live feature set. Alador is not a bank; banking and card services will be provided by an FDIC-insured partner bank once available. The argument, though, we'll make today, corporate cards were built for companies, and the creative economy is built on projects.