Every client's speaker programs, run by its SOP.

Right at every step, ready for every report.

For medical communications (medcomm) agencies: Pharmagin checks each client's SOP at every step and keeps one record per HCP, so the Open Payments export is ready the day a program closes. Our team sets it up and stays behind yours.

  • 20,000+speaker programs managed
  • Since 2010building speaker-program technology
Events › First-Line Immunotherapy in Metastatic NSCLCLive Speaker Program · Dallas, TXClose Event
  1. ✓ Draft
  2. ✓ Pending approval
  3. ✓ Approved
  4. ✓ Execute
  5. Completed
  6. Closed

Speakers, checked against this client’s SOP

  • Tomas Vargas, MD✓ Contract✓ Topic✓ Cap
  • Elena Vasquez, MD✓ Contract✓ Topic✕ Over capCan’t be added to this program

Event Closure Checklist

  • ✓ Attendees matched34 / 34
  • ✓ Actual spend in9 / 9
  • ✓ Meal cost allocatedDone

Ready to close · Open Payments export ready

Transcript · Every client's speaker programs, run by its SOP · 1:35

Your agency runs speaker programs for three pharma clients. Each has its own SOP, and the same HCP looks different in the CRM, the target list, and the sign-in sheet. Your planners check the rules from memory and fix the data by hand. Misses surface at close-out, and the Open Payments data gets rebuilt at year end. Then it's a question about your agency. Pharmagin runs each client's programs by its SOP, from request to report. Each client gets its own workspace and its own rules. Pharmagin checks each one at the step it applies. Over the cap, a speaker can't be added. Every HCP is one record. Pharmagin suggests the match, and a planner confirms it. A program can't close until its attendees and spend are right. So the spend per HCP is ready for Open Payments, and the attendance is already in the client's CRM. Our team maps each client's SOP with your planners, connects its systems, and stays after launch. Your planners stop carrying every client's SOP. Your client gets answers from the record, and your agency stays the one the client knows. To see this on one of your client's programs, book a program walkthrough at pharmagin.com.

Selected organizations and brands Pharmagin has supported.

Aclaris Therapeutics
ELZONRIS
Somatuline Depot
Veltassa
Relypsa
Ortho Dermatologics
Dysport
Salix Pharmaceuticals
Biofrontera
Bausch Health
VARUBI
XEOMIN
ONIVYDE
DEFINITY
ORSERDU
Why it's hard

Three clients. Three SOPs. One team keeping them apart.

  • What happens

    Each client's standard operating procedure (SOP) sets its own rules at every step, and the same healthcare professional (HCP) looks different in the CRM, the target list, and the sign-in sheet.

  • Who carries it

    Planners check the rules from memory and match HCPs by hand, program after program.

  • What it costs

    Misses surface at close-out or in the client's compliance review, and Open Payments data gets rebuilt in Excel at year end.

Each client's rules

Each client's SOP, checked at every step.

From the rep's request to program night, every step follows the rules of the client it is for.

ProblemThe SOP lives in a PDF.

Each rule is checked at the step it applies.

Dates inside the lead time can't be picked, and a speaker over the cap can't be added. The client decides how strict each rule is.

The program start date picker: days inside the client's lead time are greyed out, and the first selectable date is 21 days from today.
21-day lead timeSet in this client's workspace

ProblemEvery client is different.

Each client gets its own workspace.

One sign-in reaches every client workspace your team supports. Switch, and the approvers, speaker tiers, and limits switch with it.

The workspace switcher open in the top bar, listing the agency's own workspace and two pharma client workspaces.
One record per HCP

Each step leaves the right record.

Who attended, who they are, and what they received, kept from registration to close.

ProblemOne HCP, three records.

Every HCP is one record.

Each registration is matched to one HCP from the client's CRM, its target list, or the NPI registry. Pharmagin suggests the match and a planner confirms it, so the attendance limit counts the right person.

One HCP's record on its Events tab: three programs, two attended and one registered, each reconciled to this one record.

ProblemWalk-ins get typed in days later, and programs close with gaps.

A program can't close until it's right.

HCPs sign in on their own phones, and walk-ins are added on the spot. Close waits until every attendee is matched, actual spend is in, and each HCP's share of the meal is allocated.

A completed program that cannot close yet: the one item left is the spend allocation, and the closure checklist shows attendee reconciliation and expenses complete.

ProblemFinance rebuilds spend per HCP in a spreadsheet at year end.

Spend per HCP, ready the day the program closes.

Aggregate Spend shows what each HCP received, with a reason on every excluded row. Fix an HCP's record once, and every row follows.

Aggregate spend for the program year: reportable spend across 308 recipients, and excluded spend for 9 recipients that cannot be reported yet because they have no NPI.
Sent to Veeva Vault CRMAttendance, as it changes

ProblemThe brand team can't tell how a program went.

See how every program went.

Attendance, walk-in, and repeat-attendee rates cover every completed program. Slice them by format, specialty, or territory.

Attendance and Engagement for the program year: four rates across the completed programs, with attendance by format below.

For your client’s compliance team

Every exception has a name and a reason.

Each check, approval, and override stays with the program, with a name and a time.

  • Every override records who made it and why.
  • A reopened program keeps its history.
  • Each rule maps to what OIG looks for.
See the OIG crosswalk
Change history for one closed program: expense corrections, the close, the spend allocation, and the post-program certification, each with a name and a time.
The team behind your agency

Our team behind yours.

We map each client's SOP with your planners. Our CRM team works with the client's IT to connect Veeva Vault CRM, Veeva CRM, or Salesforce, tested before go-live. After launch, we stay on to support your team. You keep the client.

Wherever you’re starting from

Already on a vendor?

Move one client first, and keep the rest where they are until you're ready.

How a move works

Pitching a new client?

Show them a working platform with their own rules in it, before the contract is signed.

How agencies use Pharmagin

Optional AI

The assistant prepares. A planner decides.

Turn it on, and the assistant summarizes where a program stands, answers your team’s questions, checks speakers, and reads photographed sign-in sheets. A planner confirms every change. It stays off until it is turned on for a client.

How Pharmagin uses AI
The optional assistant's attendance proposal from a photographed sign-in sheet: the roster rows it proposes to mark attended, each noting that a signature was found but the identity is not verified, waiting for a person to confirm.
Confirmed by S. AbernathyAttendance changes applied
Next step

Show us a program that gave your team trouble.

We'll walk through how it would run on Pharmagin: the client's rules, the approvals, and the close-out.