Disha Pai · Focused operating brief

Disha Pai - Saudi market activation plan

Concentrate Saudi audience growth, authority content, and relationship-led outreach around measurable qualified conversations and mandates.
Prepared 2026-09-18Owner BAMF / Houston GoldenDisha PaiDisha PaiRuya RecruitmentSource-backed · approval-gated
Saudi campaign contacts4,346Fresh BAMF Connect snapshot
Accepted2,073Saudi-targeted campaigns
Replies71Saudi-targeted campaigns
Explicit Saudi fit1,060Deterministic location and role layer
01

The plan in one sentence

Concentrate Disha's work on a Saudi-specific relationship and content loop: identify the right hiring and business leaders, use Saudi-relevant authority content to earn context, and move qualified responses toward the 90-day conversion event Disha chooses.

02

What the full report establishes

  • 11,025 total network connections.
  • 4,346 Saudi-targeted campaign contacts.
  • 2,073 accepted connections and 71 replies across the Saudi-targeted campaign portfolio.
  • 1,060 records match the explicit Saudi location and role layer; 65 replies sit inside the deterministic reporting view.
  • The current portfolio contains 2,073 accepted Saudi-targeted connections and 71 replies. The explicit 30-day timestamp view is a separate coverage window; when it is incomplete or empty, it is reported as unavailable/observed-in-window rather than as proof that there are no leads.

The full report is the evidence layer. Geographic intent is not proof of impressions, followers, or engagement from Saudi Arabia; those remain explicitly unknown unless a live source proves them.

Example ICP signals already present

Company / ecosystemPublic role signalWhy it belongs in review
Future Careers Middle EastExecutive search / Saudi marketDirect ecosystem and referral relevance.
MeshChief AI, Product and Technology OfficerSenior technology leadership with a clear Saudi-market signal.
QiddiyaWorkplace / Saudi developmentLarge Saudi transformation ecosystem with talent and leadership relevance.
Ministry of Tourism of Saudi ArabiaGovernance leadershipSenior public-sector leadership signal; requires careful, relationship-led outreach.

These are redacted company/role examples, not permission to contact or evidence of current buying intent. The first action is to review the strongest existing replies and accepted connections, then approve the exact conversation objective for each segment.

03

Priority segments

  1. Saudi-based founders and CEOs.
  2. CHROs, Chief People Officers, Talent Acquisition, and senior People leaders.
  3. Functional executives sponsoring leadership hiring.
  4. Carefully qualified referral partners.

Segment by Riyadh, Makkah, Eastern Province, and Saudi-wide records with an explicit location signal. Do not infer geography from a name, company, or copy alone. Exclude agencies and competitors unless an explicit partnership hypothesis is approved.

04

First campaign architecture for approval

CampaignAudienceJob to be done
Warm Saudi conversationsAccepted or replied Saudi-relevant peopleRe-open a real conversation around current hiring or leadership pressure.
Executive-hiring decision makersSaudi leaders with direct people/hiring influenceEstablish a credible, market-specific exchange.
Founder/operator relationshipsSaudi founders and operatorsSurface strategic recruiting and leadership pain points.
Referral partnersCarefully reviewed ecosystem contactsCreate a high-trust introduction path.

No sequence launches until Disha/Houston approves the segment, copy, and measurement owner.

05

Verified first source list

The first new source search is verified in Disha's live Multilogin LinkedIn session:

  • Saudi Arabia.
  • Second-degree relationships.
  • Talent Acquisition, Human Resources, CHRO, or HR Director keyword signal.
  • Visible Saudi-based HR and talent results.

Open the verified LinkedIn search ↗

The BAMF Connect Connector shell Disha - Saudi Growth - HR & Talent Leaders - Review Gate - v1 remains draft and inactive. The intended connection request is blank; no follow-up copy has been saved or launched. After copy/KPI approval and provider access recovery, import this search with a 30-day refresh and bind it to the dormant shell.

06

Materialized warm-conversation tranche

The current client-scoped relationship data contains 62 Saudi-relevant people who have already replied. A bounded first 40-person warm review tranche is now staged privately for approval; all 40 have a reply signal, so this is a conversation-recovery lane rather than a cold-volume list.

  • Available warm Saudi replies: 62.
  • First review tranche: 40.
  • Reply signal in the tranche: 40 of 40.
  • Private review artifact: tmp/client-campaign-staging/2026-09-17/disha-saudi-warm-40.json.

This warm tranche should be reviewed separately from the new second-degree Connector search. Start with the warm conversations, then use the verified search to replenish the audience after the message angle and conversion event are approved.

07

Message and content spine

Lead with one credible market or company cue, then ask one specific leadership/talent question. Invite a short exchange only after relevance is established. Avoid generic “we help companies hire” language.

Content support should be Saudi executive-search authority first, then relationship-led recruiting/operator insights, founder/personal-photo observations, and only approved personal leadership stories. The prior 55/20/15/10 mix is a working hypothesis, not an approved commitment.

