The Deeper Dive / Supabase / 1:55
Three versions of Tuesday
A plumbing shop has three different schedules. The owner needs one job record the office and technicians can trust.
Read the episode transcript
AI voices perform a script reviewed by Mata.Works. Landon and Tam are the illustrated hosts. The business scenario is an example.
Landon: Tuesday morning at a small plumbing company. The office has six jobs on a spreadsheet. A technician has seven in a text thread. The owner has a photo of a whiteboard with eight. Which one is the schedule?
Tam: At the moment, nobody knows. And that is expensive in a very ordinary way. Someone drives to an address after the customer has moved the appointment. Another customer never gets a call back.
Landon: So we buy Supabase and the three lists become one?
Tam: Somebody still has to build the workflow. Supabase can hold the shared records behind a custom tool: each job, address, status, and update in one database. It can also handle sign-in and rules about who may see or change a record. It does not decide which of those eight jobs is real.
Landon: Who decides that?
Tam: The business. Start with one rule: the dispatcher owns the schedule. When a customer moves a visit, the office changes the job record. The technician sees that change in the tool. A text can alert somebody, but it should not become a second schedule.
Landon: Give me a test that would catch a bad build before we put the team on it.
Tam: Change a job from Tuesday morning to Wednesday afternoon. Can the technician see the new time? Can a different technician see that customer's phone number when they should not? Can the office tell who changed the job? And if the internet drops in the van, what does the technician see?
Landon: That last one matters. A database in the cloud does not make a phone work offline.
Tam: Right. The app has to handle that. The owner also needs to know how records are backed up and how to export them. A database is where the truth lives; the team still needs a clear way to use it.
Landon: What if their current field service system already keeps one good schedule?
Tam: Keep it. We would only propose a custom tool when a real gap survives a look at what they already pay for. The decision is simple: can everybody act on the same job record, with the right access, without another round of copying and guessing?