Bloom & Bean.
A warm welcome.
A connected workflow.
From the first reservation to the final confirmation. A café experience powered by the tools a small team already knows.
Explore the systemThe website is only
the beginning.
Bloom & Bean began with a simple question: how far could a small-business reservation workflow go using tools the team already has?
The result connects the customer experience to everyday operations. A request enters Google Sheets, staff verifies payment, and a single status change starts the confirmation workflow.
-
01
Workflow first.
Map what happens after a guest clicks “Reserve,” before choosing what to automate.
-
02
A human decision.
Staff confirms that payment arrived. The system handles the work that follows.
-
03
Native connections.
Apps Script brings Sheets, Gmail and Calendar into one connected process.
-
04
Familiar operations.
The team works from a spreadsheet, with clear statuses and booking details.
A form collects a request.
Who handles the rest?
Recording the details. Checking payment. Booking the calendar. Notifying the guest. The goal was to connect these repetitive tasks while keeping the important business decision with the team.
One reservation. One connected workflow.
The customer sees a reservation form. Operations sees a tracker. The system handles the handoff between them.
Keep the human where the human matters.
Payment remains a deliberate staff decision. Once the reservation is marked Paid, the system creates the 90-minute calendar event, invites the guest, and records the event reference.
From booking to confirmation.
No extra dashboard was introduced. The workflow sits inside the tools the team already uses.
6:30 PM – 8:00 PM
Guest invited
Less software. Less manual work. Clearer operations.
Bloom & Bean is a small demonstration of a larger idea: thoughtful systems design can remove repetitive admin without forcing a business into a stack of new subscriptions.