Expansion Revenue Email Case Study in Pakistan

The Client

A Karachi-based B2B SaaS company selling invoicing and receivables software to Pakistani SMEs — traders, distributors, and small manufacturers, the kind of businesses that cluster around Karachi’s commercial hubs and keep their accountants on WhatsApp retainer. The platform let a business issue branded invoices, track who owed what, chase payments with scheduled reminders, and reconcile cash flow across branches. By the time of the engagement it had reached roughly PKR 78M in annual recurring revenue across about 2,100 paid workspaces, at an average of around PKR 3,100 per workspace per month across three tiers, with add-ons for multi-branch access and recurring billing.

The company is described here as an illustrative composite of the engagement patterns we see across Pakistani B2B SaaS accounts at this stage, not a named client. The dynamics will be familiar to anyone who has run growth at a subscription software business in this market.

Growth had been carried almost entirely by new logos. A two-person inside sales team closed referrals and demo requests, a 14-day free trial fed self-serve signups, and word of mouth among Karachi trading communities kept the top of the funnel healthy. But the revenue that was already inside the customer base — seats added, tier upgrades, add-on modules switched on — barely moved. Month after month, workspaces signed up, settled on a tier, and stayed there until they churned or someone happened to call.

The product team could see the demand hiding in plain sight. Workspaces hitting their monthly invoice quota and quietly trimming their invoicing at month-end. Teams inviting accountants and branch managers beyond their seat allowance. Businesses attempting multi-branch features on single-branch plans. Roughly 130 of these usage-ceiling events surfaced every month, and almost none of them became an upgrade conversation. The leadership team engaged WeProms Digital to install the kind of email marketing automation lifecycle flows that convert product behaviour into expansion revenue automatically — and to make expansion a channel the company could forecast instead of hope for.

The Problem

Four gaps were capping expansion revenue every single month:

• Product data and marketing data never met. Sixteen product events — invoices sent, clients added, seat invitations, feature-ceiling hits, reminder-schedule usage — lived in a product analytics tool with no path to the email platform. The marketing database knew plan and renewal date, but nothing about behaviour. Every send was therefore a guess aimed at a whole contact file rather than a message tied to what a workspace had done that week.
• The upgrade message reached the wrong person. The occasional expansion email went to the most active user in a workspace — usually the person issuing invoices. In Pakistani SMEs that person is frequently an employee or an outside accountant; the person who approves software spend is the owner. Sends went to users who could not buy and rarely forwarded.
• One newsletter carried the whole programme. A single monthly send to ~11,400 contacts, clicking at 1.9%, with no segmentation, no lifecycle, and no attribution. It could not fail conspicuously because it was never really expected to do anything.
• Deliverability was quietly capped. Transactional invoice emails — around 48,000 a month — shared a domain and sending setup with the marketing newsletter. Business inboxes inside Google Workspace and Microsoft 365 treated the mixed stream with suspicion, holding measured inbox placement at 89%, with the weakest delivery on Microsoft 365 tenants where many corporate buyers sit.

The net effect: expansion added roughly PKR 310K of MRR a month and had for three consecutive quarters, while new-logo revenue grew 9% month on month. The board’s question was blunt — why is the revenue we already own the slowest-growing part of the business?

Phase 1 — Diagnosis, Data Plumbing, and Deliverability (Weeks 1–2)

No flow gets written until the signal is trustworthy and the message can land. The first two weeks were spent on foundations.

Rebuilding the contact model at workspace level. The first structural finding was that the email database was a flat list of people, while expansion happens at the workspace. A single workspace might contain an owner, two data-entry users, an external accountant, and a branch manager. We rebuilt the model so every contact carried workspace ID, plan tier, seat utilisation, invoice-quota utilisation, add-on status, and a role tag — with a designated billing owner per workspace. That last tag would prove to be one of the highest-leverage pieces of data in the entire programme.

Standing up the event pipeline. We forwarded the sixteen product events into the marketing automation platform in near real time and joined them to billing data so every event could be evaluated against entitlement. The three events that mattered most for expansion were invoice-quota utilisation (80% of monthly quota), seat invitations beyond allowance, and attempted use of gated multi-branch or recurring-billing features. Each got a versioned definition reviewed monthly.

Separating the mail streams. We moved marketing sends to an authenticated subdomain (SPF, DKIM, DMARC), leaving transactional invoice mail on the primary domain where its deliverability actually protected revenue collection. Seed-list testing against Pakistani business inboxes gave a true baseline: 89% placement, worst on Microsoft 365. By the end of the phase, placement on the marketing stream had climbed to 94% and kept rising as the fresh domain accumulated engagement only from people who had opted in.

Phase 1 closeout:

Diagnostic	Before	End of week 2
Product events reaching email platform	0	16, near real time
Contact model	Flat contact list	Workspace-level with roles and billing owner
Expansion signal definitions	Informal	3 versioned, scored triggers
Mail streams	Shared domain	Marketing on authenticated subdomain
Inbox placement (seed test)	89%	94%, trending to 97%

