top of page

MEDS · SOCIAL MEDIA MANAGER

A modular content system built for MEDS. — delivered simply, supported clearly.

One set of brand rules — capabilities, messaging, imagery, and motion — built so any new Reel, Story, or static post could be assembled from existing parts instead of created from scratch.

Organic follower growth in 2 months

+400%

Profile activity in

3 months

+243%

Reels published weekly

3 to 5

Shares in 3 months

+20,000

image.png

OVERVIEW

A pharmacy with no visibility problem to hide behind

MEDS needed to look and sound like a modern, trustworthy alternative to a traditional pharmacy
— not just post more often.

Challenge

  • Low visibility and engagement on social

  • Limited brand storytelling

  • Educating audiences about GLP-1s in an approachable way

Approach

Instead of producing one-off posts, built a modular system: a shared set of capabilities, messaging principles, and reusable imagery and motion templates that any format could pull from.

Execution

AI green-screen explainers, pharmacist podcast interviews, and skits tied to trending sounds — built from the same system, sustained at 3–5 Reels weekly and 2–3 daily Stories.

THE SYSTEM

Four layers, one shared set of rules

From what the brand needed to say down to how it moved on screen.

DECISION 01 - CAPABILITIES → MESSAGING

Four capabilities became four rules. Every post had to follow one.

Before any content got made, the brand's actual capabilities were distilled into messaging principles — so tone and substance stayed consistent no matter who was writing the caption or scripting the Reel.
 

Low-friction product support

A system designed to reduce friction across delivery, privacy, and communication.

Hassle-free delivery

Reliable delivery designed to minimize user effort.

Discreet packaging

Packaging designed to protect user privacy.

Text-based expert support

Expert support accessible through text-based communication.

DECISION 02 - ALTERNATE MESSAGING

Same principle, different words — built for where it would actually run

Each principle had a bank of copy variations, so content never repeated itself while staying on-message across formats, audiences, and platforms.

Remove friction
wherever possible.

Design for clarity, not speed.
Support is part of the product.

Delivery should require
minimal user effort.

Status is clear and predictable.
The product arrives without intervention.

Privacy is respected
by default.

Packaging avoids unnecessary signals.
Trust is maintained through restraint.

Support is asynchronous
and accessible.

Expert help is embedded, not external.
Users control the pace of communication.

DECISION 03  - IMAGERY → PACKAGED CONTENT

A modular imagery library, assembled into ready-to-publish posts

Product mockups and lifestyle photography were built as one reusable library — combined with the messaging system to produce finished static posts without starting a new design each time.

image.png
image.png
image.png
image.png

DECISION 04 - MOTION STORYBOARD → MOTION ASSETS

The same system, extended frame by frame for video

The packaged-content system carried directly into video: each motion piece followed the same image-zoom → blur → reveal → message → logo-lockup sequence, built from one shared asset and typography library.

image.png
image.png
image.png

From your phone, to your door

Delivered discreetly

image.png
image.png

Hero text 32 px

Delivered discreetly

Secondary text 18 px

From your phone, to your door

Alternative messaging

  • Same-day delivery

  • Discreet packaging

  • Text a pharmacist anytime

  • NYC building friendly delivery

  • From your phone, to your door

  • No long hold times

  • Skip the lines

Hero text

American Typewriter Medium · 32px

Secondary text

American Typewriter Regular · 18px

Tagline

Delivered simply, Supported clearly

VIDEO CONTENT

Made for pharmacy culture, not just pharmacy customers

Using social listening and trend-insight tools, recurring frustrations and inside jokes specific to pharmacy life were tracked before a single video got scripted — insurance back-and-forth, prior authorization delays, the small absurdities of working the counter. That research decided which trending sounds, formats, and references made it into the AI green-screen explainers, pharmacist podcast interviews, and counter-life skits.

 

Because the references came from inside the industry instead of at it, pharmacy staff and patients didn't just watch — they tagged coworkers, sent videos into their own group chats, and shared them back into the same communities they came from.

RESULTS

What the system produced once it was running consistently.

Organic follower growth in 2 months

+400%

Profile activity in

3 months

+243%

Reels published weekly

3 to 5

Shares in 3 months

+20,000

"Which platform is it on?" is daily friction

All four described the recurring experience of not knowing which launcher a game lives on. A unified searchable library with a visible platform badge on every game was the direct solution to this problem.

Aggregation is wanted but control is non-negotiable

One participant reacted negatively when a competitor auto-aggregated Xbox data without asking. Opt-in connection became the foundational design principle of the entire onboarding flow — every platform connection requires explicit user consent.

REFLECTION

"The system was the deliverable — the posts were just proof it worked."

Treating meds. like a system instead of a content calendar changed what "consistency" meant.

Once the capabilities, messaging principles, and imagery library existed as shared rules, a new format didn't need a new creative brief — it just needed someone to pull from what already existed and point it at whatever pharmacy culture was talking about that week.

 

The harder lesson was restraint. It would have been easy to let every post invent its own voice or visual rules to chase a trend. The system worked because it didn't bend for every format — three capabilities, three principles, one imagery library, one motion template. Limiting the inputs is what made scaling the outputs possible.

If I were to take this further

Document the system as an actual playbook another creator could pick up without context, build a content calendar tied to real-time pharmacy-culture trend tracking instead of ad hoc monitoring, and test whether the same modular framework holds up applied to paid media instead of organic only.

bottom of page