API manufacturers · Follow up systems
Give every sample and trial a named owner and a next step.
A follow-up system for an API plant is the set of reminders, questions and owners that carries a buyer from sample to trial result to purchase order. GullySales writes the follow-up steps and the record so that no trial goes silent without a stated reason.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What follow up systems means
A follow-up system is the set routine for calling, messaging or emailing an enquiry more than once, since most buyers do not decide on the first conversation. GullySales sets the number and timing of follow-ups so an undecided buyer keeps hearing from you until they decide either way.
Last updated 14 Nov 2026.
For API manufacturers
Where it usually goes wrong, and what we would do.
“Silence after a sample is the usual leak”
The buyer has the sample and your team has no reason to call. Weeks pass, and the trial may be running, stalled or abandoned. Without a dated next step, nobody finds out until the buyer orders elsewhere.
“The right question depends on who you ask”
A purchase executive can tell you about budget and timing. R&D can tell you how the trial stands. Quality can tell you whether the documents satisfied them. One generic check-in reaches none of them.
“A stalled trial deserves a recorded reason”
Price, grade, filing, a change in plan or a competitor are all valid reasons. Writing the reason down turns a lost trial into information about what to change.
“Repeat buyers need follow-up too”
After a first order, a buyer who is not contacted drifts. A short check on batch performance and forecast keeps the supplier in view when the next requirement is planned.
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 follow-up script by role
Questions for purchase, R&D and quality to use after a sample or trial lot.
Result: A sales executive has the right questions ready for each person they call.
Owner and next-date fields
Every open trial carries a named owner and a dated next step.
Result: A list of open trials shows owner and next date for each, and overdue steps stand out.
Stalled-trial reasons
A fixed list of reasons, with a free note, filled in whenever a trial stops.
Result: You can group stalled trials by reason and see which reason repeats.
Post-order check-ins
A short set of questions after the first and later orders on performance and next requirement.
Result: Each repeat buyer has a recorded check-in after every order.
A hand-over note
A summary for any colleague taking over a buyer, drawn from the record.
Result: A new owner reads the history of a buyer in one place.
How the result is measured
- Follow-up completion rate
- Average number of follow-ups before close
- Enquiries closed after repeat follow-up
Recorded as a baseline before work starts, so every later report has an honest comparison.
What to capture or send
Plan the question for each step after a sample leaves.
- Sample dispatched
- A dated next step set the same day, with a named owner. It stops a sample going silent.
- Question to R&D after testing
- Ask how the trial stands against the current source. Record the answer against the molecule.
- Question to quality after documents
- Ask if the pack answered their audit questions or if anything is missing. Log the gap.
- Trial stopped
- Pick a reason from the list, such as price, grade, filing or competitor, and add a note.
- After a first order
- Check how the batch performed and what the next requirement looks like, then record the answer.
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.
- No one owns the sample once it leaves the plant, so a reminder routine would fire at nobody.
- Your regulatory team has not cleared what can be said about a grade, so scripted check-ins might promise something unfiled.
Before you decide
Agree the work. Know how to judge it.
Follow-up systems for API manufacturers: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
Trace recent enquiries from arrival to the last recorded action. Include a won enquiry, an unsuitable one, and one that went quiet, with personal details removed for the initial discussion.
Make the scope clear
Agree who accepts each enquiry, what makes it qualified, and how ownership changes. Include a rule for missed replies and a clear reason for closing an enquiry.
Check the work in use
Pick an enquiry at random and ask the team to find its owner, latest conversation, and next action. Check that the record agrees with what actually happened.
Know when to change course
If no one has capacity to respond, assign that responsibility before buying more leads. Automation can support the owner, but it cannot replace an unresolved handover.
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 list of samples sent in the past
- Gather the dispatch records for older samples, even those that went quiet long ago. We use them to see the pattern of silence. Without them, we begin the reasons list from only the current trials. Include samples sent by hand at trade events, which are rarely written down.
- A named owner for each buyer account
- Each active account needs a salesperson or technical sales contact who answers for it. We attach follow-ups to that name. Accounts without owners are left to chance, which is the habit we are trying to remove. Keep the list current: when an owner leaves, the sales head names a successor the same day.
- Access to the buyer record for the team
- The sales team must be able to open and edit the record, with their logins set. If the CRM is not yet in place, we use a shared sheet, and the follow-up plan stays simple until the record is ready. A paper register is acceptable, but then someone must enter its entries by hand into the record.
- A decision on how silence is closed
- Decide what your company does when a buyer stays silent after follow-ups: mark closed, keep warm or hand to management. We write the rule. Without it, items sit open for ever and the list loses meaning. A written rule saves the team from improvising when a quiet buyer is also a large one.
- Sample batch documents ready to attach
- Keep the certificate and specification for each sampled batch in one folder. Follow-up messages need them again. If they are scattered, the follow-up waits on a search and loses its point. Add the lot number and the dispatch date to the folder name, so nobody opens the wrong batch.
How it works
How the follow up systems 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
Map what happens after each sample leaves
With your sales and dispatch staff we trace what happens from the courier slip to the buyer's first reply, and note where nobody currently follows up. This map shows the points at which silence begins and who could speak first. The map is drawn on one sheet and shown to dispatch, so they can correct it.
- 2
Write the question for each buyer role
For a purchase contact we write a question about the sample's arrival and the plan; for R&D, a question about the test and any need for more information; for quality, one about the document set. Each is short and answerable in a reply. Each question points to a document or an offer, so the buyer has something to act on.
- 3
Set owners and next-date fields in the record
Every open sample and trial gets a named owner and a next action date in your buyer record. Your sales head agrees who owns what, and the team tests the fields on live items so nobody leaves them blank. The owner is a person, not a department, since a department cannot be asked why a trial stalled.
- 4
Agree the reasons a trial may stall
We list the real reasons trials go quiet: other priorities, a different supplier, a batch under review, a regulatory delay. Your team picks the list, and every stalled trial must carry one reason, so patterns can be read. Reasons are chosen from the list, with a free note allowed only for a reason not on it.
- 5
Prepare the check-in after the first order
We write the message and call script for a buyer after the first purchase order, asking about receipt, packing and any queries on the batch documents. Your quality head approves the questions on the batch, and the reply is logged. It also asks whether the packing and labelling suited the buyer's line. The answer goes into the record.
- 6
Review the stalled list against the start
We compare the stalled trials and their stated reasons with the starting count of silent samples. You see which reasons are common, which buyers moved forward after a follow-up, and what your sales head should change in the script. Where no reason was ever recorded, that gap is itself the first thing to fix.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 2, qualification. 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.
How often should we follow up on a trial?
What if the buyer simply does not reply?
Who owns the follow-up, sales or technical?
What do we do when a buyer never replies after a sample?
Who should call the buyer, sales or technical staff?
Is it intrusive to chase a trial that has gone quiet?
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: 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.