Relationship Status
Active Client
First won: Apr 27, 2026
Current Program
$85K
SpringWorks Ogsiveo Meta Campaign
Owner / Lead
Chad Holloway
SVP, Media & Platform Partnerships
Discussion Stage
Self-Service Scope
Logistics · Integration · Pricing
Meeting Agenda · 3 Topics
PharmaForceIQ wants to discuss a self-service option. Here’s what we’re covering and what we’re prepared to answer.
2
Topic 2
Data Integration Pathways
+ inflow/outflow formats · share FIA on call
3
Topic 3
Topic 1 · Self-Service Logistics
1
Self-Service Logistics — Who Does What
Operating model · responsibilities · onboarding timeline · ongoing support
Equals 5 Owns
The data, identity, and activation infrastructure
  • NPI list ingestion + deterministic identity match (85%+ Meta, 75%+ LinkedIn)
  • Audience build, syncing to social destinations
  • EQ5 Signals Pixel + closed-loop NPI engagement tracking
  • Prescriber-Level Data (PLD) pipeline and engagement scoring
  • Identity resolution + privacy / HIPAA compliance posture
  • Platform-side technical support (engineer-to-engineer)
PharmaForceIQ Owns
The client relationship and campaign operations
  • Day-to-day campaign setup, trafficking, QA
  • Creative production, ad approvals, regulatory review
  • Client billing and end-client commercial relationship
  • Campaign pacing, optimization decisions, dashboard interpretation
  • First-line client support and reporting interpretation
  • Their own internal account management of pharma brands
Operating Model
Hybrid — EQ5 platform-as-a-service, PharmaForceIQ runs the meter
PharmaForceIQ has access to EQ5’s NPI-matching and audience-activation tech as a back-end. They keep their pharma client relationships fully white-labeled or co-branded, depending on the brand’s preference. EQ5 stays invisible to the end client unless they ask. Reporting can be branded PharmaForceIQ + Equals 5 or PharmaForceIQ-only with an EQ5 footer.

Critical: NPI list ownership and identity-resolution stay 100% with EQ5 — PharmaForceIQ does not get raw match data export. They get the activation outcome and PLD pipeline. This protects EQ5’s data asset.
Onboarding Timeline
~3 weeks from MSA signed to first live campaign
Week 1 — Spec exchange: FIA walk-through, agree on data formats and delivery mode (SFTP / API / S3). PharmaForceIQ provides their internal data model.

Week 2 — Credentials + sandbox: SFTP / API keys provisioned, sandbox NPI list round-trip tested, engagement pixel deployed on a test landing page, sample PLD file delivered.

Week 3 — First live campaign: Production launch with a small budget pilot. EQ5 engineer on standby for 48 hrs post-launch.

Ongoing: Monthly account review, quarterly capacity planning, dedicated Slack / shared Jira channel for engineer-to-engineer.
Key Constraints to Flag on the Call
1. PLD pipeline is operated by EQ5. PharmaForceIQ doesn’t run identity resolution themselves — they receive the PLD via the agreed integration pathway. This keeps the value asymmetric (we own the match; they own the workflow).

2. Multi-tenancy. PharmaForceIQ operates across multiple pharma brands. Each brand gets a logical workspace inside EQ5’s platform with isolated NPI lists and reporting. Cross-brand list leakage is prevented at the infrastructure level — relevant for compliance review.
Topic 2 · Data Integration Pathways
2
Data Integration Pathways — API · SFTP · S3 · Formats · FIA
Inflow + outflow between PharmaForceIQ and Equals 5 · we’ll share the FIA live on the call if useful
Supported Integration Pathways
All paths are bidirectional — same channel for inflow (PharmaForceIQ → EQ5) and outflow (EQ5 → PharmaForceIQ). Pick the one that fits their data stack.
Method
How It Works
Best For
Status
SFTP
Scheduled push/pull on a shared SFTP endpoint. PGP-encrypted file drops at defined intervals (hourly, daily, weekly). Each side maintains its own SSH keys.
Most common pattern for pharma clients — mature, audit-friendly, no real-time dependency.
Recommended
REST API
Authenticated REST endpoints for list submission, audience status, PLD retrieval, and engagement event streaming. OAuth 2.0 or API key with IP allowlist.
Teams running near-real-time campaign workflows or integrating EQ5 into their own SaaS / dashboard.
Supported
S3 Bucket Sync
Drop/pull files to/from a designated S3 bucket (PharmaForceIQ-owned or EQ5-owned). IAM role-based access, server-side encryption (SSE-KMS).
Teams already on AWS — cleanest pattern if PharmaForceIQ data warehouse is Redshift / Snowflake on AWS.
Supported
Snowflake Data Share
Direct Snowflake-to-Snowflake share for high-volume PLD outflow. No file movement — cross-account read-only grant.
Optional for enterprise data-warehouse integration. Adds compliance/security review.
Optional / Roadmap
Webhook
Real-time event push for engagement signals (HCP click, hot-lead trigger). HTTPS POST with HMAC signature.
Triggering downstream systems (rep activation, CRM updates) on per-HCP events.
Supported
Inflow — PharmaForceIQ → EQ5
What we ingest to launch a campaign
Required:
  • NPI target list — CSV (NPI, optional specialty, optional client-defined cohort tag)
  • Campaign parameters — brand, channels, budget, flight dates, creative URLs
  • Landing-page URL (for Signals Pixel deployment)
