Skip to content
GullySales

API manufacturers · Website

Build a site that a quality head can check before agreeing to a trial.

A website for an API plant is the reference a sourcing manager and a quality head open after any introduction. GullySales works on the molecule pages, the document list, the plant description and the enquiry route.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

Pharmaceutical staff inspect sealed medicine packs in a cleanroom

What website means

A website is the page a customer lands on after searching, clicking an advert or scanning a code, and it decides whether they call or leave. GullySales builds and maintains sites that load quickly, explain the offer plainly and make the enquiry form or phone number easy to find.

Last updated 14 Nov 2026.

For API manufacturers

Where it usually goes wrong, and what we would do.

  • “The site is checked after every other contact”

    Whatever brought the buyer to you, a trade fair, a mail or a recommendation, the next step is to open your site. A thin or confused site undoes the effort that went before.

  • “A catalogue of names is not a product page”

    The buyer wants grade, standard, packing, storage and documents on one page. A list that stops at the molecule name leaves the buyer to email for facts the site should supply.

  • “Quality heads look for the plant”

    A buyer who might audit you wants to see the site layout, the laboratories and the quality systems described. Plain, accurate descriptions, with permitted photographs, stand in for a first visit.

  • “A site must not say more than the filings allow”

    Statements about approvals, inspections and markets must match the documents. An optimistic line on a page is read by buyers and regulators alike, so regulatory approves each claim.

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.

  1. Molecule pages with technical detail

    A page per product with grade, standard, packing, storage, documents available and markets served, as cleared.

    Result: A buyer can write a sample request from the page without further questions.

  2. A documents page

    A clear list of the papers you can supply and the process for requesting them.

    Result: The page lists each document type and how to ask for it.

  3. A plant and quality page

    A factual description of facilities, laboratories and quality systems, with approved photographs.

    Result: A quality head reads what the plant has and what it has not claimed.

  4. An enquiry route for samples and documents

    A form and a contact route that capture molecule, grade, intended use and company.

    Result: Each submission arrives with the details your team needs to reply.

  5. Pages for overseas importers

    A page that states the markets where your filings permit supply and what an importer should ask for.

    Result: An importer can tell from the page whether to proceed.

How the result is measured

  • Page load time
  • Bounce rate
  • Enquiries from the website

Recorded as a baseline before work starts, so every later report has an honest comparison.

Searches your buyers type

Give a quality head the pages they check before a trial.

[molecule] grade, standard, packing and storage
A molecule page with every field a sourcing team needs, so a sample request can be written without a further mail.
API documents available on request
A documents page listing the papers you can supply and how to ask, without claiming approvals your adviser has not confirmed.
API manufacturing facility and quality systems
A plant page with an accurate description and approved photographs, standing in for a first visit.
request an API sample
The enquiry page, with molecule, grade, intended use and the company the material is for.
API supplier for regulated markets
A page for overseas importers stating the markets supplied as the regulatory team confirms them.

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.

  • Your regulatory team has not reviewed the claims about markets and approvals, so a page could state more than the filings allow.
  • Your document list is changing and no one owns the library, so the documents page would fall out of date at once.

Before you decide

Agree the work. Know how to judge it.

Website for API manufacturers: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

List the pages that support a buying decision and the actions visitors must complete. Keep examples of failed forms, unclear product information, and questions your team answers repeatedly.

Make the scope clear

Agree the page list, content ownership, integrations, and who controls the domain and hosting. Include redirects and existing search traffic in a redesign brief, before changing addresses.

Check the work in use

Complete a real enquiry journey on a phone and a laptop. Check that the confirmation appears, the enquiry reaches the right person, and tracking records the action once.

Know when to change course

If visitors can enquire but the team does not follow up, start with the sales handover. A larger website will not resolve that delay.

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.

