Cafe case study (DRAFT - placeholder)

Status: DRAFT. This page is a template for a single-venue cafe case study. Replace the bracketed sections with a real customer story (with the customer's permission and preferred level of attribution) before promoting this URL externally. The structure below is the one ChillSense uses for cafe and bakery case studies.

The customer

Name: [Cafe name, or "A Sydney specialty cafe" if anonymised]
Location: [Suburb, state]
Format: [Specialty cafe / bakery / artisan bakery / patisserie]
Cold-chain assets: [e.g. one display fridge, one prep fridge, one upright freezer]
Staff size: [Owner + N FoH + N kitchen]
Food safety regime: [State environmental health, with annual inspections]

The problem

[Open with a concrete situation, in the customer's own words where possible. Examples to draw from:]

The owner was the only person who consistently filled in the paper temperature logs hanging off each fridge; staff would forget for days at a time and the logs would be back-filled the day before an inspection.
The cafe had a near-miss the previous summer when the display fridge slowly crept up over a weekend; nobody noticed because nobody was looking until Monday morning.
The owner had previously trialled a consumer-grade Bluetooth fridge logger; the data lived on one person's phone and was useless when that person was on holiday.

The ChillSense deployment

Hardware: Cafe Pack - 1 hub + 3 sensors.
Subscription: 3-sensor monitoring - [monthly or yearly].
Sensor placement: [1 - front-of-house display fridge; 2 - back-of-house prep fridge; 3 - upright freezer].
Hub placement: [Single hub on the back-of-house wall socket; clear line of sight to all three sensors.]
Install time: [Under an hour; staff briefed in the same visit.]

The first month

[Describe what happened in the first month of real use. Common patterns to draw from:]

Owner stopped doing the manual paper log entirely; the dashboard's start-of-shift glance replaced it.
1-2 minor excursions in the first week, all door-related during morning prep; debounce + sensible thresholds meant only one became an SMS alert.
The first monthly HACCP PDF report arrived in the dashboard reports area at month-end. Forwarded directly to the food safety officer without modification.

The outcome that mattered

[Describe the concrete operational outcome that made the deployment "worth it" for the customer. This is the heart of the story.]

Example structure:

Three months in, ChillSense surfaced a drift pattern in the display fridge - readings creeping up by about half a degree per week over a fortnight, still inside the safe range but visibly degrading on the dashboard trend view. [Owner name] booked a service visit before the asset hit a hard breach; the technician found a degraded door seal and replaced it under warranty. No stock loss, no incident on the audit record, and the seal replacement cost a fraction of the wholesale value of a single weekend's chilled stock.

"Honestly, the subscription pays for itself the moment it warns me before stock is lost," said [Owner name]. "And the monthly PDF means the food safety officer audit went from a stressful prep day to a five-minute email."

What the customer says about ChillSense day to day

[2-3 short quotes from the customer about specific behaviours. Examples:]

"I check the dashboard on my phone while the espresso machine warms up. Twenty seconds, every morning."

"The casuals don't have to know anything about it. They get an SMS, they tap it, they pick what they did, done."

"The first monthly report turned up looking exactly like what the auditor asks for. I didn't have to do anything."

Configuration details (for technical readers)

Per-asset thresholds:
Display fridge: [range]
Prep fridge: [range]
Freezer: [range]
Alert contacts: Owner + head barista; SMS + email.
Quiet-hours policy: [Owner only after 9pm to avoid waking staff.]
Reporting cadence: Auto monthly PDF; on-demand pre-audit pack.