When a Lahore business gets professionalised, automation is how the knowledge gets written down

The handover problem, which arrives before the technology problem

A pattern repeats across Lahore. A business built over decades by one owner is now partly or fully run by a son or daughter who has studied somewhere else, has seen how a structured company works, and has come back to find that nothing is written down. Pricing decisions live in the father's judgement. The rule about which customer gets extended credit is not a rule, it is a set of remembered favours. The reason a particular supplier is used has never been stated aloud.

The second generation usually reaches for software first, and buys a CRM or an ERP. Then the implementation stalls, because the software wants fields filled with decisions the business has never made explicit. This is the actual starting point for automation work in Lahore, and it is not a technical starting point. It is an interview.

Automation done properly is a forcing function for that conversation. To automate a quotation you have to state how a price is arrived at. To automate follow up you have to decide how many times someone is chased and by whom. Half the value of the first project is that the business ends up with its own rules on paper for the first time, which is worth having even if the automation is later rebuilt.

It also protects against the risk every family business here knows and rarely names. When the person who holds the process leaves, retires or falls ill, the process leaves with them. A documented and running workflow does not.

• Write the pricing rule down before automating a quotation, including the exceptions
• Decide who is allowed to approve a discount, and what happens when they are unreachable
• State the follow up cadence rather than leaving it to whoever remembers
• Record why each rule exists, because the second generation will want to change some of them

Software houses that automate everyone except themselves

Lahore has a large services export layer: software houses, design studios, engineering and back office firms selling time to clients in other time zones. They write automation for a living and run their own operations on a spreadsheet, a WhatsApp group and one very tired project manager.

The pressure points are consistent. Timesheets that are reconstructed on Friday from memory and are therefore wrong. Status reports rebuilt by hand every Monday for each client. Proposals and RFP responses assembled by copying from the last similar one and forgetting to change a name. A recruitment funnel where good candidates go cold because nobody replied for four days. Invoices that go out late because the person who raises them was in a delivery crunch.

The useful builds are internal rather than customer facing. A weekly client report assembled automatically from the tools where the work already happens, with a human writing only the commentary. A proposal draft that pulls the right case description, scope template and rate card and leaves the judgement to a person. A recruitment workflow that acknowledges every applicant within the hour, screens against the actual requirement, and books the ones worth talking to.

One caution specific to this segment. A software house has the ability to build these things itself, so the honest question is not whether an outside firm can do it, but whether the internal team will ever be allowed to stop billable work for long enough. If the answer is that it has been on the roadmap for two years, that is the argument for an outside build. If a team can genuinely take a fortnight, they should build it and own it.

Multi branch retail and the restaurant floor

Lahore's retail and food scene runs at a pace that generates a specific kind of operational debt. A group with four or five outlets is not running one business, it is running five businesses that share a name and disagree about their numbers. Sales come in through the counter, through delivery aggregators, through a phone line and through Instagram messages, and reconciling them at the end of a day is a manual exercise that nobody enjoys and everyone rushes.

Customer contact is fragmented in the same way. A complaint about a late delivery arrives on the aggregator app, on the brand's own Instagram, and sometimes on a public review at the same time, from the same customer. Whichever channel gets answered first is a matter of who happened to be looking.

What helps is boring and effective. Bring every inbound channel into one queue so that a complaint is answered once rather than three times or not at all. Classify by branch and by cause so that the pattern behind repeated complaints becomes visible instead of being absorbed as bad luck. Send each branch manager the same daily summary at the same hour, built from the same source, so that the Monday meeting argues about decisions rather than about whose figure is right.

Reservations and event bookings are worth automating only when the volume justifies it. A restaurant taking a handful of bookings a day is better served by one person who is good at the phone.

Schools, academies and the admissions season

Education businesses in Lahore live with a demand curve that arrives in a few weeks and then disappears. Admissions enquiries spike, phones go unanswered, parents ask the same twelve questions about fees, timings, transport and syllabus, and the staff answering them are the same staff running the current term.