Final product and specification list
Provide the list of molecules, grades and packs you want shown, with the specifications behind them. The site copies these. If the list changes after launch, someone must update the pages, so name that person. A spreadsheet is the usual format, with one row per molecule. Mark which entries are not final.
The documents you are willing to host or send
Decide which documents sit on the site, which are sent on request and which are for existing buyers only. We build the documents page on your decision. Without it, the page lists nothing, and buyers email for everything. Say which are safe to share openly and which only with a named buyer.
Plant photographs and facts checked by the plant head
Bring photographs and a short description of the plant and quality laboratory, checked by the plant head. Anything that shows a process secret or a visitor is removed. If none exist, we plan a plant walk before writing the page. Send them as files, not as screenshots, so we can use them at full size.
Existing domain, hosting and email access
Hand over the domain, hosting and email details held by the company. We need them to publish and to route forms. If an agency or former employee holds them, secure the transfer first. If you do not know who holds them, a bill, a renewal email or a registrar lookup shows it. Then ask the holder to release them.
A decision on what overseas importers see
State whether importers get a separate page and which documents it mentions. We write the page on that basis. If the company has no stated export position, regulatory should say so, and the page stays general. Importers differ by country, so general wording suits a company without a stated export view. Say it plainly in the brief.

How it works

How the website 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. 1

    Audit the current site as a buyer would

    We open your present site as a sourcing manager would, searching for a molecule, a document and the plant. We note where the trail ends, then list the pages, forms and links to keep, rewrite or retire, and you correct any note that is wrong. Screenshots of every dead end go into the file, with the page it was on.

  2. 2

    List the molecules and documents for the site

    Your quality and regulatory staff supply the final list of molecules, grades, packs and documents available on request. We settle the page for each one. Anything under revision or not yet filed stays off the site until it is clear. The list is checked by quality and regulatory in one sitting, so changes do not arrive piecemeal.

  3. 3

    Draw the page structure with buyers in mind

    We sketch the home page, molecule pages, the documents page, the plant page and the enquiry route, then show it to your sales head. You move or remove pages until the structure follows how sourcing staff actually look for a supplier. We keep the structure shallow, so a buyer reaches a molecule or document in few clicks.

  4. 4

    Write the molecule and plant pages

    We draft molecule pages from the approved specification, and the plant page from a walk with your plant head. Quality and regulatory staff correct each page, and a page with an unconfirmed fact is held until the fact is checked. Facts are never written from memory; each one is traced to a signed document or a person's name.

  5. 5

    Build the enquiry route for samples and documents

    We build separate routes for a sample request, a document request and an importer's question, each landing with a named owner. Your team tests them with sample enquiries, and we fix any route that arrives at a general inbox. Every route sends an acknowledgement to the buyer, and the acknowledgement makes no promise about time.

  6. 6

    Publish, then compare with the starting enquiries

    After sign-off we publish and hand over the logins. We compare the enquiries naming a molecule and the sample requests with the start record, and you see which pages are used and which need more information. We also list the pages that need regular attention and name the person who owns each.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.

  1. 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.

  2. 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.

  3. 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.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

How many pages does an API site need?
Enough for a page per molecule, a documents page, a plant page, a company page and a contact route. The number follows your product list. Do not add pages that say nothing a buyer can use.
Can we show regulatory certificates on the site?
Only those your regulatory team approves for public display, shown exactly as issued. Rules on what may be displayed differ by profession and state, so check with your own adviser before publishing any certificate.
What about a secure area for buyers?
A login area for documents suits confidential papers. It is extra work to run and to keep current, so consider it after the public pages are complete and your document library is organised.
Should the site list our customers by name?
No. Supply relationships in this trade are confidential, and an agreement can forbid naming the buyer. Describe the types of buyer you serve in general words, and show a name only with written permission.
Should the site have a login area for approved buyers?
Only if you have buyers who regularly need current documents and your team can keep the area up to date. A login that holds stale certificates is worse than none. Several plants send documents on request through the enquiry route, which is simpler. We recommend starting without a login and adding one if the volume of requests demands it. Start with the enquiry route and add a login only when requests justify it. A login adds a maintenance duty, and someone must own it.
Who updates the site when a specification changes?
A named person in your company, in quality or sales support, updates the page after quality approves the new specification. We write a short update note and show that person how to edit. A specification that changes without a matching page update is how buyers receive conflicting information. Without that step, the site and the documents library drift apart, and a buyer may download an older certificate. The update note puts the order in plain words: quality approves, the editor changes the page, and sales tells existing buyers.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.

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.