A Book-Lending Business That Runs on 2 Minutes a Day

Dahabibi lends English books to travellers and digital nomads in Dahab, Egypt. It has one owner and no staff. This is my own venture: I designed, built and run the system myself.

Run by hand, every loan would take a string of manual steps: WhatsApp messages back and forth, remembering who has which book, noting due dates, chasing late returns, and working out late fees and loyalty rewards by hand.

That's fine with 5 readers. With 50, it falls apart: books get double-promised, reminders get forgotten, and nobody knows whether the business is actually making money.

Six automations that work together as one system:

Online booking page. Readers choose from books that are actually on the shelf. Once a book is booked, it disappears from the list automatically.

Instant confirmation. The reader gets a booking reference and a one-tap WhatsApp button to confirm. At the same moment, the owner gets an alert.

9 AM morning briefing. Every day the owner gets one message listing who is picking up, what's due back, and who is late, with the reminder messages already written.

Updates in one tap from a phone. When a book goes out or comes back, the owner sends a short Telegram message. Late fees, loyalty rewards (every 5th loan is free), and stock levels update on their own.

Monday business report. Loans, revenue, repeat readers, and lost books are delivered automatically every week.

Safety net. If any part of the system fails, the owner is alerted right away with the details.

About 2 minutes a day of owner time to run the whole operation

No manual bookkeeping. Fees, rewards, stock, and weekly numbers are all calculated automatically.

Built and live in about a week, running on the business's own website: dahabibi.online

Tested end to end before launch. The full journey from booking to pickup to return to report was proven with live test bookings on the real system, backed by 90+ automated checks.

During beta testing, one booking was saved twice. Two copies of the same request arrived 4 seconds apart, the kind of thing a double tap on a slow connection causes. Left alone, this would have corrupted that booking, for example, marking a collected book as not picked up.

Within a day I found the cause and fixed it at three levels:

The submit button now can't be tapped twice

The system double-checks right before saving, and shows the reader their existing booking instead of creating a copy

The daily briefing, the owner's phone commands and the weekly report all detect a duplicate. Instead of acting on it, they warn the owner

Then I recreated the exact situation on the live system to prove the fix works.

What this means for clients: I don't stop at "it worked in my test." I build for what real people actually do, like double taps, slow connections, and mistakes, and I fix issues properly when they come up.

n8n (self-hosted) · Google Sheets · Telegram · WhatsApp · Gmail · Claude Code · Custom domain & server