Tailored sales playbooks for every market, built from approved content and live in CRM
Every rep opens the right playbook for their market, built 70% faster.
See one case, screen by screen ↓A field team works across markets, products and audiences: a hospital pharmacist in Germany needs storage, preparation and ward-stock answers plus the Pflichttext; a gastroenterologist in France needs patient selection and the mentions légales. Every combination is a different playbook, and today each one is put together by hand from the content library, the product information and whatever the CRM says about the account.
That is slow, and it drifts. Modules expire or are withdrawn, product information moves to a new version, and nobody can say which live playbooks still quote the old wording. Reps fill the gaps by asking colleagues — about storage outside the fridge, samples, hospitality, use in children — rather than finding the passage in the SOP.
Estimated split for one tailored playbook, in days. The totals match the working solution’s sample dashboard: 5.4 days before agents, 1.6 days now.
Agents read the CRM account, assemble and check each playbook from approved content; the playbook owner signs.
Klinikum Rheinhafen’s drug committee meets on Oct 22, and the last call, on Sep 18, ended with a question: can Veltrimab pens be kept as ward stock at room temperature? Here is how the playbook for that meeting is built, signed and kept current, screen by screen, in the working solution.
Lena opens the solution: 146 playbooks live in CRM across 7 regions, 3 products and 6 audiences, 1 ready to sign, 4 needing a refresh, and 412 rep questions this week, 94% answered with a citation. The list under “Needs you” shows what each item is waiting for.
“Veltrimab product information — version 7 · Stability after dilution changed · 4 playbooks quote the old wording”
Lena picks Germany (58 reps), Veltrimab and Hospital pharmacist, and the account Klinikum Rheinhafen. 38 approved modules match. Before anything is built, the builder shows what it will leave out — DE-VEL-0371, expired Sep 30; DE-VEL-0388, withdrawn for its old stability wording; US-VEL-0207, approved for the US only — and that the Pflichttext will be added for Germany.
Audiences with no approved content for the product, such as Cardiologist for Veltrimab, cannot be picked: “No approved content”.
The agent run is shown step by step: the CRM account read, 38 approved modules found, 3 left out, 9 sections assembled with the wording unchanged, compliance check passed. The account snapshot opens the playbook — 1,150 beds, IBD centre, Dr. Petra Lindqvist as chief pharmacist, drug committee on Oct 22, 212 patients on IBD biologics — and the ward-stock question from the last call is answered in section 3.
“Built only from approved, in-date modules — wording is unchanged, so Medical and Legal approval carries over. Your sign-off publishes it.”
Beside the playbook, Lena asks the SOP assistant what a rep can say about storage outside the fridge. The answer comes from 3 passages in 3 documents in 0.9 s: up to 30 °C for a single period of up to 30 days in the carton, never back in the fridge. Anything beyond that is a medical question, logged as a medical information request in CRM during the call.
The answer ends with the approved wording to say, from module DE-VEL-0418.
A numbered citation opens the source with the passage highlighted: section 6.4 of the Veltrimab product information, version 7, effective 1 Oct 2026, and section 5 of SOP-COM-031 Communicating product handling. The same works for every source chip under every section of the playbook.
The sign-off screen lists what Lena is signing: 10 approved modules, all in date, next expiry Mar 12, 2028, nothing within 14 days; the Pflichttext for Germany included; the compliance check passed; publishing to the Germany hospital team, 58 reps, on the account tab and next call plan. She chooses the reason — “Approved for field use” — and enters her password.
“Your signature, the reason and the time are recorded on the audit trail.”
PB-2047 is live for 58 reps. In CRM, on the Klinikum Rheinhafen account and Jonas Weber’s call plan for Oct 14 at 10:30, the rep sees the opening line in approved wording, the talking points, what to keep on label, the approved materials to share and the SOP assistant. The footer reads “v1 · 10 approved modules · published Oct 6”.
Version 7 of the product information changed section 6.3: the diluted infusion is now stable for 8 hours at room temperature, not 4. Omar Haddad withdrew module DE-VEL-0388 on Oct 1 and DE-VEL-0421 was approved by Medical and Legal the same day. The freshness checker found the 4 live playbooks that still quote the old wording.
“Refresh 4 playbooks” swaps DE-VEL-0388 for DE-VEL-0421 and its local equivalents, reruns the compliance check and sends each playbook to its owner — Lena Ortiz, Marco Bellini, Lucía Romero and Sam Patel. Nothing changes in the field until they sign.
The freshness checker never edits a live playbook without sign-off.
A pharmacist asks Miriam about use in children. The assistant answers that Veltrimab is approved for adults only, that field colleagues never answer off-label questions, and how to pass it on: capture the question word for word with the pharmacist’s consent and submit it in CRM. It cites SOP-MED-022 and offers “Log medical information request”.
“They acknowledge within 1 business day.”
The same playbook, seen by the four people who carry it — what their week looked like, and what it looks like now.
Agents read the CRM account, assemble and check each playbook from approved content; the playbook owner signs.
Builds a playbook for one region, product and audience from approved modules, SOPs and the CRM account — orders the modules into the audience’s section template, adds the region’s mandatory text and returns every section with its sources.
Checks every assembled playbook before sign-off: each module approved, in date and tagged for the region, the mandatory text current, and no sentence that cannot be traced to a module or source.
After sign-off, publishes the playbook to the CRM account and the next call plan of each rep in the territory, and records the version published.
Watches product information, SOPs and modules for new versions, expiry and withdrawal, finds every live playbook that quotes the old content and proposes the replacement module.
Answers rep questions from the current SOPs and product information, cites every statement and offers the approved wording when one exists.
Signs before it goes live. The agents propose; a named person decides.
Playbook owners can ask about any playbook, the content behind it or how reps use it — or tell it what to change. Answers cite their source.
Which playbooks still quote the old stability wording?
Four published playbooks quote version 6 of the Veltrimab product information — 4 hours at room temperature after dilution. Version 7 says 8 hours. They are PB-2038 Germany · Infusion nurse (31 reps), PB-2033 Italy · Hospital pharmacist (16), PB-2031 Spain · Hospital pharmacist (14) and PB-2027 UK · Hospital pharmacist (21). Use Refresh 4 playbooks to swap in the current module.
Start a playbook for France · Veltrimab · Gastroenterologist
Done — France, Veltrimab and Gastroenterologist are picked in the builder. 44 approved modules match; one French module is still in review and will be left out. Check the account and press Assemble playbook.
Hold content that expires within 30 days
Rule changed: modules expiring within 30 days (was 14) are now left out of new playbooks. That holds 23 modules today, including DE-VEL-0412 (expires Oct 28). Existing playbooks keep them until the freshness check swaps them out. The change is in Settings and on the audit trail.
How are reps using the Germany gastroenterologist playbook?
PB-2046 has been opened 318 times by 22 reps since Oct 2. The most opened sections are Open with (204), Questions they may ask (166) and Stay on label (97). Reps also asked the assistant 41 questions from this playbook — mostly about dosing intervals.
13 screens from the working solution, on its sample data. Pick one to see it large.
Content rules, reviewers and where playbooks appear in CRM are settings, applied every time a playbook is assembled.
| Setting | Default | Choose from |
|---|---|---|
| Use approved, in-date content only | On | Draft, in-review, expired and withdrawn modules are never used |
| Hold content that is about to expire | 14 days | Any number of days, e.g. 30 |
| Add the region’s mandatory text automatically | On | Pflichttext · mentions légales · prescribing information · safety information |
| Keep playbooks current | On | Re-check every live playbook when a source changes |
| Medical review | Dr. Maya Chen | Dr. Maya Chen · Dr. Felix Brandt |
| Information officer — Germany | Katrin Hoffmann | Katrin Hoffmann · Jens Albrecht |
| Playbook sign-off | Playbook owner | Playbook owner · Playbook owner + Medical |
| Publish to | Account and call plan | Account and call plan · Account only |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample markets and products · “proven” = user acceptance testing at a global medtech manufacturer · “target” = the design goal, measured in the live solution · “estimated” = our estimate. Products, hospitals and people named on this page are characters in the working solution.
It assembles a tailored sales playbook for one region, product and audience from your approved, in-date content and the CRM account, checks it for compliance and publishes it to CRM once the playbook owner signs. Reps also get an SOP assistant that answers from current SOPs and product information, with the passage cited.
No. The playbook assembler uses approved modules word for word and never paraphrases a claim. The compliance check flags any sentence that cannot be traced to a module or source, and any new wording goes back to Medical and Legal.
The content freshness checker watches product information, SOPs and modules for new versions, expiry and withdrawal, and finds every live playbook that quotes the old content. It proposes the approved replacement, the compliance check reruns, and the owner signs before the new version goes live.
The region’s mandatory text — Pflichttext in Germany, mentions légales in France, prescribing information in the UK, Important Safety Information in the US — is added from the current approved module. In Germany, the information officer signs mandatory text and German-language modules.
It does not answer them. For questions on use in children, doses or intervals outside the label, or storage outside the label, it explains how to log a medical information request in CRM. If a rep hears about an adverse event, it prompts a report within 24 hours.
Yes. Medical and Legal approve the modules, the playbook owner signs every playbook with a password and reason, and nothing reaches CRM before that signature. The freshness checker never edits a live playbook without sign-off, and every step is on the audit trail.
The Agentic Solution Engine builds and deploys it from your requirements — your approved content, SOPs, product information and CRM territories — and it goes live once every quality gate has passed. We will walk you through it on a sample of your own content first.
The quarterly risk narrative, drafted in minutes with every figure from a live query.
1-min filmClaims ReviewEvery chargeback claim read first by agents, each verdict with its rule and evidence.
1-min filmClaims CheckEvery claim in a promotional draft tied to the page that supports it, before it reaches the review committee.
1-min filmWe’ll run Field Playbooks on a sample of your own approved content, SOPs and product information.