Skip to content
← All articles

Notes for owners · Sales management

Selling to Pune auto-component makers and to Nashik engineering buyers

What a supplier needs on one page before a Chakan vendor development engineer or a Satpur purchase manager will talk: approval status, sample terms and a named contact who answers when a line stops.

The GullySales team · Updated 17 Oct 2026 · 6 min read

Editorial illustration for Capability presentations
On this page
  1. Two buyers, two first questions
  2. What the Pune vendor development engineer wants on day one
  3. What the Nashik purchase manager wants instead
  4. The one-page profile, top to bottom
  5. For example: a press shop in Ambad
  6. When one page will not get you in
  7. Fit your plant on one side of A4

A Pune auto-component maker and a Nashik engineering buyer both want three things before they will send you a drawing. Who has already approved you? What will a sample cost them in time and money? And who picks up when something goes wrong on their line? Put all three on one page, in that order, and hand it over before any brochure. The Pune buyer reads it as a vendor development file. The Nashik buyer reads it as proof you can handle small, varied orders.

Two buyers, two first questions

Both buyers work in MIDC estates a few hours apart on the Pune to Nashik road, in Maharashtra. In Chakan, Bhosari and Ranjangaon, a tier-1 or tier-2 maker supplies a vehicle plant on a schedule that cannot slip. In Satpur, Ambad and Sinnar, an engineering firm makes pumps, machinery or fabricated assemblies in smaller batches, often to its own designs.

So the first question differs. The Pune engineer asks, "Who else in auto has approved you?" The Nashik purchase manager asks, "Can you do forty pieces of this, and twelve of that, by next week?"

What the Pune vendor development engineer wants on day one

The person you meet in Pune is usually from vendor development or supplier quality, not purchase. Purchase comes later, at the rate. The job is to add a vendor without adding a risk to a line that runs three shifts.

The engineer wants your approval status first: which auto customers you supply, at what tier, and which quality certification you hold, with its validity date. Many auto buyers ask about an auto-sector quality certification. If you hold one, put it at the top. If you are working towards it, say only what is true and where you are.

Then come your sample terms. How many pieces in the development lot, how soon from receiving the drawing, what reports come with them, and who bears the cost. The last ask is the one suppliers forget: a name and a mobile number that answers at two in the morning when a part is rejected on the line.

What the Nashik purchase manager wants instead

In Nashik the buyer is often the purchase manager and sometimes the owner, who may know half the vendors in Ambad personally and ask a colleague about you before calling.

The concern is less auto approvals and more range and flexibility. Can you handle many part numbers in small quantities? Will you hold finished stock against a schedule? Can you take job work on the buyer's material? The same named contact matters, for a different reason: quantities change by phone, not by email.

The one-page profile, top to bottom

Keep it to one side of A4, readable on a phone as a PDF. The order matters, because the engineer stops reading once the answer is found.

  1. The top line. What you make, in parts not adjectives: "Pressed and welded brackets and sub-assemblies in CRCA and HR sheet, 1 to 6 mm."
  2. Machines and range. Press tonnages, welding and finishing, inspection equipment, the largest part size and the shifts you run.
  3. Who you already supply. Customers by name only with permission, otherwise by description, with tier and the approval you hold.
  4. Samples. The development lot size, the time from drawing to parts, the reports enclosed and your cost terms.
  5. Who picks up. A named quality head with a mobile number and the hours it is answered, plus the shift in-charge for nights. Then one commercial contact and the works address.

Leave out the vision statement, the founder's message and the photograph with a minister. They push the answers below the fold. The fuller deck comes after the first meeting. The registration papers that follow approval are a separate job, set out in the vendor folder.

For example: a press shop in Ambad

Imagine a sheet-metal press shop in Ambad, Nashik, supplying brackets to two local engineering firms for years and wanting its first Chakan customer. The details are illustrative.

The owner emailed a sixteen-page company brochure to a vendor development engineer at a Chakan seat-frame maker. It opened with the founder's story and a group photograph. The press list was on page eleven. The only contact was the office landline, which nobody answers after six. The engineer did not reply.

The brochure had answered questions the engineer never asked and hidden the three that were. So the owner rebuilt it as one side of A4. Press tonnages and sheet range went to the top. The two Nashik customers appeared by description, and both agreed to take a reference call. A development lot of fifty pieces, at the shop's cost, was offered against any drawing. At the bottom sat the quality head's mobile: "answered six in the morning to eleven at night; the night shift in-charge after that". The owner sent the page with a two-line WhatsApp asking for fifteen minutes at the plant gate. This time the engineer asked for a drawing. It was for a bracket in a sheet grade the shop did not stock, so the sample came two weeks late and the Chakan buyer sent a second drawing only after the lot was approved. The fifty pieces cost the shop about ₹30,000 (an invented figure).

When one page will not get you in

A one-page profile opens a conversation. It does not replace the approvals a buyer requires. If a tier-1 maker needs documented process approval you cannot yet produce, start with tier-2 and tier-3 makers and with Nashik firms, and come back with a track record.

Some large buyers only issue enquiries through their supplier portals or formal RFQs. There, the page gets you invited, and the bid itself is a different discipline; RFP and tender management covers that side.

In Nashik the page matters less than the name behind it. An Ambad owner who already knows your family will ring a colleague before reading anything. Send the page after that call, not instead of it.

Fit your plant on one side of A4

Write the top line first, in parts and sheet range, not adjectives. Then list the presses and approvals, and name the person who answers at night. If it spills onto a second side, cut the history before you cut a machine. One side is the whole test. Building the page is capability presentations work; tell us what you need to start.

Questions

Questions owners ask.

Should the profile name the companies we already supply?
Only with their written permission. Without it, describe them so the engineer can place you: a tier-1 seat-frame maker in Chakan, a pump maker in Satpur. A named customer you were not allowed to name can cost you that customer and the new one.
Who pays for a development sample?
It is negotiated, and practice differs by buyer and by part. Many small suppliers absorb a small development lot to get in, while tooling is discussed separately. Put your own terms on the page so the engineer does not assume the worst and move on.
Do we need separate profiles for Pune and Nashik buyers?
One page with the same top and bottom, and a middle block you swap. The Pune version leads with approvals and sample terms. The Nashik version leads with the range of small batches you handle and how fast you turn a drawing into a part.
Should we register on a buyer's supplier portal before anyone has met us?
Register when the buyer asks you to, usually after the first conversation, because a portal entry nobody has sponsored rarely gets an RFQ. Keep your login, documents and contact details current there, and check the portal's own terms before you upload anything.

From the blog

More notes for owners.

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.