Optional:
  • Custom audience tags / segmentation cohorts
  • Prior-campaign suppression list
  • HCP demographic enrichment data (we’ll merge if provided)
Format options: CSV (default), JSON via API, Parquet for high-volume.
Encryption: PGP for SFTP, TLS 1.2+ for API/S3.
Outflow — EQ5 → PharmaForceIQ
What we return as identified data
Standard PLD file (every campaign):
  • NPI · specialty · city / state / DMA
  • Date / time exposed · channel · creative ID
  • Activity type (impression / click / engagement) · campaign ID
  • Aggregate impression + click counts per NPI
Engagement scoring:
  • Per-HCP engagement signal across every channel
Format options: CSV (default), JSON via API, Parquet via S3.
Cadence: Daily, weekly, or on-demand — PharmaForceIQ’s choice.
The FIA — File Integration Agreement
A two-page spec doc that locks every byte of the data exchange — we’ll walk it live on the call
The FIA is EQ5’s standard integration spec. It’s a short, dense document that defines exactly what the inflow and outflow look like for a partner so engineers on both sides can build to it with no ambiguity. It’s the single artifact that has to be agreed before week-2 of onboarding.

What the FIA defines:
  • Column-by-column field mappings (NPI, specialty, name fields, geography, identifiers, etc.)
  • Delivery cadence (real-time, hourly, daily, weekly)
  • File naming conventions + version suffixes
  • Encryption (PGP keys exchange, key rotation schedule)
  • Error handling + retry / fallback SLAs
  • Reconciliation reporting (record-count match, error-row escalation)
  • Authentication mode (SSH key, IAM role, API key, OAuth)
  • Data-retention rules + scrubbing schedule

On the call: Bring up the standard FIA template and walk through it side-by-side with PharmaForceIQ’s data engineering lead. Edits and red-lines done live cut a week off onboarding.
Topic 3 · Pricing
3
Pricing — Self-Service Rates and Tier Structure
Channel CPMs · onboarding fee · tier discounts · what’s bundled vs. billed
Social Media Channel Rates
Managed Service baseline CPM + effective CPM at each self-service tier.
Channel Match Managed
baseline
Self Service
10% off
Self Service $2M+
20% off
Self Service $3M+
25% off
Meta (Facebook / Instagram) 85% $185 $167 $148 $139
LinkedIn (Newsfeed + Audience Network) 75% $500 $450 $400 $375
LinkedIn (Newsfeed Only) 75% $950 $855 $760 $713
Self-Service Tier Structure
Self Service
Self Service
No commitment
10% off
vs. Managed CPM
  • Pay-as-you-go — no minimum
  • Any channel, any volume
  • Standard integration (SFTP)
  • Weekly PLD pipeline
Self Service
$2M+ Tier
Over $2M committed spend
20% off
Once spend threshold is met
  • $2M+ committed spend
  • Multi-brand workspaces
  • SFTP + S3 access
  • Daily PLD + webhook events
Bundled in CPM
  • NPI list ingest + deterministic identity match
  • Audience build + activation to all supported channels
  • EQ5 Signals Pixel (one-time per landing page)
  • Standard PLD file (cadence per tier)
  • Engagement scoring
  • Dashboard access (self-service portal)
  • Privacy / HIPAA compliance posture
Billed Separately / On-Demand
  • Custom FIA work beyond standard spec (T&M)
  • Custom data exports / one-off PLD pulls outside cadence
  • White-label or co-branded dashboard build (one-time)
  • Snowflake Data Share setup (optional integration)
  • Field-trigger / MSL-Ready webhook customization
The Pricing Narrative
The discount maps to the labor PharmaForceIQ takes on — campaign management, trafficking, optimization. The CPM still reflects the value of the data — the NPI match, the audience build, the PLD pipeline. That’s priced the same whether they run it or we run it.

Recommended starting position: Self Service $3M+ tier (25% off) if the spend threshold is plausible across their book within 12 months. If they want to ease in, Self Service with no commitment (10% off) lets them test scale before committing.
Next Steps
Path Forward
Right after
Share the FIA spec with PharmaForceIQ’s data engineering lead.
Shortly after
Send the SOW draft — tier and commercial terms aligned to the option PharmaForceIQ selects.
Early
Technical kickoff — Equals 5 eng + PharmaForceIQ data eng lead. Walk the FIA, exchange test credentials, define inflow + outflow fields.
Mid-onboarding
Sandbox round-trip test — PharmaForceIQ submits a sample NPI list, EQ5 returns sample PLD + engagement scoring. Both sides sign off on format and cadence.
Go-live
First production self-service campaign — engineer on standby for the first 48 hrs post-launch.
Post-launch
Joint operating review — PLD volume vs. expectation, dashboard usability, integration stability, scope for next brands.