PortuguêsBook a conversation →
Trabuka width=Event budget platform
for marketing and production
Budget Table

More than a budget spreadsheet. It's the heart of the event.

One line per service, and from that line everything else is born: briefing, request for quotation, comparison, approval, Purchase Order, Work Order, schedule, commercial proposal and closing report.

The problem

The spreadsheet dies the day the event ends.

Every event starts in a spreadsheet: what it is, who delivers, when, for how much. The spreadsheet dies the day the event ends, and the history dies with it: who quoted, who approved, why that supplier, what it really cost. The next edition starts from scratch.

The Budget Table is that spreadsheet, except it doesn't die and nothing is typed twice.

Three ideas behind it

01

The line is alive

It is born almost empty, with just the service name, and gains supplier, quote, value, approval, PO, delivery. An empty field is not an incomplete form; it means "not yet". That life can last six or twelve months, and nothing is lost.

02

Everyone sees their own column

The same table, read by different people: approvers see the total, buyers see the cost, the supplier sees no value at all. Who sees what is decided on the server, by role, never by a button.

03

The trail is the product

Every change of value, status and approval is stamped with who and when. Approving, issuing and sending are acts of a person, with a click. Nothing happens on its own.

What the line does

Everything is born from the line and returns to it. No screen asks you to type again what you already said.

The line
  • One line per service: name, category, descriptive quantity and unit
  • Description is the item's brief, read by supplier and client
  • Supplier (company or individual), contact and internal owner
  • Status (pending, quoting, approved, PO issued, delivered, dismissed) and internal deadline
Money
  • Planned, approved and actual cost, always the line total
  • Sale and net margin (sale − cost − tax), only for those with the sales axis
  • Event budget: approvals draw from it, the panel shows what remains
  • CL flag: the client pays the supplier directly, the house invoices the difference
Quote and approve
  • Selected lines become a request with no values; the supplier replies by magic link
  • The comparison puts the answers side by side
  • Whoever has authority approves; the stamp is never erased
  • Event actions give the line a venue and dates; the schedule comes from there
Documents that come out
  • Purchase Order and Work Order, one supplier per document, acceptance by link
  • Commercial proposal by category, frozen versions, client acceptance by link
  • Attachments by axis: a supplier's invoice never reaches the client
  • CSV and numbered PDFs for everything that goes out
Trail
  • Line history: who changed what, when
  • Dismiss instead of delete: a line with an act stays forever, out of the sum
  • Line tasks and checklist, with owner and deadline
  • Nothing happens on its own: approving, issuing and sending are a person's clicks

Frequently asked questions

Is it a spreadsheet?

It looks like one, on purpose. The difference is that the line generates documents, keeps history and controls who sees each column.

Do I need to fill in everything to create a line?

No. The service name is enough. The life of the event brings the rest.

Why is there no unit price?

Because a house that adds totals and a screen that multiplies give the wrong number. Every money field is the line total.

Does the supplier see my cost? Does the client see my margin?

No. Requests, Work Orders and briefings go out with no values. The client sees the sale. Margin only exists for those with both axes.

Does the supplier need an account?

No. They get a link by e-mail, answer the quote or accept the PO right there, and the act is recorded.

Does the table send e-mails on its own?

Never. Every e-mail comes from a click.

Who it's for

For the marketer

The marketing person at the company that commissions the event. They don't want a spreadsheet; they want to know whether the event fits the budget and who approved what. They open the event Summary, follow the budget, approve within their authority and read the Closing Report. Next edition, last year's table is right there.

Sounds familiar? →

For the producer who buys

The company's in-house events team: runs its own events, pays suppliers, sells to no one. The Budget Table is just cost, budget and status. They quote by line, compare, approve within budget, issue POs and Work Orders. Procurement and compliance have the history without asking for a spreadsheet.

For the producer who sells

The agency or production company: buys from the supplier, sells to the client, lives on the difference. Cost from the quote, sale from what the client pays, net margin line by line. The proposal comes out of the table; the client accepts by link. Closing: planned × actual × sold, per event.

Talk to Trabuka

Let's talk about your event?