Capabilities with numbers
Processes, machine list, capacity per month, materials handled, tolerances, finishing. A buyer is checking feasibility, and adjectives do not answer feasibility questions.
An export buyer shortlists you from another country using nothing but your website. Most NCR manufacturing sites give them almost nothing to shortlist on.
A manufacturing or export website has one job: let a technical buyer establish whether you can do the work, without a call. That means published capabilities, capacity, materials, tolerances, certifications and lead times. Brand language without specifications loses to a plainer competitor who published the numbers.
Processes, machine list, capacity per month, materials handled, tolerances, finishing. A buyer is checking feasibility, and adjectives do not answer feasibility questions.
ISO, industry-specific approvals, export codes, compliance marks. For international buyers these are frequently a filter before anything else is read, so they belong high on the page rather than in a footer.
Sectors served, order volumes, export destinations, years operating. Named clients where you have permission, described anonymously with real numbers where you do not. Never invented, because one questioned figure discredits the page.
Time zone, who responds, in what language, and how quickly. An RFQ form that captures specification, quantity and target market, with WhatsApp as an alternative because a large share of export enquiries arrive that way.
Specification sheets, catalogues and capability documents downloadable without a form wall. A champion inside the buying company needs something to circulate internally, and gating it means it does not get circulated.
Buyers may be on poor connections in other markets. Light pages, no heavy sliders, and plain English written for a reader whose first language may not be English.
| Problem | What it costs |
|---|---|
| Brand language, no specifications | Buyers cannot judge feasibility and move on |
| Certifications buried or undated | Fails the first filter for export buyers |
| No capacity or lead time | Every enquiry starts with questions you could have answered |
| Catalogue behind a form | Nobody circulates it internally |
| One page for all products | Ranks for nothing specific |
| Contact form only, no WhatsApp | Loses a large share of export enquiries |
| Site slow and image-heavy | Buyers on poor connections leave |
| Ask them | A good answer sounds like | Walk away if |
|---|---|---|
| Who owns the work and files? | You do, unconditionally, in the contract | Ownership depends on staying with them |
| Can I see three live examples? | URLs you can open and check yourself | Screenshots and a portfolio PDF |
| What is explicitly not included? | A written list with change pricing agreed | Everything is included, which means nothing is defined |
| How will we know it worked? | A metric agreed before the work starts | They report activity rather than outcome |
The last question separates most of the field, because answering it commits them to a number.
Want capability, location, delivery terms and a number to call. Shorter buying cycle and more likely to visit.
Want certifications, export history, documentation, payment terms and confidence you can hold quality at volume without them being present.
One site can serve both, with distinct paths and content rather than a single page hedging between two very different readers.
Capabilities with numbers, machine list, capacity, materials, tolerances, certifications, lead times, sectors served and export history. A technical buyer is establishing feasibility, and that cannot be done from brand language.
Yes. It is the fastest way for a buyer to establish whether to contact you, and it filters out enquiries you cannot serve. Competitors can already find this out by asking; the buyer you lose by hiding it is the more expensive loss.
Search, trade portals and referral, then they shortlist from websites before contacting anyone. Certifications and specification detail are usually the first filter, which is why they belong high on the page.
Generally no. Buyers circulate specification documents internally to build a case for you, and gating them means that does not happen. Capture the enquiry through the RFQ path instead, where the intent is already higher.
Only if you sell into a specific non-English market at volume. Plain English written for a reader whose first language is not English usually does more than a poorly translated second version.
Through an RFQ form capturing specification, quantity and destination, plus WhatsApp, since a large share of export enquiries arrive that way. State who responds and how quickly, because a buyer in another time zone is comparing responsiveness.
Yes, with a structure that lets your team add products without a developer. One page per product family, because a single combined products page ranks for nothing and gives buyers nothing to evaluate.
Send us what you are trying to fix and we will tell you what it takes, what it costs, and whether we are the right people for it. If we are not, we will say so.