Not a process diagram — a wall of what the person actually experiences, A to Z. One sticky = one thought, decision, action, problem, or cost. Color reveals where ailb deletes, simplifies, or takes over.
It's never a convenient thing, and it's never a convenient time.
There is no directory. There are only people who know people.
Phone tag with people whose office is their pocket.
"Ba3d el dohor" is a window of time that extends to never.
The price is a function of your building's marble, not the broken part.
The warranty is a feeling.
Draw the arrows and the "process" collapses into a few tight feedback loops. These are where people get stuck, re-decide, and abandon.
The strongest opportunities aren't the happy-path clicks — they're the things people genuinely don't want to do.
What survives after delete → simplify → automate. The human only does what only the human can do.
The map is nearly all red: every step between "it broke" and "it's fixed" is search, phone tag, waiting, and price anxiety — none of it is the repair itself. The photo-diagnosis + fixed-quote + dispatch chain deletes almost everything except the visit, and photo diagnosis alone is a jaw-drop demo moment that needs zero real supply. Recommendation: hackathon demo flow — demo the diagnose→quote→dispatch conversation with 2–3 seeded pros.