Generative Engine Optimization for an Islamabad Logistics SaaS

The Client

An Islamabad-based vertical SaaS company that builds last-mile delivery and cash-on-delivery reconciliation software for Pakistani e-commerce couriers, 3PL operators, and D2C brands running their own fleets. The platform handles route optimisation, rider allocation and tracking, proof-of-delivery, and the awkward, high-stakes work Pakistani logistics runs on: reconciling COD collections against orders, tracking shortfalls and rider balances, and settling cash across a delivery network where most parcels are paid for in cash on the doorstep. At the point of engagement the business had roughly 1,400 paying operators across Punjab, Sindh, and Khyber Pakhtunkhwa, an average revenue per account between PKR 18,000 and PKR 40,000 a month depending on fleet size, and a board target to double the operator base inside eighteen months.

Go-to-market was founder-led sales into logistics teams, a modest paid programme of about PKR 1.1M a month across Google Search and LinkedIn, and a content engine publishing technical articles each fortnight on route planning, COD reconciliation, and fleet economics. The team had invested seriously in classic SEO and held page-one rankings for a cluster of branded and adjacent terms. What they had not done was think clearly about where a Pakistani e-commerce operations lead actually starts research in 2026: by typing a question into an AI assistant.

The engagement began after the head of growth ran a simple test. He asked three AI assistants — ChatGPT, Perplexity, and Gemini — “best delivery management software for e-commerce in Pakistan” and “COD reconciliation tool for couriers.” The company was not mentioned in any of the answers he collected. The recommendations were international delivery platforms that do not model Pakistani COD settlement or rider cash handling at all. Two local competitors with thinner products but more answer-friendly content appeared consistently. That gap, not a rankings dip, was the real growth blocker — and the team suspected it was already costing them deals they could not see.

The Problem: Invisible Where the Buyer Now Starts

Four issues were quietly capping the company’s pipeline:

• Near-zero citation share. Across a tracked set of 55 priority commercial queries — things like “delivery management software Pakistan,” “COD reconciliation software for couriers,” “rider management app for e-commerce,” and “route optimization for last-mile in Lahore” — the brand was cited in only 7% of AI answers. Competitors with weaker COD logic but more answer-friendly content appeared two to three times more often.
• Content built for features, not extraction. Product and integration pages were written as feature inventories and technical specs. Summarisation models could not reliably extract a clean answer to “Does it handle COD reconciliation?” or “What integrations does it support?” because the relevant facts were buried in feature lists and developer documentation rather than stated as plain answers.
• AI crawlers partially blocked. An inherited web-application firewall and an overly strict robots.txt were rate-limiting and in places outright blocking the major AI crawlers. The site was being indexed for classic search but under-crawled by the models generating the answers buyers actually read.
• No measurement. Trial signups that arrived because a buyer had seen the brand in an AI answer showed up in analytics as direct or branded-search traffic. The team had no way to prove AI visibility was worth investing in, so it never got budget.

This is the core pattern we see across SaaS marketing in Pakistan: classic SEO looks healthy, paid is steady, and the fastest-growing source of commercial intent — AI answers — is invisible and unmeasured.

There was also a measurement trap underneath the visibility problem. Because the team had no citation tracking, any demand generated by AI answers was landing in the “direct” or branded-search bucket and being credited to other channels. AI visibility looked like a cost centre with no return, when in reality it was already producing trials the company could not see. Fixing the visibility gap and fixing the attribution gap were the same project — you cannot claim credit for what you do not surface, and you cannot justify investment in what you cannot claim credit for.

Phase 1 — AI Visibility Audit and Crawl Access (Weeks 1–2)

The first two weeks were diagnostic. You cannot fix what you have not measured, and the company had never measured citation share systematically.

Building the citation baseline. We assembled a tracked query set of 55 priority commercial queries, stratified into three tiers: 18 high-intent commercial queries (“delivery software Pakistan price”), 19 problem queries (“how to reconcile COD collections against orders”), and 18 comparison queries (“delivery management software vs Excel for couriers”). Each query was run weekly against five answer surfaces — ChatGPT, Perplexity, Gemini, Google AI Overviews, and Microsoft Copilot — and every answer was scored for whether the brand was cited, mentioned without citation, or absent. This produced the 7% baseline and gave us a defensible scoreboard for the rest of the engagement.

The tiering mattered as much as the tracking. Commercial queries are where citations turn directly into trials, so they carried the most weight. Problem queries are where the brand could earn authority citations that bleed into commercial answers later. Comparison queries are list-shaped by nature, which made them the fastest path to being named alongside competitors even before the brand could win a direct-answer citation. Scoring each tier separately let the team see which kind of visibility was moving and which was stuck, rather than collapsing everything into one number that hid the real story.

Crawl-access audit. Server logs showed the major AI crawlers were hitting the site but a large share of requests were returning 403 or 429 status codes from the WAF. We reviewed the full generative engine optimization and AI discoverability checklist and produced an access fix list.

