API manufacturers · Buyer persona
Write down who at the formulator asks, who vetoes and who signs.
A buyer persona for an API plant describes the separate people inside a formulator or contract manufacturer who shape a source change. GullySales works with your sales head to write one persona per role and to match each to what they need to see.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What buyer persona means
A buyer persona is a plain description of the kind of customer who actually buys from you. It includes what they search, what worries them and who else they ask before deciding. GullySales builds this from real enquiries and past sales rather than a generic template, then uses it to write every page and advert.
Last updated 14 Nov 2026.
For API manufacturers
Where it usually goes wrong, and what we would do.
“Four people, four different questions”
The purchase executive asks about price and supply. R&D asks about impurity profile. Quality asks about audit history. Regulatory asks about filings. Writing one persona for all four produces a message none of them finds useful.
“A persona for a regulated-market buyer differs from a domestic one”
An overseas buyer begins with filings and inspection record. A domestic formulator begins with supply reliability and batch consistency. The same molecule needs two different first replies.
“A contract manufacturer buys for someone else”
A contract manufacturer buys what its client specifies and cares about lead and consistency. Its persona is built around the client's needs, so ask who the client is.
“A trader is a persona too”
A trader wants margin and prompt answers, and may hold the relationship you want. Treat the trader as a role with its own needs, not as an obstacle, and decide in advance what you offer to one.
What we do
What we deliver for API manufacturers.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
A one-page persona for each role
Purchase, R&D, quality and regulatory, each with the questions they ask, the documents they want and the worry behind them.
Result: Each role has a page your sales team can read before a call.
A buyer-type split
Separate notes for formulators, contract manufacturers, importers and traders.
Result: Your team can say which type a given enquiry is before replying.
Question-to-document mapping
A table matching each common question to the document or page that answers it.
Result: For any question a buyer asks, you can point to the answer without searching.
Interview notes from your own team
A short record of what your sales and quality staff have heard from buyers, kept as evidence for each persona.
Result: Every persona statement can be traced to a real conversation.
A review after real calls
A check of each persona against what actual buyers said, with corrections noted.
Result: Persona pages carry a note of what changed after the latest calls.
How the result is measured
- Enquiry match to persona
- Conversion rate by persona
- Content aligned to persona
Recorded as a baseline before work starts, so every later report has an honest comparison.
Who is asking
Each person at a formulator asks something different first.
- Purchase executive at a domestic formulator
- Wants supply reliability, batch consistency and price, and sends the first mail.
- R&D scientist planning a trial
- Wants the impurity profile, particle size and form, and a sample to test against the current source.
- Quality head weighing an audit
- Wants inspection history, systems description and the full document list before agreeing to visit.
- Regulatory lead at an overseas importer
- Wants filing support, the market's requirements and the status of the product, as your adviser can state it.
- Trader holding the relationship
- Wants margin and a prompt answer, and may not name the end buyer unless asked politely.
Who it is for
This is written for these API manufacturers.
- Generic API manufacturers for domestic formulators
- Regulated-market API plants with overseas filings
- Intermediate and advanced intermediate producers
- Herbal extract and phytochemical API makers
- Vitamin, amino acid and nutraceutical ingredient producers
- Veterinary API manufacturers
- Peptide and complex molecule producers
- Custom synthesis and CDMO units making APIs to order
Before you decide
When this may not be the right fit.
- You have only a handful of buyers whom the sales head already knows well, so formal personas would restate what they do daily.
- No one has recorded what buyers ask in audits and calls, so a persona would be built from impressions.
Before you decide
Agree the work. Know how to judge it.
Buyer personas for API manufacturers: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
Write the decision the research must support, such as entering a market or choosing a buyer group. Separate what you know from sales records from what the team currently assumes.
Make the scope clear
Agree which buyers to speak to, which sources to review, and what access you can provide. Include lost enquiries and people who chose another supplier, where they are willing to take part.
Check the work in use
Look for source dates, sample limitations, and evidence that disagrees with the preferred answer. A recommendation should show how it follows from the findings.
Know when to change course
Do not treat a few positive conversations as proof of demand. Test the proposed offer with an actual buying decision before committing to a wider launch.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from API manufacturers. Anything missing is noted in the written scope, with who will supply it.
- A list of trials with their outcomes
- Bring a sheet of recent trials, naming the buyer type, the molecule and the stated reason for the result. Buyer names may be coded. Without outcomes, the personas describe the ideal buyer, not the actual one. Where no outcome was recorded, say so, since an honest gap is better than a guess.
- Your sales head's time for the interviews
- The sales head knows how each role behaves. Set aside a sitting, uninterrupted. If the sales head is travelling, the interviews pass to the technical sales staff, and the pages reflect their narrower view. Without that time, the pages describe the roles from outside, and the sales head corrects them later.
- Sample correspondence with technical teams
- Share a handful of email threads with R&D and quality contacts, with names hidden. They show real wording and real objections. If all correspondence is on phone calls, we rely on staff recollection. A forwarded thread with the signature removed is enough for our purpose. Even three or four threads show the wording well.
- A decision on the buyer segments
- Decide which segments you serve, such as domestic formulators, regulated-market buyers, contract manufacturers and traders. We write personas for these. If the company is still choosing, we wait rather than write for segments it will not pursue. The persona pages are written for these only, and others are added on request. Say which you will not serve.
- Access to someone from the regulatory team
- A regulatory staff member must tell us what buyers ask about filings and what the company can answer. Without their input, the regulated-market persona is thin, and it may ask for documents you cannot supply. Bring them in for a single sitting, so the regulated-market page asks only for documents you hold.
How it works
How the buyer persona work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Pick the roles that block a source change
With your sales head we name the roles at a formulator or contract manufacturer who touch a new source: sourcing, R&D, quality assurance, regulatory and purchase. You tell us which two or three decide the outcome of your trials, and we start with those. The remaining roles are added later, when the first pages have proved useful.
- 2
Read past trials for who asked what
We go through emails and trial files and note, for each trial, which role asked which question and what delayed the decision. Your sales team fills the gaps from memory, and we mark what is fact and what is recollection. Silence is also data: we record the trials where nobody ever said why.
- 3
Split the regulated-market and domestic buyer
We separate buyers who need filing references and inspection history from buyers who judge on supply reliability and consistent batches. Your sales head confirms the split against actual accounts, and each type gets its own set of questions. A buyer can sit in both groups, and the page says which questions apply when it does.
- 4
Talk to your sales and quality staff
We interview your salespeople, technical sales staff and quality representatives about what each role says in the first call, what they reject and what makes them agree. We write their answers without buyer names. We ask which question they find hardest to answer on a first call, and why.
- 5
Write one page per role and match documents
For each role we write a page with its goal, its fear, the questions it asks and the document that answers each. You check every page against a real buyer and correct anything the buyer would not recognise. Each page is one sheet long, so it can be pinned beside the desk. Wording a buyer would never use is removed.
- 6
Test the pages on live calls and revise
Your team uses the pages on real calls and notes where a role asked something the page missed. We add those, and compare the number of calls where the right document was ready first time with the start record. Pages that fail on a call are corrected from the notes taken. Roles with no page yet are listed for later.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 0, foundation. The audit comes before it, and sales management keeps it running.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2 · you are here
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Do we need a persona if we only have a few buyers?
Where does the evidence come from?
Should the persona name actual companies?
Can the persona include a company's actual name?
Should the persona cover the trader as well?
Can one person fill several roles at a small buyer?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for API manufacturers
Related work to consider.
Closest to this: strategy and research
Also for API manufacturers
Or start from the overview: sales and marketing for API manufacturers.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.