Three systems, one operating layer.Three systems, one operating layer.Three systems, one operating layer.
An app your team opens, the automation that fills it, and a voice that answers when nobody can. Each is stronger because the other two exist.
01 · Apps
Interfaces people actually use.
Field apps, dashboards and customer portals — designed around the two minutes a person has, not the forty a form wants. Offline-first where the signal drops.
Android & webDashboardsField captureOffline sync
HeadcountToday · by block
Tap a block · submit
02 · Automations
Work that quietly finishes itself.
Leads answered in the minute they arrive. Invoices that chase themselves. Reports that land before the meeting. WhatsApp, sheets, CRM and payments wired into one flow — and watched, so you don't have to.
Inbound or outbound, in English, Urdu, Hindi or Arabic. It books, qualifies and follows up, and hands over to a human the moment it should — transcript already in your inbox.
A fixed sequence, because order matters. You touch something working in week two — not a deck in month three.
01Week 1
Discover
We sit with the people who do the work. Half a day, real screens, real calls. We leave with the three things that waste the most time.
Field interview notes“We type the headcount twice a day.”“Invoices get chased by memory.”— calls after 6 pm go unanswered— 3 leaks worth fixing · 1 worth deleting
02Week 2
Design
A clickable app, a live voice script you can call, the automation drawn on one page. You approve what you can touch.
Book
Clickable prototypeTap through it on your own phone.A voice script you can call.
03Weeks 3–4
Build
Your data, your numbers, your WhatsApp. A pilot crew uses it for real while we're still in the room.
Working workflow
Formn8nSheetWhatsApp
● pilot crew · live since Tuesday
04Ongoing
Run
We watch every flow and every call. When something changes in your business, the system changes that week.
Live system dashboardWhatsApp flows● healthyVoice line● healthyInvoice chaser● healthyLast change● this week
Work
Shipped, not mocked.
Three systems built end to end by one person — designed, coded, run on real crews, still in use. Phone screens are live captures, not renders.
DripYap · f/1.4
Chapter 01
DripYap
Private communication infrastructure.
Problem
Team and client conversations live on personal phone numbers, inside someone else's cloud.
System
A Kotlin messenger on your own server. Members join by invite code; bot accounts wired to n8n post announcements, reminders and answers.
Outcome
Branded rooms the organisation owns. Nobody hands over a personal number, and nobody is the product.
Press the gold button, allow the microphone, and talk.
Hear it live
Press call. Listen.
A real agent on our own server, not a recording. It listens, thinks and answers in about a second. Interrupt it, ask it to book a callback, try to confuse it.
Answers in about a second
No hold music. It picks up before the second ring.
Acts, not just talks
Books the slot, sends the WhatsApp, updates the sheet — during the call.
Knows when to stop
Anger, confusion or a question it can't answer goes to a human, with the transcript.
Your voice, your rules
Trained on your prices, your policies, your way of speaking. Nothing invented.
Speech recognition · کٲشُر · اردو
Speak Kashmiri. Read it back.
Our own speech-to-text for Kashmiri and Urdu, on our own server. Not perfect yet, but a Kashmiri or Urdu reader will understand what was said.
Tap, say a sentence, tap again.
Your words will appear here in Nastaliq script.
Runs on Lumivon's server · open models, no big-cloud API
Where it runs
Built in Kashmir. Designed for everywhere.
Every system on this site was built from one studio in Srinagar — and the phones, crews and callers using them are not all in one place.
Srinagar · home
India
UAE
Saudi Arabia
Qatar
Oman
United Kingdom
01234567890123456789systems shipped and still running
0123456789.0123456789Mautomated actions every month
0123456789.0123456789saverage voice pickup
0123456789countries, four languages
From a discovery session · the system before the software
About
Built by someone who sits in the room.
Sheikh Muhibul Hassan (Muhib) · Founder & lead engineer
I build every Lumivon system myself, with the people who will use it in the room. Apps in Kotlin and AppSheet, automations on n8n and WhatsApp, voice agents that book and follow up in four languages. If it ships with my name on it, I have run it on a real crew first.
What I believe
Sit with the people who do the work before drawing a single screen.
Show something you can touch in week two, not a deck in month three.
Twelve questions, answered honestly, that show you where your week actually goes — and which of those leaks is worth fixing with software and which is not.
The four leaks that show up in almost every business here
How to tell a process worth automating from one worth deleting
What each fix really costs, in weeks and in rupees
Questions
Asked before signing.
Start a project
Put your operations in a better light.
Tell Muhib the one thing that wastes your team's week. You get a reply the same day — usually within a couple of hours — with a plan, a price and a date.
TodayA reply with a plan, a price and a date. Not a brochure.
Week oneA call with the people who do the work, then a written scope.
Week fourA working system your team uses for real, in your own accounts.
LUMIVONApps · Automations · Voice