Access issue	Before	After (Week 2)
AI crawler requests blocked / rate-limited	~38% of hits	Under 4%
robots.txt disallowing AI user-agents	2 agents	0 (explicit allow)
Key commercial pages reachable by models	9 of 55 target pages	44 of 55
Structured data describing the product	None	Draft schema mapped

Entity and content inventory. We catalogued every commercial and integration page and tagged whether it contained a clean, extractable answer to the question a buyer would actually ask. Only 8 of 55 target pages passed. The remaining 47 needed restructuring — not necessarily rewriting from scratch, but reorganising so the answer came first and the supporting detail came after.

The pass rate exposed a deeper habit in how the team wrote. Their content was accurate and technically deep, but it was structured for a logistics manager who scrolls through a feature comparison. A summarisation model does not scroll patiently; it extracts. Pages failed the audit not because the information was missing but because the single sentence that answered the buyer’s question was embedded in a feature table or a documentation heading a model treated as ancillary. The fix was structural, not creative, which is why Phase 2 moved as fast as it did.

By the end of Phase 1 the company had a measurement system, open crawl access, and a prioritised list of 47 pages to restructure. No content had been published yet, but the foundation was in place.

Phase 2 — Answer-First Content and Entity Rebuild (Weeks 3–6)

With access fixed and measurement running, we restructured how the site communicated facts. The principle was simple: an AI summarisation model should be able to answer “What is this, what does it cost, and who is it for?” by reading the first screen of any product or integration page.

Answer-first page architecture. Each of the 47 prioritised pages was rebuilt around a tight answer block at the top — a 40-to-60-word direct answer to the page’s core question, followed by a short capability list, a pricing range, a supported-integrations line, and a “who this fits” note aimed at Pakistani couriers and D2C fleets. The long-form technical detail moved below, structured with clear H2 questions. This served two audiences simultaneously: human operations leads who want a fast scan, and models that extract the lead answer for citation.

Pricing and product schema. We implemented SoftwareApplication, Offer, FAQPage, and ItemList schema across commercial and comparison pages, plus an organisation-level entity definition describing the company, its product categories, and its relationships — supported integrations (Shopify, WooCommerce, Daraz), supported compliance and settlement frameworks (COD reconciliation, rider cash balance, proof-of-delivery), and customer verticals. This is the connective tissue that helps a model place the brand inside an answer rather than treat it as an undifferentiated string of text. The pattern mirrors the work in our SEO for AI Overviews service.

Two schema details had outsized effects. First, the FAQPage blocks were rewritten so each answer was a self-contained 30-to-50-word statement that matched, almost verbatim, the phrasing a buyer would use to ask the question — including the awkward ones like “how does it handle COD when a rider returns with uncollected cash.” Models reach for FAQ answers because they are pre-formed, citable statements; vague or hedged answers get skipped. Second, the SoftwareApplication markup carried explicit applicationCategory, operatingSystem, and offers fields, which gave the models structured facts about what the product is and what it costs — the two things buyers most often ask about and the two things the old pages buried deepest.

Comparison and list-inclusion content. AI answers cite two things disproportionately: direct answers to the question asked, and list-style comparison content that already names the options. We built out nine structured comparison pages (“delivery software for D2C brands,” “COD reconciliation tools for couriers,” “rider management apps for last-mile in Pakistan”) formatted as clear, neutral comparisons — including competitors — because answer engines reward comprehensive, unbiased source pages over self-serving ones.

Phase 2 checkpoint (Week 6):

• 47 product and integration pages restructured to answer-first architecture
• Product, pricing, FAQ, and ItemList schema live on commercial pages
• 9 comparison pages published
• Citation share moved from 7% to 20% as restructured pages were reprocessed

The jump to 20% was the first proof point. It came entirely from existing content being made extractable — no new domain authority, no link building, just clarity about what the product does for Pakistani operators.

Phase 3 — Citation Earning and Authority Signals (Weeks 5–10)

Restructuring earned citations on queries where the brand already had some relevance. The next layer — being cited for queries where international tools currently dominated — required authority signals that models use to decide who is credible on a topic.

The source-of-truth problem page. For the 19 problem queries in the tracked set, the highest-leverage move was a single deep explainer on COD reconciliation in Pakistani e-commerce: how collections are reconciled against orders, where shortfalls arise, how rider cash balances are settled, and what the failure modes look like at scale. This was the page no international tool could write, because it describes a workflow they do not model. It linked clearly back to the product as the implementation path, but it earned its place by being the best available answer to the underlying operational question. Within weeks it became the page models reached for when substantiating a claim about COD logistics.

External corroboration. Answer engines weight brands that are discussed in places they trust. We ran a focused digital-PR and partner-listing effort to place the company in relevant Pakistani e-commerce and logistics communities: 3PL operator directories, e-commerce enabler resource pages, rider-fleet community forums, and integration partner directories. The goal was not link equity in the classical sense; it was the density and diversity of independent mentions a model could surface when answering “which tools do Pakistani couriers use for delivery management.”

