Tre & Tide Operations & Automation

Blog · Real build

One studio, one system.

How a podcast studio's booking portal, payments, iOS app and Slack updates were built to work as one. No names.

Anna Bui · 4 min read

A podcast studio runs on a lot of small jobs.

Someone books a session. Someone sends the invoice and checks it got paid. Someone makes sure the recording saved, gets it to the editor, and tells the customer when their episode is ready to review.

In a small team, that someone is usually the same two or three people.

When I started on this build, each of those jobs lived in a different tool. Bookings in one place, invoices in another, contracts somewhere else, recordings in a fourth. The glue between them was a person, chasing.

So the goal was simple: less admin for a small team.

Start with the booking

Everything in a studio starts with a booking, so that's where I started too.

The studio's website has a booking page. A customer picks a package and a time at least 48 hours ahead, and the session goes straight onto the studio's calendar.

Payments without the chasing

When a booking comes in, a QuickBooks invoice is created for it and the payment link goes out from the studio's own email.

If it isn't paid in time, the slot is released. Nobody has to remember to check.

When a booking needs a person, like a returning customer on a special rate, it lands in Slack as a draft invoice for the team to finish. It doesn't wait for someone to notice it.

One portal for the customer

Customers get their own portal. They can see their upcoming sessions, cancel if they need to, read and sign their contract, and watch their edits and leave comments in one place.

Before, each of those was its own email thread.

The app in the room

In the recording rooms, an iOS app runs the session: start, end, and what happens next.

When the session ends, the footage moves on to editing without anyone dragging files around.

Slack is where the team sees it

The team already lived in Slack, so that's where the system talks to them:

  • New bookings, and invoices that need a hand
  • A daily summary of where every episode is in production
  • An alert when a connection lapses, with reminders in the same thread until it's fixed, and a ✅ when it's back

That last one I learned the hard way. The first version posted a new alert every time a check failed, and the channel filled up with the same message. Now it's one post, one thread, and an update when it's fixed.

Built around the tools they already had

I didn't ask the team to move into a new tool. They already had QuickBooks for invoices, a shared calendar for sessions, ClickUp for episodes, Frame.io for edits and Slack for talking to each other. Each one was good at its job. The problem was the gaps between them.

So the system sits in the gaps. A small database and a few background jobs pass information from one tool to the next: a booking becomes an invoice, a paid invoice becomes a confirmed session, and a finished recording becomes an episode in production.

The most important decision was which tool owns which piece of information.

Session times are a good example. It would have been easy to read them from the database. But people reschedule and cancel in the calendar, and the database never hears about it. So the calendar owns session times, and the portal reads them straight from there.

Sometimes building around a tool means working around it. When QuickBooks wouldn't send the payment email, the invoice stayed in QuickBooks and the link went out from the studio's own email instead. And when a connection needs signing in again every couple of weeks, the system can't do that for the team. So it tells them clearly, once, and keeps reminding them in the same thread until it's done.

None of these tools are unusual. The work is in how they connect.

Built one piece at a time

It wasn't one big project. I built it piece by piece, and each piece had to work on its own before the next one connected to it.

That's what I'd tell any small team: you don't need to replace everything at once. Pick the job someone chases most often, and start there.

If your team is doing the glue work by hand, I'm happy to talk it through (opens Google Calendar in a new tab).

Work with me (opens Google Calendar in a new tab)

Want to talk through your own workflow?

Book a call and bring one workflow, or send me a short message about what keeps going wrong.

Message me