Every Umrah agency has The File.
It's called something like UMRAH-RAMADAN-FINAL-v7-NEW(2).xlsx. It has fourteen tabs. Three people edit it — one of them on a copy from last Tuesday. The rooming tab has colors whose meaning only Amina remembers, and the payments tab has a column labeled "paid?" with values like yes, YES, half, and ask him.
If this is your agency, nothing is wrong with you. Excel is where every agency starts, because it's flexible and it's already on the computer. But "free" is doing a lot of work in that sentence.
What Excel actually costs you
Hours, first
Count the manual work in one 45-pilgrim departure:
| Task | Typical time in Excel |
|---|---|
| Typing pilgrim + passport data from photos and forms | 10–15 min × 45 pilgrims |
| Chasing missing fields ("send me the passport again") | hours, spread over weeks |
| Building the rooming plan by hand (twice — Makkah and Madinah) | 2–4 hours, redone after every change |
| Re-typing the flight manifest into the airline's format | 1–2 hours, plus corrections |
| Reconciling who paid what | ongoing, error-prone |
| Producing the visa file in the format the system expects | 1–2 hours |
That's easily 25–40 working hours per group of pure clerical work — before anything goes wrong.
Then, errors
Spreadsheet mistakes in this business aren't typos; they're incidents:
- A passport number copied one row off — caught at visa submission, or worse, at the check-in desk.
- A room assigned twice — discovered in the hotel lobby in Makkah at 2 a.m., with 45 tired pilgrims watching how you handle it.
- A missed installment nobody chased — discovered as a hole in the budget after the group returns.
- The file itself lost — a laptop dies, and with it the only current copy. (Passport data in an unencrypted spreadsheet on a personal laptop is also a GDPR problem — see Passport & Document Management.)
Each of these costs more — in money and reputation — than a year of proper software. Pilgrims forgive a delayed bus. They tell everyone about the agency that misspelled their name on a ticket.
Finally, growth
Here is the uncomfortable ceiling: Excel scales with your hours. Two departures a year is manageable. At five, evenings disappear. At ten, you either hire someone to do data entry — a salary, to maintain spreadsheets — or the owner becomes the bottleneck for every list, every change, every question. The knowledge lives in one person's head and one fragile file.
What changes with purpose-built software
| Task | Excel + WhatsApp | Purpose-built platform |
|---|---|---|
| Pilgrim data entry | You re-type from photos | Pilgrims register themselves via a link; you review and approve |
| Passports | Photos in chats | Uploaded to an encrypted profile, duplicates auto-detected |
| Rooming | Colored cells, by hand, twice | Live bed counts, gender rules enforced, auto-assignment, hotel-ready export |
| Flight manifest | Re-typed per airline | Generated in the airline's format from the same data |
| Payments | "paid?" column | Per-pilgrim balances, installment plans, outstanding list |
| Group profit | Nobody truly knows | Live, per group |
| Next season | Copy the file, delete old data, hope | Copy the group structure, keep clean history |
The pattern: data is entered once, by the person who owns it, and every document — rooming list, manifest, visa file, invoice — is generated from that single source instead of re-typed.
Migrating without drama
The fear is always "we can't switch mid-season." You don't have to:
- Export what you have. Your Excel is not wasted — it's your import file.
- Import it. Ziyara imports pilgrims from a spreadsheet template in bulk and flags duplicate passports on the way in.
- Run one group in parallel. Keep The File for your current departure; run the next departure in the new system. Compare the workload honestly.
- Switch when convinced. Nothing forces the whole agency to move on day one.
The 14-day free trial fits this exactly: import up to 20 pilgrims, build one real group, generate the rooming list and manifest you'd otherwise build by hand — and then decide whether The File deserves a v8.