Skip to case study

Production Planner

Helping small production companies stay on budget without a finance department

Unifying conversations, contacts, and expenses into one workspace to give independent film producers total financial visibility without a dedicated accountant.

Production Planner message center with floating messages and a payment modal for Anna Smith, reviewing two approved expenses totaling $650.25
My role
Product Designer
Team
2 Product Owners • Designer
Timeline
6 months

Context

In independent filmmaking, creative vision is constantly constrained by extreme financial fragility. With roughly 60% of indie shoots exceeding their budgets, productions rarely fail on artistic merit—they fail from financial exhaustion caused by coordination slip-ups, unchecked gear costs, and schedule drag. Because existing studio tools demand a full-time finance team and consumer apps lack production context, line producers are forced to juggle informal agreements across scattered threads while budgets leak silently.

Role

Co-designed the user interface and flow with two industry product owners.

Scope

Communication workspace UI, message-to-expense interaction design, and vendor payment tracking.

The guiding question

How might we give producers instant visibility and financial clarity across projects, so they always know what’s paid, what’s pending, and how productions are progressing?

01 / Problem

Expense tools don't know production and production tools aren’t suited for small teams

Enterprise entertainment tools assume a full-time accounting department. Everyday expense trackers assume standard corporate overhead. For lean production companies, neither fits. Teams improvise across fragmented spreadsheets, camera-roll receipts, and unrecorded chat threads—leaving producers to manually stitch together who is owed what after the shoot has already wrapped.

Standard tools record receipts after the fact, but fail to answer the on-set question that matters most: “What do we still owe this person on this specific job?” None of them bring financial accountability into the conversations where money is actually committed.

The Wrong Coverage

  • Generic tools ignore production context

    Filing a receipt solves nothing if it isn't tied to a department, a shoot day, and a project ledger.

  • Studio platforms over-engineer basic tasks

    Built for studio hierarchies, enterprise software demands extensive setup and dedicated administrators that small teams don't have.

  • Communication channels stay severed from the ledger

    Crew plans in group chats, vendors quote over email, and caterers confirm via text. The producer becomes the sole, fragile bridge between informal promises and cash flow.

“It’s 9pm. The shoot wrapped an hour ago. The line producer still has to pay the caterer who’s texting for confirmation, send tomorrow’s call time to the camera crew, and log three receipts before she forgets which project they belong to. Five apps. Five context switches. One tired person. A dozen ways for something to slip.”

A day in the life, told honestly

02 / Research

The root cause: Systems track documents, but productions run on people

Through interviews with two film-industry product owners and an analysis of on-set workflows, I mapped how money actually moves across a shoot: where rates are negotiated, who approves overages, and how debts accumulate.

Five distinct spending workflows emerged across talent, camera, art, catering, and post-production. While their paperwork differed, every single one shared the same flaw: the commitment happens in a conversation, but the financial record gets made days later—by whoever remembers to log it.

Producers, crew and vendors, and reconcilers share three questions: who is owed, where the production stands, and what was agreed. The root cause is that money is organized around documents while decisions are organized around people.

03 / Requirements

Moving from retroactive guesswork to real-time financial control

Every production issue we uncovered came down to the same barrier: answers existed across PDFs, texts, and spreadsheets, but the data was organized around static files rather than active relationships. To solve this, the product had to stop treating messaging and money as separate systems.

Translating Into Requirements

  • At-a-Glance Multi-Project Health

    Surface live budget burn and project status instantly, removing the need for manual calculations or spreadsheet audits.

  • Unified Financial Audit Trail

    Consolidate every transaction, payee, and project ledger into a single searchable record.

  • Context-Preserving Inbox

    Centralize SMS, email, and group chats so financial commitments stay tied directly to the conversation that created them.

  • Proactive Drift Detection

    Clarify the gap between reported expenses and settled payouts across every department to flag budget overruns before wrap.

04 / Alternatives

Every cut costs something

Every design choice required balancing the chaotic reality of a fast-moving film set against the structured data needs of a reliable ledger. Rather than building ideal-world features, we prioritized decisions that reduce cognitive load and preserve financial truth.

Exploration & process alternatives

Automatically detecting commitments in conversations

Alternative
Rely on producers to manually log agreed rates and expenses after a conversation.
Design decision
Flag potential financial commitments in messages and prefill an expense with the amount, payee, and project for the producer to review and confirm.
Tradeoff
Reduces manual entry and missed commitments, but a quote or proposed rate is not always an agreement. Producer confirmation keeps unapproved amounts out of the ledger. This capability was scoped for v2.

Separate messaging tabs vs. one conversation stream

Alternative
Split the message centre into three tabs—Chat, SMS, and Email—each with its own message stream.
Design decision
Bring messages into a single chronological conversation, with visible Chat, SMS, and Email labels identifying each message’s source and an explicit channel selector for replies.
Tradeoff
A shared stream keeps context together and reduces tab switching, but needs clear source labels and reply controls so producers always know which channel they’re reading and sending through.

Visualizing the commitment gap instead of static budgets

Alternative
Traditional “planned vs. actual” budget tables familiar from accounting software.
Design decision
Surface the live delta between paid spend and reported commitments, requiring zero upfront setup.
Tradeoff
Introduces an unfamiliar mental model for traditional bookkeepers, but gives independent producers an immediate read on pending debt without manual math.

05 / Design

One system for team conversations and vendor payouts

To eliminate manual reconciliation, the data architecture could not treat messaging, crew contacts, and accounting as disconnected silos. We unified them into a single relational entity: the contact book doubled as the payment directory, every conversation anchored to a verified payee, and every expense required both a person and a project before saving.

By giving conversations and financial commitments the same “address,” checking budget health or settling an invoice no longer requires switching between apps.

Project D budget overview with department spending, Vendors selected beside Crew, a payment status filter, and Apex Camera’s outstanding balance, due date, and payment terms

Project Hub

Compares committed spending with the project budget and department allocations. The Vendors tab connects unpaid balances to the selected vendor’s due dates, payment terms, and contact details.

06 / Reflections

The Wrap: What shipped, what’s next, and what I learned

The complete product strategy relies on a four-stage loop: meet teams in their preferred channels, capture commitments in the moment, maintain a live ledger, and surface budget trouble early. For this release, I focused on shipping the core infrastructure: the multi-channel communication hub and the real-time financial ledger.

The next release would introduce inline message capture, allowing producers to convert an agreed quote or rate directly into an attributed expense before context is lost. Proactive warning alerts require an accurate, trusted ledger first, just as capturing commitments requires anchoring those conversations inside the workspace.

Next case study

Avenue Air Depot

Modernizing HVAC manufacturing workflows to resolve inefficient order processing and scale operations