Proof without client names

Why a logo strip does not count as proof

A row of logos tells a buyer who you have sold to, not what you did for them. It says nothing about the product, the size of the order, the standard it was made to or whether it arrived on time, and those are the things a purchase manager is trying to judge.

In a study EbizIndia published in October 2026 of 30 Indian manufacturer websites, only 2 described a past project or supply in any detail. Eleven named at least three clients in text. Logos shown only as images were not counted, and an assistant reading page text often cannot see them at all. One common reason for the gap is that customers will not allow their names to be used.

What goes into an anonymised case note?

Five facts, written as plain sentences on a web page. Leave out the name and keep everything else specific.

• Sector and type of buyer. "A pump maker in western India", "an EPC contractor building a cement plant", "a state water utility". Size and region help if they do not point to one company.
• The problem. What the buyer needed or what was going wrong with the previous supplier: rejections, delays, a size nobody stocked, a test the old parts failed.
• What you supplied, to what specification. Product, sizes, material grade, standard, quantity, inspection. This is the part buyers search for and the part competitors cannot copy.
• The outcome. A measured result where you have one: rejection rate, delivery against schedule, approval granted, repeat orders.
• Time taken. From enquiry or purchase order to first dispatch, and for the full order.

Add a month and year. A dated note tells the reader the work is recent and tells an assistant the fact is current.

How much can you say without breaking confidentiality?

Usually more than owners assume, but read the contract first. Some agreements forbid any mention of the supply, and those cases stay off the site. Where the contract is silent, the safe line is this: describe the buyer by sector, region and scale, and never publish anything that identifies them by itself.

Things to leave out: the project name, an exact site location when only one plant exists there, the customer's drawings or part numbers, prices, and photographs showing their logo or equipment. Things that are normally fine: your own product, its specification, quantities in round figures, the standard and the inspection method. When in doubt, send the client the draft. A two-line email showing exactly what will appear often earns permission to say more.

Three example case notes

The three notes below are illustrative formats written for this article. They are not real clients and the figures are invented to show the shape. Replace every line with your own facts.

Example A: ball valves for water treatment (illustrative)

• Sector: a water treatment contractor working on municipal plants in Maharashtra.
• Problem: the contractor needed 50 mm and 80 mm ball valves with stainless trim inside six weeks, and its regular supplier had a three-month backlog.
• Supplied: 640 ball valves, PN16, CF8M body, flanged ends, hydro-tested at 24 bar with test certificates for each lot.
• Outcome: all lots passed third-party inspection at first offer.
• Time taken: five weeks from purchase order to final dispatch. March 2026.

Example B: SG iron castings for a pump maker (illustrative)

• Sector: a mid-size agricultural pump manufacturer in Gujarat.
• Problem: porosity in impeller housings from the previous foundry was causing machining rejections.
• Supplied: SG iron castings to IS 1865 grade 500/7, 4 kg to 18 kg, with method changes to the gating and sample radiography on each heat.
• Outcome: machining rejections fell from about 6 per cent to under 1 per cent over the first four monthly batches.
• Time taken: eight weeks to approved samples, monthly supply since. Approved June 2026.

Example C: TMT bars for a warehouse project (illustrative)

• Sector: an EPC contractor building a logistics warehouse in eastern India.
• Problem: the site had little storage space and needed steel delivered in phases matched to the pour schedule.
• Supplied: 1,200 tonnes of Fe 500D TMT bars to IS 1786, 10 mm to 25 mm, with mill test certificates per heat, in eleven scheduled lots.
• Outcome: ten of eleven lots arrived on the agreed date; one was two days late due to a transport strike.
• Time taken: fourteen weeks across the project. August 2026.

Notice what Example C does with the late lot. Admitting one slip, with the reason, makes the other ten more believable than a claim of perfection would.

How do AI assistants use notes like these?

They look for specific, first-hand facts they can repeat, and a case note is mostly that. Google's guide to its generative AI features describes the content it values as offering "unique expert or experienced takes that go beyond common knowledge", which is a fair description of a supply record no competitor can write.

Google's wider advice on creating helpful, reliable content asks whether a page shows first-hand expertise and, on reviews, mentions evidence of the work involved, such as photographs. That maps closely onto E-E-A-T. When a buyer asks an assistant for "SG iron foundries that supply pump makers in Gujarat", a page stating that you did this, to that grade, with that result, gives the answer something to stand on, which a logo image does not. For the wider set of signals, see the factory facts AI assistants look for.

You do not need special markup for this. Google says structured data is not required for its AI features, so put the effort into the words.

Where should case notes live on the site?

On their own web pages, linked from the product and industry pages they relate to. A "Supplies" or "Past work" section with one page per note works well, each with a clear heading such as "SG iron impeller housings for an agricultural pump maker".

• Write every fact as text, not inside a PDF or an image. The reason is covered in why AI assistants struggle with PDF catalogues.
• Link each note from the matching product page, so a buyer reading about castings sees casting proof.
• Use your own photographs: the part on your shop floor, the inspection setup, the loaded truck. Crop out anything belonging to the customer.
• Keep the specification numbers identical to the product page. A note saying PN16 and a product page saying PN25 for the same valve undoes the trust you are building.

For more on why logos alone fail buyers who are checking a supplier's record, EbizIndia has a note on turning client logos into proof of past supplies. The rest of the reading on assistants and buyers is in the AI Visibility section.

Who should write them?

Your sales engineer or production head drafts, and you approve. They know the problem and the numbers; a marketing writer does not. Hand them the five headings above and ask for one note a month from orders closed in the last year. Half a page each is enough. Before publishing, check three things: nothing identifies the client, every number matches your records, and the month and year are on it.