Sahulat

Small service businesses often coordinate appointments, staff availability, customer messages, and bills across separate chats and paper or spreadsheet records. That makes routine work harder to track, especially when the customer journey begins on a phone and should feel natural in Urdu.

Four workflow gaps

Disconnected booking: A request can arrive in a conversation without a consistent way to capture the service, provider, duration, date, and customer contact details.

Availability conflicts: A requested time must fit both the selected provider and the service's full duration, or the booking can collide with work already scheduled.

Follow-up depends on memory: Reminders and missed-appointment recovery are easy to overlook when nobody owns a reliable schedule.

Billing loses the thread: A completed appointment needs a matching invoice and payment status, while a cancelled booking should not leave an unpaid bill behind.

One bilingual customer and owner workflow

Sahulat is a local-first product demo for three Pakistan service businesses: Noor Salon in Gulberg, Lahore; Ilm Academy in Johar Town, Lahore; and Apna Repair in Saddar, Karachi. Each sample business has its own services, providers, appointments, invoices, conversations, and follow-ups.

Customers can use the guided booking flow in Urdu or Roman Urdu. They choose a service and eligible provider, then an available appointment time. Availability is provider-specific, uses 30-minute increments, and checks the full service duration. Repair bookings also ask for a device note.

The owner workspace brings today's appointments, bookings, invoices, and follow-ups together. Owners can review appointments, reschedule or cancel them, mark attendance, and view a customer conversation in a WhatsApp-style simulator.

Completing an appointment creates its invoice once. A missed appointment queues a rebooking follow-up. Eligible bookings can queue a reminder at least 24 hours ahead; the demo clock is advanced manually to process due messages.

The payment panel demonstrates successful, failed, and cancelled JazzCash, Easypaisa, or card outcomes. These are local simulations: they do not connect to payment providers or move money.

A runnable React MVP that brings the customer booking journey and the small-business owner workflow into one responsive, right-to-left-capable browser app.

The seeded walkthrough covers salons, tutoring, and device repair, with nine sample services in total and two eligible providers per business. Service names, prices, customers, and activity are illustrative demo records, not findings from live businesses.

Urdu is the default language, with a Roman Urdu switch. The interface supports both directions, and date and time calculations use Pakistan Standard Time.

The app uses browser local storage on one browser and site origin. It has no server, accounts, shared multi-device records, background scheduler, live WhatsApp integration, or live payments. The follow-up clock runs only while a user advances the demo.

No field-pilot results, adoption figures, time savings, revenue recovery, or production operating costs have been measured. The MVP demonstrates the workflow and marks the integrations that still need a production implementation.

A reusable product pattern for appointment-led local services: make the customer path simple, give the owner an operational view, and keep booking, attendance, billing, and follow-up connected to the same record.