On this page
Why one message for everyone falls flat
Buying a bioreactor or a TFF system goes through many hands. Process development, engineering, QA, production, procurement and the site head all look at the same equipment, and each one is checking for a different risk. If your message only covers technical performance, QA and procurement find nothing for them and the project stalls.
Research by the Ehrenberg-Bass Institute for LinkedIn's B2B Institute points out that most of your customers are not in the market at any given time. So marketing's job is to make the brand come to mind in the buying situations that matter. In pharma, that means every role on the committee should know you before the specification is written.
A message map for every role on the committee
A message map is a simple table. At the top sits the core promise, the same for everyone. Below it, each role gets its main question and the proof that answers it. You already have the arguments, because they come from technical meetings, quotes and customer questions. The map simply puts them in order.
| Role | What they want to know | Proof that works |
|---|---|---|
| Process engineering | Whether the equipment meets the URS and integrates with the plant | URS compliance matrix, drawings and interface list |
| Process development | Whether results hold when scaling up | Scale-up data and shared design criteria across scales |
| QA and validation | How much qualification work it will create | Documentation package, FAT and SAT protocols and IQ and OQ support |
| Production | Whether the equipment is easy to run and clean | Operation video, training plan and batch changeover explained |
| Procurement | What it will cost over the equipment's whole life | Cost of consumables, spare parts, service and validation |
| Site head | What risk comes with this supplier | References, local technical service and company stability |
Do we need a separate page for each role?
Not always. A well-structured product page with blocks that answer each role, plus a few downloadable documents for QA and procurement, is often enough. What matters is that each block is easy to find, because the engineer and the buyer will not read the page in the same order or with the same questions in mind.
Engineering wants proof the equipment fits their URS
For engineering, the document that rules is the user requirements specification, the URS. Points 3.2 and 3.3 of Annex 15 of the EU GMP guidelines say the URS should be the point of reference throughout the validation life cycle and that design qualification should verify its requirements. So your message has to speak that language.
A good approach is to offer a matrix that answers the client's URS point by point, and to show on the website which sizes, sensors, connections and software options can be configured. ISPE's Baseline Guide on commissioning and qualification covers best practices for the URS and for design review.
Who should write the message, marketing or engineering?
Both. Marketing structures and writes, and engineering and QA check that every claim is true and defensible. If one of your engineers would not say a sentence in front of a client, it should not be published. This review also stops you promising things the project team cannot deliver later on.
Want to know which role on the buying committee your website leaves without an answer? Leave your details and we will take a look.
Review my messageQA and validation want to know how much work lands on them
QA is mainly trying to reduce risk ahead of an inspection. Point 3.6 of Annex 15 allows, where appropriate and justified, some documentation review and testing to be done at the FAT, at the supplier's site. It then does not need repeating at IQ and OQ, provided it can be shown that transport and installation do not affect functionality.
That argument carries weight if you can back it up. Explain what documentation package you deliver, what your FAT and SAT protocols look like and how you support IQ and OQ. If the equipment runs software with electronic records, describe how the audit trail and access controls work, because QA will be thinking about the FDA's 21 CFR Part 11.
How do we know whether the message map is working?
Watch the conversations. If QA and procurement questions arrive earlier and are better framed, or if quotes get stuck less often at the review stage, the message is helping. You can also ask new customers what made them decide and compare their answers with what the map says.
Procurement and site heads look at total cost and risk
Procurement compares quotes, but with bioprocess equipment the purchase price is only part of the story. There are single-use consumables, spare parts, service contracts, validation hours and production downtime. If you do not explain those costs, the buyer estimates them alone or sticks to the quote price, which is usually the worst comparison for a mid-sized manufacturer.
The site head adds one more question, which is what risk comes with choosing a smaller supplier. Local technical service, a response time you can actually keep, references you are allowed to show and a clear company profile all help here. All of it should be on the website and in the sales deck.
What if we sell through distributors?
Then the map is even more useful. Distributors should receive the same arguments and proofs for each role, translated and adapted to their market. If every distributor explains the product their own way, the buying committee hears different messages depending on the country and the brand loses strength.
How to build the map and who should use it
The map comes out of a working session with sales, engineering, product and QA. Go through the questions clients ask in quotes and meetings, group them by role and pick the best proof for each one. From then on, every product page, every deck and every follow-up email should use the same words.
David Monje, founder of crida studio, led marketing at TECNIC Bioprocess Solutions for four and a half years. Part of that job was bridging engineering, product and sales, including when opening markets such as Germany, Scandinavia and Asia. Every company has its own buying committee, so the map has to be built from its own customers' questions.
