Events & media Spain

A month close that takes three days instead of three weeks.

Every production lived in its own spreadsheet, so nobody knew the real position until the shoot wrapped. Costs now land categorised, and a hot budget line surfaces the same week.

22 hBack per week
3 daysMonth close, was 3 weeks
9%Budget overruns avoided
01 Walkthrough

Nine minutes with the person who built it.

Hugo takes the project apart on screen: the bottleneck we found, the system we shipped, the number it moved.

The walkthrough is being recordedHugo is filming a short breakdown of this project. It appears here once it is edited.

No walkthrough yet. The written case below carries the same numbers.

02 The situation

Eleven productions, eleven spreadsheets, one very tired producer.

Vela Studios makes commercials and branded content out of Madrid, with a second office in Barcelona. Twelve people on staff, up to sixty freelancers in a busy month, eight to twelve productions running at once.

Each production got a spreadsheet, copied from the last one and edited by whoever had it open. Card receipts arrived as photographs in a WhatsApp group. Some never arrived at all.

The real numbers were built at the end, from bank statements. By then the overspend had already happened. On two productions in 2025 it reached eleven percent of budget.

Month close took three weeks of one person, which meant Vela was always closing the month before last.

03 What we found in the audit

The part nobody had time to fix.

Two days of interviews and one week of their own data. Here is what was actually going wrong, told the way the people living with it told us.

Every production started as a copy of the last one. The sheet then drifted, edited by whoever had it open that afternoon, until two shoots described the same cost in two different words.

That left the producer flying blind through the part of the job where the money actually moves. Real figures arrived weeks after the wrap, from a bank statement, long after the decision they should have shaped.

Freelancers felt it at the other end. Their invoices waited behind an approval nobody owned, and two of the best ones quietly stopped picking up.

04 What we built

From a photograph of a receipt to a number the producer trusts.

Built inside the tools the company already paid for. Every workflow, credential and prompt was handed over at the end.

System 01

Spend capture

Company cards fire an event the moment they are used. The freelancer photographs the receipt in the app. A model reads it, then files it against the right production.

Card paymentPhoto of the receiptRead and categoriseMatch to productionFiled in Drive
PleoOpenAIn8nGoogle Drive
System 02

Live budget by production

Every approved budget becomes a live sheet that reloads each night. A line crossing 80 percent sends the producer a message naming the line, the shoot day and the amount.

Approved budgetActuals every nightCompare by lineAlert over 80 percentProducer decides
Google SheetsHoldedn8nNotion
System 03

Close and pay

Freelance invoices are matched to the purchase order, queued for one approval and posted to Holded. The close pack builds itself on the second working day.

Invoice arrivesMatched to the POOne approvalPosted to HoldedClose pack ready
Holdedn8nNotionGoogle Sheets
05 What changed

Before and after, measured the same way.

Before figures come from the company's own records, pulled during the audit. The after column is the ninety day average once every system was live.

Metrics before and after the project
MetricBeforeAfter
Month close3 weeks3 days
Chasing receipts, weekly14 h20 min
Budget position5 weeks lateSame day
Productions over budget4 of 111 of 13
Freelance invoice to payment34 days12 days
Producer admin hours, weekly26 h4 h
22 hBack per week
3 daysMonth close, was 3 weeks
9%Budget overruns avoided
06 In their words

What they say now it is running.

I used to find out we had overspent when the money was already gone. Now I get a message on the Tuesday and there is still time to move something.

Marta VillarHead of Production, Vela Studios
07 What we would do differently

The parts we got wrong.

Every project has them. Writing them down is how the next one gets shorter.

We built the reporting before the category list was agreed, so the first month of data had to be recoded by hand.

Two hours in a room with the bookkeeper would have prevented all of it.

We also assumed freelancers would adopt the card app on their own. They did not, until a producer sat down with each of them for ten minutes.

08 Timeline

Week by week, start to handover.

First system in production inside a month. Everything after that is iteration with the client in the room.

  1. Week 0Audit. Three productions reconstructed from scratch to find where the money actually went.
  2. Week 1Category list agreed with the bookkeeper. Company cards issued to eight freelancers.
  3. Week 2Spend capture live on two productions only.
  4. Week 4All active productions on capture. Receipt chasing effectively stops.
  5. Week 6Live budgets running, with alerts to the producer at 80 percent of any line.
  6. Week 8Close pack automated. First three day close in month two.
  7. Week 10Handover. Vela owns the sheets, the workflows and the Holded connection.
10 Next case

Two more, in other industries.

Logistics & transport United States

Northfield Freight

First response, was 4 h: 11 min

Read the case

All five case studies

Your turn

Which four hours is your company losing every day?

The AI and Operations Audit finds it, prices it, then hands you a plan in two working days. Your fee comes off the first thing you build with us.