Phase 2 — Build the Six Expansion Flows (Weeks 3–5)

With clean signal flowing, we built coverage: an automated, behaviour-triggered response attached to every expansion-relevant moment in the product.

Invoice-quota ceiling flow (3 emails). The headline driver. When a workspace crossed 80% of its monthly invoice quota, the billing owner received an email showing their actual usage — invoices sent this month, quota remaining, projected overrun date — with the next tier’s quota and price, and a one-click upgrade path. Because Pakistani trading businesses invoice heaviest in the last week of the month, the trigger naturally clustered at the moment the pain was real and the owner was already thinking about cash flow. The email quoted the workspace’s own numbers, never a generic pitch.

Seat expansion flow (2 emails). When seat invitations hit the allowance, the billing owner got a short, direct message: who was invited, why adding a seat cost less than the workaround, priced at the per-seat rate. Roman Urdu subject lines outperformed English on owners by a wide margin here, which testing in Phase 3 confirmed.

Add-on module trial flow (2 emails). When a workspace attempted a gated feature — multi-branch access or recurring billing — the flow offered a 14-day trial of the add-on rather than an immediate sale. Trial-first offers respect how cautiously Pakistani SMEs approve new software spend; the buyer gets to justify the line item with two weeks of evidence rather than a promise. This flow family follows the same sequencing logic WeProms uses across broader cross-sell and upsell campaign systems, where the ask is matched to demonstrated behaviour instead of campaign calendar.

Billing-owner usage digest (monthly). A short monthly summary per workspace — invoices issued, payments collected, overdue amounts reduced — that earns the open by being genuinely useful, and carries a single upgrade line relevant to that workspace’s usage pattern. This flow existed to build trust and reply-worthy familiarity; its job was to make the other five flows feel expected rather than promotional.

Stalled-workspace reactivation (2 emails). Workspaces whose invoice volume dropped for three consecutive weeks — usually a sign of churn risk or a lapsed trial of a higher tier — received a check-in offering a receivables health review. Expansion and retention are the same motion at this stage of an account.

Renewal-window upgrade flow (2 emails). Thirty days before annual renewal, billing owners received a year-in-review usage summary with a right-sized plan recommendation. Several workspaces discovered they were paying for more quota than they used while lacking seats they needed — right-sizing at renewal converted gratitude into upgrades.

Phase 2 closeout:

Flow	Trigger	Early signal (first fortnight live)
Invoice-quota ceiling	80% of monthly quota	First tier upgrades attributed
Seat expansion	Seat invites at allowance	Per-seat orders from owner inbox
Add-on trial	Gated feature attempt	Trial starts same session as trigger
Usage digest	Monthly, per workspace	Reply rate from owners, not users
Stalled reactivation	3-week volume drop	Recovered workspaces re-invoicing
Renewal upgrade	30 days pre-renewal	Right-sizing conversations opened

Phase 3 — Optimize Offers, Personas, and Send Logic (Weeks 4–8)

Once flows carried volume, optimisation shifted from coverage to conversion. This phase overlapped the tail of Phase 2 — each flow entered testing as soon as it carried enough volume to read.

Persona-targeted sends. The single highest-impact change: retargeting upgrade sends from the most active user to the tagged billing owner. Early seat-flow sends to active users performed weakly — opens without action, since employees rarely escalate software purchases. Sending to the owner, referencing the employee’s actual invitation attempt, lifted seat-flow conversion sharply. Pakistani SMEs concentrate purchase authority in one person; the data model had to respect that.

Bilingual subject-line testing. Owners and accountants read email differently. Across structured tests, Roman Urdu subject lines beat English for owner-targeted flows (the seat flow’s advantage was the largest), while English won for accountant-facing sends. Language, sender identity (founder versus product team), and send time (evening sends for owners, mid-morning for accountants) were all tested to pre-decided sample sizes before winners were locked.

Offer sequencing by readiness. Not every trigger earned an upgrade ask. A first quota-ceiling hit offered a low-friction quota top-up; a repeated hit offered the tier upgrade; a gated-feature attempt offered the trial. Matching the ask to demonstrated readiness — rather than always pitching the biggest change — reduced deferrals and unsubscribes while lifting total conversion.

Sales handoff for large signals. Workspaces above six seats showing any expansion signal created a CRM task for the two-person sales team, with the triggering usage summary attached. Email worked the long tail of ~2,060 previously untouched workspaces; humans closed the biggest opportunities. This split kept the programme an ally of sales rather than a competitor for credit.

Suppression and fatigue rules. Global suppression covered workspaces in open support tickets, mid-trial, or already upgraded — nothing erodes an expansion programme faster than asking a workspace that upgraded last week.

Phase 3 closeout:

Metric	Start of phase	End of week 8
Expansion MRR added (monthly)	PKR 318K	PKR 361K
Email-sourced share of expansion	13%	21%
Upgrade events (monthly)	61	74
Lifecycle flow CTR	2.8%	4.6%

Phase 4 — Attribute, Compound, and Hand Over (Weeks 8–12)

The final phase made the engine durable and defensible.

Source-of-expansion attribution. A shared dashboard attributed every upgrade event to its source — quota-ceiling flow, seat flow, add-on trial, renewal flow, sales-led, or organic — alongside flow-level CTR, trial conversion, and deliverability. This replaced the leadership team’s vague sense that expansion felt better with a defensible answer to which flow earned which rupee, and it fed expansion into revenue forecasting as a planned line rather than a rounding error.

Model re-weighting on outcome data. Weeks of results re-ranked the signals. Invoice-quota proximity proved the strongest expansion predictor — workspaces hitting 80% of quota upgraded at more than triple the base rate. Seat-limit signals were the second strongest. Raw login frequency, which had looked compelling on paper, was nearly worthless as a predictor and was demoted to a supporting attribute. The flows kept firing on what actually converted.

Iterating the winners. The monthly review cadence retired the weakest variant of each flow, refreshed fatigued creative, and added one new test. The digest earned a payments-collected chart in response to owner replies; the quota flow gained a projected-overrun date after it measurably lifted urgency.

Handover. Trigger definitions, suppression rules, the scoring model, and the review cadence were documented and handed to the in-house marketer with two training sessions, so the programme runs without depending on an agency.

Final Results at 90 Days

Metric	Before	At 90 days	Change
Expansion MRR added (monthly)	PKR 310K	PKR 394K	+27%
Email-sourced share of expansion	11%	26%	+15 pts
Upgrade events (monthly)	58	83	+43%
Workspaces touched per quarter	~40	1,340+	expansion coverage at scale
Lifecycle flow CTR	1.9%	5.4%	+185%
B2B inbox placement	89%	97%	+8 pts
Add-on trial-to-paid conversion	—	24%	new channel

Every number traces to a phase: placement and data plumbing came from Phase 1, coverage and the first attributed upgrades from Phase 2, conversion gains from Phase 3’s persona and offer work, and the durable attribution plus compounding lift from Phase 4. The company’s own summary was that expansion had moved from the slowest-growing revenue line to a forecastable channel — and the 27% lift held through the following quarter as the digest and renewal flows matured.

What Made This Work

1. Signal before send. Plumbing sixteen product events into the email platform before writing a single flow meant every message fired on what a workspace actually did — not on a calendar. Most lifecycle programmes fail because they skip this step and send educated guesses to a whole list.
2. The billing owner is the buyer. Retargeting upgrade sends from the most active user to the tagged owner matched how Pakistani SMEs actually purchase: authority concentrated in one person. This one change did more for seat-flow conversion than any copy test.
3. Triggers timed to the business rhythm. Quota ceilings cluster in the last week of the month, when trading businesses are invoicing hardest and already thinking about cash flow. The flow arrived at the moment of felt pain, which is why it out-converted every other trigger.
4. Trial-first offers for cautious spenders. Offering a 14-day add-on trial instead of an immediate sale respected the internal justification cycle most Pakistani SME buyers run software purchases through — and converted 24% of trials to paid.
5. Attribution made the result real. The source-of-expansion dashboard turned a felt improvement into a defensible 26% share that leadership could put in front of the board, which is what protected the programme’s budget.

What Teams Can Apply

For Pakistani SaaS companies that want expansion to pull its weight:

1. Connect product events to your email platform first. If your email tool cannot see what a workspace did this week, you are running a newsletter, not lifecycle marketing. Invoice-quota utilisation, seat-limit proximity, and gated-feature attempts are the three highest-leverage triggers for SMB SaaS in this market.
2. Tag a billing owner per account and send upgrade emails there. The most active user is usually not the buyer. One role tag in your contact model will outperform months of subject-line testing.
3. Match the ask to readiness. First ceiling hit: offer a top-up. Repeated hit: offer the tier. Feature attempt: offer the trial. Sequenced asks convert better than always pitching the upgrade.
4. Separate transactional and marketing mail. If your product sends invoices, receipts, or reminders from the same domain as your newsletter, deliverability for both suffers — and in a market where buyers sit inside Workspace and Microsoft 365, placement is revenue.
5. Hand the biggest signals to a human. Automate the long tail, but let the system create the CRM task with usage attached. Expansion programmes scale further when sales trusts the signals it receives.

WeProms Digital applies this framework across Pakistani B2B SaaS and subscription software companies — vertical SaaS, HR and payroll, fintech, and marketplace tools — and the wider context for that work is covered in our guide to digital marketing for SaaS. The trigger definitions, personas, and offers change with each product; the account-level, signal-first approach does not.