Automation earns its place here mostly by absorbing repetition. A parent asking about fee structure, class timings or the documents needed for admission can be answered accurately at any hour from your own published information, in Urdu or English, with anything unusual passed to a person. Fee reminders and outstanding balance notices can go out on a schedule rather than as a monthly panic. Enquiry records can be captured in a form the admissions team can actually work through instead of a WhatsApp scroll.

The line to hold is that an assistant should never negotiate a fee, promise a seat, or answer a question about a specific child's performance. Those conversations belong to people, and a system that wanders into them will cost more trust than it saves time.

How this works when the firm is not in Lahore

Wobble is an AI automation company based in Karachi. There is no Lahore office and no local team, and saying so is more useful than implying otherwise, because most firms bidding for this work imply a presence they do not have.

For this kind of project it matters less than it sounds. The build happens inside your accounts, your messaging platform and your existing tools, which are reachable from anywhere. Lahore and Karachi share a time zone and a working week, so there is no lag in getting an answer, and travel between the two cities is a morning when a workshop genuinely needs to be in a room.

What a remote arrangement does demand is discipline about access and ownership. Accounts in your company name, administrator rights held by you, and a named person on your side who can approve a change without waiting for a board. Firms that ask for a local presence usually want reassurance that someone will still be answering in six months. That is a contract question rather than a geography question, and it should be answered in the contract.

When the handover has to happen before anything is built

If the business is mid handover and the two generations have not agreed on how things should run, automation will freeze the disagreement into a workflow. Everyone will then argue about the system instead of the decision. Settle the rule first, even roughly, and build afterwards.

If you run a software or services firm with capable engineers and genuine slack, build it yourself. You will maintain it better than anyone else can, and this page is not going to pretend otherwise.

If your retail group's stock or sales data is unreliable at source, an automated report will publish the unreliability faster and to more people. The fix is upstream, in the counter process, and it is not a fun project but it is the one that pays.

And if the honest driver is that a competitor has announced something with AI in the name, wait. Projects started from that motive tend to produce a demo that impresses a meeting and changes nothing about how the business runs on a Tuesday.

Common questions

What kind of Lahore businesses does AI automation actually suit?

Businesses with enough repetition that manual handling genuinely costs money, and enough stability that the process will still look the same in six months. In Lahore that commonly means multi branch retail and food groups, services and software firms with client reporting and recruitment overheads, education businesses with seasonal admissions load, and family businesses being formalised by a second generation. Volume and stability matter more than sector.

We are a family business with nothing documented. Where do we start?

Start with the interview rather than the tool. Pick one process, usually quoting or order handling, and write down how a decision is actually made today including the exceptions. That document is the specification. It is also the most valuable output of a first project, because it survives whatever software you use later and it stops the process from leaving when a key person does.

Do you have an office in Lahore?

No. Wobble is based in Karachi and works with Lahore clients remotely, and there is no local team behind that arrangement. For this work the build happens inside your accounts and tools rather than in an office, the time zone and working week are the same, and travel is straightforward when a session genuinely needs to happen in a room. What matters more than a local address is who holds administrator access and who is accountable in the contract.

Can automation help a restaurant group with several branches?

It helps most with two things. First, bringing complaints and enquiries from aggregator apps, social channels and phone into one queue so each customer is answered once. Second, producing the same daily figures for every branch from one agreed source, so management meetings stop arguing about whose number is correct. Reservation handling is worth automating only when the daily volume is high enough to justify it.

Our software house could build this internally. Should we?

If your team can genuinely take a fortnight away from billable work, yes, and you will maintain it better than anyone else. The reason firms bring this outside is that internal tooling loses every scheduling argument against client delivery, so it stays on the roadmap for years. Judge honestly which of those two situations you are in before signing anything.

How long does a first automation project take?

A single well scoped workflow is usually a matter of weeks. In Lahore the part that runs long is rarely the engineering, it is agreeing the rules the workflow encodes, particularly in businesses where those rules have always been someone's judgement. Programmes covering several processes are phased so each one is running and measured before the next begins.