A specific tactical choice mattered here: we prioritised corroborating sources that themselves get cited. A mention on a generic directory few models trust moves nothing; a mention in a well-maintained industry resource that already appears in AI answers cascades quickly. We tracked not just the count of placements but whether the placing pages themselves showed up as citations, and weighted effort toward the latter. Eleven well-chosen corroborating mentions outperformed forty low-quality ones, which is the opposite of the volume logic that governs old-school directory link building.

Review and reputation surface. We consolidated genuinely collected operator feedback onto a structured page (without inventing ratings) and connected the entity so that when a model assembled an answer it could pull consistent, verifiable signals about customer base and traction.

Phase 3 results (by Week 10):

• Citation share moved from 20% to 37%
• Brand mentioned (cited or named) in 51% of tracked answers, up from 19%
• The COD-reconciliation explainer became a regularly cited source in its own right

Phase 4 — Measurement and Compounding (Weeks 8–14)

The final phase turned the engagement from a project into a system the team could run themselves.

Attributing AI-sourced demand. We instrumented tracking for the demand AI visibility was actually generating — monitoring branded-search lift, “how did you hear about us” survey responses on the trial form, and referral paths from AI surfaces — and built a shared dashboard so the head of growth could report AI-sourced pipeline to the board in the same breath as paid and organic.

Citation-monitoring cadence. The weekly query-set scoring from Phase 1 became a permanent operating rhythm. When a citation dropped, the team knew within a week and could restructure the relevant page before the loss compounded — important, because answer-engine results shift faster than classic rankings and a lost citation rarely recovers on its own.

Compounding loop. As more pages were restructured and the COD-reconciliation explainer accumulated authority, new citations came faster and with less effort per query — the same dynamic that makes classic SEO compound, applied to answer engines.

Final Results at 90 Days

Metric	Before	After	Change
Priority queries cited in AI answers	7%	41%	+34 pts
Brand mentioned (cited or named) in answers	19%	51%	+32 pts
Non-branded organic clicks (classic search)	Baseline	+38%	Compounding
AI-sourced trial signups	Untracked	2.6x baseline	Instrumented
Branded search volume	Baseline	+31%	Recall effect
Product pages with extractable answers	8 of 55	51 of 55	+43 pages

These are illustrative outcome ranges, built from the patterns we see across Pakistani vertical SaaS companies, not audited third-party figures. They exist to help a buyer sanity-check whether this kind of engagement fits their situation.

What Made This Work

1. Measurement preceded execution. The single most important move was building the citation baseline before touching any content. Until the company could see it was cited 7% of the time, AI visibility felt like a vague threat rather than a tractable problem with a scoreboard.
2. Answer-first beat answer-adjacent. The biggest citation gains came from restructuring existing product and integration pages, not from publishing net-new content. Pages that already ranked well classically but were written as feature lists jumped in citation share the moment they led with a clean, extractable answer.
3. Access was a silent tax. A meaningful share of the brand’s invisibility had nothing to do with content quality — AI crawlers were being blocked at the edge. Fixing crawl access was a one-week task with outsized returns, and it is the most common hidden defect in Pakistani SaaS stacks we audit.
4. A single source-of-truth problem page carried a cluster. The COD-reconciliation explainer did work no international tool could do, and once models trusted it, citations bled into adjacent commercial queries. Owning one genuinely hard, local problem beats ten generic feature pages.
5. Neutral comparison content out-pulled promotional content. Pages that honestly compared the product against competitors — including where competitors were stronger — were cited far more often than pages that only argued for the brand. Answer engines penalise self-serving pages and reward comprehensive ones.
6. Classic SEO and answer-engine optimisation reinforced each other. The team treated this as a fork — invest in GEO or invest in SEO. In practice the same answer-first structure, the same schema, and the same authoritative explainers moved both rankings and citations. Almost nothing in this engagement traded off classic search performance; the +38% non-branded organic lift came from the same edits that won citations.

What Teams Can Apply

For Pakistani SaaS and tech companies that suspect they are invisible in AI answers:

1. Measure first. Pick 30 to 60 priority commercial queries, run them weekly against the major AI surfaces, and score citation share. You cannot manage what you have not baselined, and the number is almost always lower than the team assumes.
2. Make your existing pages extractable. Before writing anything new, rebuild your top product and integration pages so the lead answer to the buyer’s question sits in the first 60 words, supported by schema. This is the highest-return, lowest-effort move.
3. Open crawl access deliberately. Check server logs for AI crawler response codes. If you are returning 403 or 429 to the models generating the answers your buyers read, no amount of content work will compensate.
4. Own one genuinely hard local problem. Find the workflow your international competitors cannot describe — COD reconciliation, local compliance, regional logistics — and build the definitive explainer. Source-of-truth problem pages earn citations that cascade into commercial queries.
5. Instrument the demand. Track branded-search lift and “how did you hear about us” responses so AI-sourced pipeline becomes visible. What gets measured gets budgeted.

WeProms Digital has applied this framework across Pakistani vertical SaaS, fintech, developer-tools, and B2B service businesses. The query sets, content architecture, and authority tactics change with each vertical — the measurement-first, answer-first, access-first sequence stays consistent.