08

This week

  • BAMF: reauthenticate BAMF Connect and inspect current campaign, filter, prospect, and delivery state before any mutation.
  • Disha/Houston: define the single 90-day conversion event and numeric target: qualified Saudi conversation, call, referral, or mandate.
  • BAMF: review and segment the staged 40-person warm tranche, then prepare-not send-the approved follow-up sequence.
  • Disha: provide approved Saudi market observations and source material for the next content cycle.
09

Decision gates

  • No campaign activation, external outreach, or WhatsApp automation until the conversion target, approval owner, and live provider state are confirmed.
  • Track sends, accepts, replies, qualified Saudi conversations, meetings, content approvals, and geography coverage separately.
  • WhatsApp remains an opt-in, governed planning channel-not an unapproved execution path.
  • Do not activate the new Saudi HR/Talent lane until Houston and Disha approve the blank connection request, follow-up sequence, and one 90-day conversion event.
10

Evidence enrichment: Saudi content, outreach, and audience intelligence

Provenance. This section reconciles the canonical Aug. 12 Fireflies call (real meeting ends at 01:01:07; later audio is unrelated), matching Notion notes/strategy pages, the review-gated Gmail draft, the Sept. 17 Saudi staging plan, and the Sept. 18 report artifact. Primary ledger: project-context/plans/2026-08-13-disha-call-action-plan/source-ledger.md; operating boundary: project-context/plans/2026-08-13-disha-call-action-plan/disha-operations.md. It is planning evidence, not a client approval or send receipt.

Saudi content strategy backlog

Run a source-led loop of: (1) Saudi executive-search authority, (2) relationship-led recruiting/operator observations, (3) founder and candid/photo-led moments, and (4) optional personal leadership or motherhood stories only when Disha opts in. Use specific incident → tension → what Disha noticed → useful conclusion; request 3-5 approved photos or a voice note with date/place, context, significance, audience, and off-limits details. Keep the prior 55/20/15/10 allocation as a test hypothesis only.

Keep these additional ideas in the reviewed backlog, not as commitments: buyer-versus-candidate lane allocation; Ruya/company-page cadence; Google/owned-media discoverability; relevant Saudi/MENA engagement groups; an older mobile-campaign concept; and a one-variable Arabic profile-language experiment. The Arabic test requires a research basis, fixed window, baseline, and one success metric. Do not let family content displace Saudi recruiting expertise.

Saudi outreach strategy backlog

Sequence the four lanes already approved for review: warm accepted/replied Saudi relationships; Saudi executive-hiring decision makers; founders/operators; and carefully qualified referral partners. Add the verified second-degree HR/Talent search only after the blank connection request, follow-up copy, KPI owner, and provider state are reviewed. Start with the private 40-person warm-reply tranche, keep it separate from net-new search, and draft-not send-follow-ups. Every candidate needs explicit location, role/ICP fit, relationship signal, relevance cue, and a named conversation objective.

WhatsApp BAMF Agent alpha/beta offer (planning only)

  • Alpha - governed source capture: opt-in Disha/Houston conversation for approved photos, voice notes, Saudi observations, and interview scheduling; identity/client binding, quiet hours, media retention, and submit now confirmation are required. General conversation must not create Notion/Slack writes.
  • Beta - confirmed content-request workflow: after the Houston pilot and provider checks, a Disha-confirmed request may create one client-scoped intake, first-person draft, two image options, Notion assignment, and an Edits Required receipt. This is an approval workflow, not auto-publishing or a consumer WhatsApp group capability. The Sept. 8 Disha receipt proves this bounded path, not broad automation.

Enhanced audience request and measurement contract

Request a read-only, source-labeled view covering profile demographics (location, industry, title, seniority, company, company size), per-post demographics, profile visitors, follower origin, engaged-profile cohorts, and content impressions/reach. Capture 24h, 48h, 72h, 7-day, then monthly/frozen checkpoints where the provider supports them. Keep impression geography, follower geography, engager geography, profile visitors, and campaign targeting as separate dimensions; unavailable or partial fields remain unknown/pending, never zero. Named visitors are permissioned relationship evidence, not aggregate demographics. Any impression-share multiplication must be labeled derived_estimated_impressions, never unique reach.

Approval gates and next evidence

Before any external action, Disha/Houston must approve the 90-day conversion event/target, buyer-versus-candidate allocation, content mix, Arabic experiment, message copy, WhatsApp opt-in/binding, retention/quiet-hours policy, and reporting cadence. BAMF must revalidate live campaign/provider state, retain source timestamps and coverage, and preserve the unsent Gmail draft boundary. The Disha audience canary previously returned DEMOGRAPHICS_NOT_AVAILABLE; do not claim Saudi demographic or impression proof until a fresh non-empty authorized source is captured.