Cases

Running in production, not in a pitch deck.

WHYBLE. is deployed on real businesses today — a venue on Koh Phangan, a fitness studio, and our own marketing. These are the plays that run.

Deployments

Three proofs, three different surfaces

⌂

Venue · live

The Spot — Koh Phangan

A hostel-venue running a full WHYBLE. node: guest screens, staff dashboard, jukebox, door access and cameras — plus market intelligence on beds, events and weather.

4 screens · guest cinema + staff surfaces
PMS, doors, lighting, NVR on one dashboard
local demand & events feed the venue

The hospitality play

✓

Fitness · live

FitPro

A fitness studio running the local-business play — review watch, member signals and drafted outreach that waits for the owner's approval.

review_spike → draft reply → approve
member & fill-rate signals in the digest
approval cards, not black boxes

The fitness play

⬡

Dogfood · live

This website

hybridin.io runs on the same loop — the market board you see is real data our observers collect, and the briefs pipeline is the product publishing itself.

40 instruments tracked daily
theater cast writes · human approves
missions gather → approvals gate → publish

Open the market board

How a deployment works

The same loop, every tenant

Different surfaces, same pattern — senses read, the brain remembers, drafts wait for humans.

StepWhat happens

WatchesObservers read your sources continuously — reviews, prices, bookings, sensors, inboxes

DraftsFindings become drafted work — a reply, a promo, a brief — never sent blind

ApprovesAnything external waits for a human card: publish, message, mutate

ReportsThe digest tells you what ran, what it found and what needs you

Your turn

Your business could be the next case.

Describe the signals that matter — WHYBLE. composes the watch, the drafts and the gates around them.

Public data only — never paste secrets, customer lists or passwords.