Every map is the same exercise: sticky-note the process A→Z as a real Lebanese person lives it, then delete → simplify → automate. Scores are comparable across maps (same 4-part rubric). Goal: pick what we demo Saturday 8AM — and what we only talk about.
Each pillar's highest score that is also demoable by Saturday with zero external integration. Together they tell one story: the agent interviews you once, then does the work — sells your stuff, builds your livelihood, fights your bureaucracy.
Rubric: Pain = how red the map is · Collapse = share of steps deleted/automated · Market = frequency × value in Lebanon · Demo = feasible by Saturday without integrations. Overall = mean.
| # | Process | Steps | Overall | Call |
|---|---|---|---|---|
| 1 | No single pain is severe — it's death by thirty WhatsApp chats; the agent can do everything between the photo and the handover. | 16 → 3 | 8.0 | Demo |
| 2 | The onboarding interview IS the product — and every provider interviewed becomes the supply for the other maps. | 16 → 3 | 8.0 | Demo |
| 3 | The embassy decision can't be collapsed, but ~80% of the suffering is prep and slot-hunting — exactly what a chat concierge demos brilliantly. | 21 → 5 | 7.8 | Demo |
| 4 | Everything between "it broke" and "it's fixed" is search, phone tag, and price anxiety — none of it is the repair. | 19 → 5 | 7.8 | Demo |
| 5 | The buyer's real job is surviving a hostile information market — "qualify me once, then hunt and verify for me" deletes the grind. | 24 → 5 | 7.5 | Demo |
| 6 | The product isn't search, it's trust — the verification layer Lebanon's used-phone market never had. | 18 → 4 | 7.5 | Demo |
| 7 | The atomic dependency of all Lebanese paperwork — requirements are oral tradition and the 3-month validity clock kills every bigger file. | 14 → 3 | 7.3 | Demo |
| 8 | No book value, no escrow: six weeks of pricing by vibes, lowballers, and trusting strangers with your keys and your cash. | 22 → 5 | 6.8 | Roadmap |
| 9 | Listed rent is fiction — the real product is the true monthly cost (rent + moteur + water + fees) interrogated out of every landlord. | 22 → 6 | 6.5 | Roadmap |
| 10 | Price opacity → inbox congestion → slot decay; fixing it requires owning real calendars that can't be faked by Saturday. | 16 → 3 | 6.5 | Roadmap |
| 11 | The state is mid-digitization — ailb's edge is surviving platform volatility; biometrics and production time cap the collapse hard. | 17 → 4 | 6.5 | Roadmap |
| 12 | Parents pay $300/month behind a closed door with zero progress data — the real product is the progress loop, which is slow to make credible. | 18 → 3 | 6.3 | Roadmap |
| 13 | Already half-disrupted — LibanPost/OMT quietly solved access and nobody knows it; a concierge can nearly fully absorb the errand. | 14 → 3 | 6.3 | Roadmap |
| 14 | The pain is stubbornly physical — what collapses is the coordination layer between two strangers: a novel two-party chat, a harder solo demo. | 20 → 6 | 6.0 | Roadmap |
| 15 | The market punishes whoever believes a number — but the job stays stubbornly physical and people move once every few years. | 16 → 4 | 5.8 | Skip |
Patterns that emerge when you read all 15 maps side by side — use these lines in the pitch.
Across all 15 maps the red stickies are the same species: no prices, no reviews, no escrow, no recourse, strangers and cash. Lebanon doesn't lack marketplaces — it lacks a trust layer. ailb's agent is that layer: it qualifies, verifies, and vouches.
Every winning flow starts the same way: the agent asks you about yourself once — what you're selling, what you can do, where you want to go — and the listing, profile, or document file falls out of the conversation. No forms anywhere.
Map #8 (sell car) + #5 (buy car) + #14 (transfer) chain into one narrative: ailb sells your car, finds the buyer their car, and walks both through the mécanique with a prepared file and one visit. Pitch it as the vision; demo the trio above as the proof.
No API will save you at the mukhtar. The honest gov play is knowing the live requirements, prefilling the file, watching validity clocks (ikhraj qaid < 3 months!), sequencing dependencies, and making every mandatory visit a single prepared one.