API manufacturers · CRM
Keep every sample, document request and trial on one record per buyer.
A CRM for an API plant is a shared record of each buyer company, the people in it, the molecules asked about and the state of every sample and trial. GullySales sets up the fields, the stages and the habits your team uses to keep it current.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What CRM means
A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.
Last updated 14 Nov 2026.
For API manufacturers
Where it usually goes wrong, and what we would do.
“The company is the record, not the enquiry”
A formulator may send four enquiries from three people over a year. If each enquiry is a separate row, nobody sees the pattern. One record per company, with people and molecules beneath it, shows the whole relationship.
“Trials need stages that match the buyer's work”
Sample sent, trial in progress, results awaited, filing change under way and first order are real steps. A generic pipeline of lead, proposal and won hides where a trial is stuck.
“Documents sent belong in the record”
When the pack goes out, the record should show which documents, which version and on what date. When a buyer says they never received something, you can answer from the log.
“Regulatory and sales both need to read it”
If sales cannot see which grades are filed and regulatory cannot see what was promised, the gap becomes an error. A shared record, with limited editing rights, closes it.
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 record built around buyer companies
Fields for company type, molecules used, current source, roles in contact and market.
Result: Opening a company shows its people, molecules and the whole history on one screen.
Trial stages that mirror the buyer's process
A sequence from sample request to repeat order, with a reason field for stalled trials.
Result: Every trial sits in a stage and every stalled trial has a stated reason.
A document log
A field that records each pack, the documents inside it and the date it was sent.
Result: You can answer what was sent to whom without searching mailboxes.
Views for each role
A sales view, an export view and a regulatory view of the same data.
Result: Each role sees the records that concern them without scrolling through the rest.
Data entry habits
A short guide on what to record after each call and who is responsible.
Result: Staff know what to write after a call and where to write it.
How the result is measured
- Enquiries logged in the CRM
- Data completeness
- Reports generated from CRM data
Recorded as a baseline before work starts, so every later report has an honest comparison.
Fields worth keeping
Keep these fields against each buyer company.
- Molecules asked about and grade
- Entered by the sales executive after each call, so the record shows the whole range of interest for one company.
- Roles and names in contact
- Purchase, R&D, quality and regulatory contacts, kept by sales so a follow-up reaches the right desk.
- Trial stage and stalled reason
- Sales updates it after each call. A reason field turns a silent trial into something the team can learn from.
- Documents sent with version and date
- Logged by whoever sends the pack. It answers a buyer who says a paper never arrived.
- Filed grades and markets
- Maintained by regulatory and visible to sales, so no one promises a grade or market that is not filed.
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 a few buyers and the sales head holds every detail, so a CRM would add entry work with little to read back.
- Regulatory and sales have not agreed who maintains filed-grade data, so the field would be wrong from the first week.
Before you decide
Agree the work. Know how to judge it.
CRM for API manufacturers: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.
Make the scope clear
Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.
Check the work in use
Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.
Know when to change course
If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.
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.
- The current buyer spreadsheet or contact list
- Bring the file your sales team uses now, however untidy. We map its columns to the new record. If several versions exist, tell us which one is trusted, or the cleaning will take the longest. Include the business-card folder and the mail contacts as well. Mark the sheet you would keep if you could keep only one.
- A list of open samples and trials
- Write each sample sent and each trial running, with the buyer, molecule and last contact. These are the first live entries. If the list is not ready, the record begins empty, and the team may not see its use. Names of buyers can be coded; we only need the molecule, the stage and the last contact date.
- The documents you send to buyers
- Provide the standard set of certificates, specification sheets and filing references with their version numbers. The document log refers to them. If versions are unclear, quality must settle which is current before we log anything. Version dates matter, because a buyer who received an old specification needs a corrected copy.
- Decision on who edits and who reads
- Say who may create and change buyer records, and who may only view them. We set the rights from this. Without a decision, everyone edits and the record soon contradicts itself. Choose it per role, not per person. Roles with edit rights should be few, since each extra editor adds a risk of duplicate entries.
- A sales staff member to be the record keeper
- Choose someone to check entries and chase gaps. The record needs one custodian. If every salesperson owns their own data, the shared view fails, and the buyer ends up asked the same question twice. Without it, duplicates and half-filled records spread. It may be a sales assistant instead of a senior salesperson.
How it works
How the CRM 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
Take stock of every buyer file you keep
We collect the spreadsheets, email folders, business cards and trade-event lists where buyer information lives today, and list the fields in each. You show us which file the sales head actually relies on, and we use it as the starting point. Cards from trade events are scanned and added only if the person is still at that company.
- 2
Choose the buyer company as the main record
We agree that the main record is the company, with people, molecules, samples and trials linked to it. Your sales head confirms the fields, and we remove any that nobody would fill in, since an empty field is worse than none. A field is kept only when somebody can name a decision it helps.
- 3
Define trial stages from the buyer's own process
We write stages that follow what a formulator does: request, sample sent, in testing, result, approved source, order. Your technical sales staff correct the names and add the stage where silence begins, so the pipeline reflects the real work. Stages are numbered in the order a buyer moves, so a salesperson sees the next step at a glance.
- 4
Add the document log and role views
We add a place to record which certificate, specification or filing reference was sent to whom, and set up views for sales, quality and regulatory. Each role sees what it needs, and regulatory staff can read without editing. Regulatory staff see documents and trial status, while price fields stay with sales.
- 5
Load existing buyers and test on live enquiries
Your team moves the active buyers and open trials into the record, and we watch for confusion over three or four live enquiries. We change field names or stages that people misuse, and fix duplicates before they spread. Duplicate companies are merged by the sales head, with both owners informed.
- 6
Read the record against the starting figures
After a period of use we compare the record with the start figures: samples sent, trials open and purchase orders. You see which trials are stuck and why, and your sales head decides who owns the follow-up. We also list the fields nobody filled in, and drop them. Training is repeated for any role that struggled.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales management. A target, a review routine and someone who owns the number.
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
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3 · you are here
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.
Which CRM should an API plant use?
Can we use a spreadsheet instead?
Who should be allowed to edit buyer records?
Should regulatory staff have edit rights on buyer records?
Should regulatory staff see commercial prices in the record?
What happens to buyer data when a salesperson leaves?
How long is the contract?
How soon will we see results?
Who will actually do the work?
What do you need from us?
More for API manufacturers
Related work to consider.
Closest to this: leads and follow-up
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.