ARIYA CONTENT WIZARD

Content that knows
your brand plan

Any model can write about your product. None of them know your key messages, your personas, your approved claims or what your MLR team will send back. Content Wizard does, because that context is loaded into it. It creates and adapts assets inside your brand, with every statement referenced to the source it came from.

Book a walkthrough See it run on your own brand →
Content Wizard grounding assets in brand context with referenced sources

THE PROBLEM

Fluent is not the same as approvable

The generic tools produce clean drafts in seconds. Then the work starts. Someone checks it against the brand plan. Someone asks where a claim came from. Someone rewrites it for the persona it was supposed to be written for. Someone sends it back because that message was never approved for this market. The draft was free. Everything after it was not.

No brand context

The model has never seen your brand plan, your messaging framework or your segmentation. It writes for nobody in particular.

No traceability

A statement with no source behind it cannot go through review, however well written it is.

Volume keeps arriving

Global material, congress output, webinars. Local teams rebuild it by hand, channel by channel, and output is capped by their hours.

WHAT IT DOES

Two jobs, one context

Content Wizard does both halves of the work. It creates assets from a brief, and it adapts material you already have. The difference between it and a general purpose model is not the writing. It is that both jobs run inside your brand context, so what comes out is already pointed at the right audience, built on approved ground, and carrying its sources.

Create
Start from a brief

Start from a brief, a claim, an indication or a persona. Rep-triggered emails, DHPC (Direct Healthcare Professional Communication) letters, digital collaterals, web content, one-pagers. From scratch does not mean from nothing: the output is grounded in your approved evidence and written to your messaging.

Adapt
Start from a source

Start from a source you already have. A congress booklet, a webinar recording, an approved email. One upload becomes a full local package across every channel that needs it.

WHY THE OUTPUT IS USABLE

We load the brand before we write a word

This is the part that decides whether the content survives review. Before generation, Content Wizard is set up with the material your team already works from. The model does not infer your strategy. It is given it.

What goes in
Your brand context
Brand plan and strategic priorities Key messages and the messaging framework Target personas and segmentation Approved claims and the source documents behind them Brand and design templates MLR guidelines and market specific rules
What comes out
Assets ready for review
Assets written to the right message for the right persona Every statement referenced back to the document it came from Output inside your templates, ready for review rather than ready for rewriting

Ask a general model for a claim and you get a sentence. Ask Content Wizard and you get the sentence and the page it came from.

HOW TIGHT YOU WANT IT

Generated from approved sources,
or assembled from approved messages

How much freedom the system gets is your decision, not ours. Both modes run on the same context.

Source grounded

The system writes new copy, grounded in your approved source documents, with a reference on every claim. Use it where you need new assets and the review chain can handle new copy.

Pre-approved only

The system works only from your library of pre-approved message modules. It selects, sequences and localizes them, and writes nothing outside them. Use it where review capacity is the constraint. Approve the module once, reuse it across every channel and market it fits.

Most teams start in pre-approved mode for promotional material and open up from there.

HOW IT WORKS

Five steps, the same flow every time

01

Source

Upload the material, or start from a brief.

02

Configure

Channels, language, personas, tone, mode.

03

Generate

Draft the assets with references attached.

04

Review

Medical, legal and regulatory check, with human approval.

05

Activate

Push to your systems.

One booklet becomes a full package, with MLR review and a source language preview on every asset.

WHERE IT IS USED

The assets teams produce with it

Rep-triggered email

One approved email becomes three persona versions. Same design, tailored copy. Or a new one, written from approved modules, in minutes rather than an agency cycle.

Congress report

One English booklet becomes a local summary, web articles, emails and a rep-triggered email.

Webinar follow-up

A recording becomes a summary, a one-pager and two follow-up emails, one for participants and one for no-shows.

DHPC letters

Direct Healthcare Professional Communications, generated from the approved source material with minimal input, in the required structure.

Digital collaterals

Approved brand content turned into flyers, ads, web articles and campaign assets that stay inside brand.

ARIYA

Same platform, different jobs

Ariya is built for the decisions: what the evidence supports and what you should do about it. Content Wizard is built for the output: turning brand strategy and approved material into what each channel needs. Both run on the same knowledge base, the same governance and the same referencing.

Explore Ariya →

Common questions

Both. From scratch means without a source document to work from. It does not mean without context: the output is still written to your key messages and grounded in your approved evidence.

Two ways, and you choose. Source grounded mode writes only from your approved documents and attaches a reference to each claim. Pre-approved mode writes nothing outside your library of approved message modules.

The brand plan, key messages, personas, approved claims and their source documents, your templates and your MLR guidelines. Most of it already exists.

It removes the repetitive work: variants, localization, persona versions, assembly. Agencies stay useful where original creative is needed.

The engine is language agnostic. Deployments are configured per market, with the source language kept as a preview on every asset for review.

Veeva PromoMats two way, OCE and comparable email tools, and HCP portals. Others are scoped per deployment.

12 weeks to a live first use case in the first brand and market. Following markets are faster because the core is already built.

Want to see it in action?

The fastest way to judge this is to watch it write inside your own context, on material you already know.

Book a walkthrough Talk to the phamax team →