Is that Korean inquiry a project or a budget check? How to tell before you quote

An inquiry arrives from Korea. Model number, quantity, delivery date, and a request for your best price. You quote, carefully, and hear nothing. Six months later a similar inquiry arrives from the same address. The first one was never a purchase — it was a number being collected for a budget, and it was worth more attention than you gave it, not less.

Capital spending runs on an annual cycle

Korean manufacturers manage equipment investment inside annual budget envelopes. An item that is not in the envelope is difficult to approve, however small the amount.

That produces two distinct kinds of inquiry, several months apart. In the first, someone is building a number so the item can be entered into next year's plan. In the second, the envelope exists and the purchase is being executed.

Both arrive looking identical, because both come from the same address in the same format. Treating them the same is where the effort goes wrong: the budget inquiry gets a rushed number, and the procurement inquiry gets the same level of detail when it needed more.

A third factor sits behind both: the type of investment. Capacity expansion depends on the demand outlook and can be deferred; replacement of ageing equipment and anything driven by safety or environmental requirements is harder to postpone. Which category your product falls into changes how firmly the line item sits in the plan — and the same machine can be presented either way depending on what the buyer needs to justify.

The signals that separate them

You can usually tell within one exchange, and often from the message itself.

The document list is the most reliable single indicator. Nobody attaches a document schedule to a budget inquiry, because the documents cost money and nobody is spending yet.

Just ask

The efficient move is to ask directly: "Is this for investment planning or for a current procurement?" This is a normal question in Korean industrial practice and it gets a straight answer.

Asking does not make you look unserious. It signals that you know how the buying cycle works, and it lets the sender give you what you actually need — which is often a relief to them, because they know the inquiry was thin.

The one thing to avoid is asking it in a way that implies you will work harder on a real order. Frame it around what you will send: "so I can send either an indicative budget figure with assumptions, or a full quotation with the document scope priced in."

What a budget inquiry actually needs

A planning number does not need engineering precision. It needs to be defensible, bounded, and usable inside someone else's document.

Give a figure with explicit assumptions: the configuration you priced, what is included, what is excluded, and the validity of the number. A budget figure without assumptions is dangerous, because it will be treated as a commitment when the project becomes real — and the person holding you to it will not be the person you sent it to.

Include the things that move the total later: installation supervision, commissioning, spare parts for the first period, documentation, and any certification work. These are the items that appear as "extras" at procurement stage and cause the budget to fail, which is a bad outcome for both sides.

Currency deserves a line in a budget figure too. Between the planning cycle and the eventual order there can be a year or more, and an exchange rate moves in that time. A number quoted without stating the currency basis and its validity becomes, in the buyer's file, simply a price — and any later increase reads as a price rise rather than as a rate movement. One sentence naming the currency and the assumption avoids that conversation entirely.

Why the budget stage is worth more

There is a counter-intuitive point here. The inquiry with no deadline and no specification is often the more valuable one.

The number that goes into the budget is usually built from one supplier's figure. The technical assumptions behind it frequently become the outline of the later specification. If your configuration is what was costed, the eventual tender describes something close to your product — and competitors price against a scope that was shaped by you.

The reverse is also true. If a competitor's figure built the envelope and yours is higher, you are not expensive; you are outside the budget. That distinction is invisible from your side, and it explains a lot of lost bids that looked like price losses.

Neither, sometimes: the benchmark inquiry

A third case exists. Occasionally an inquiry is neither planning nor procurement but a price check — someone confirming that an existing supplier's quotation is reasonable, or building a comparison for an internal argument.

The tells are a specification that reads as if it were written around a specific competitor's product, an unusually short deadline with no project context, and no interest in your technical questions. Requests for a detailed breakdown without any discussion of scope point the same way.

This is not a reason to refuse. It is a reason to calibrate effort: send a clean, complete quotation without investing in a custom engineering study. And it is worth noting for later — an organisation that benchmarks you this year has your details on file when the incumbent disappoints.

Keep the budget inquiry alive

Between the two stages there are months in which nothing visible happens. Most suppliers do nothing during them, which is why the second inquiry so often goes to whoever was in contact most recently.

Two things are worth doing. Confirm the validity window of your figure and offer to refresh it before the planning cycle closes — a legitimate reason to make contact with a date attached. And send anything that strengthens the case for the item itself: a reference with comparable data, a payback calculation, a note on regulatory drivers.

That second point matters because your contact has to defend the line item internally against other projects. Material that helps them argue for the investment is material that keeps your configuration inside the envelope.

Two different internal readers

The two stages are read by different people, and the documents should differ accordingly.

A budget figure is read by whoever approves the plan. They want scope, magnitude, timing and risk — one page. A procurement quotation is read by an evaluator building a comparison table, one column per supplier. There, structure matters more than persuasion: answer in the order the inquiry asked, so your figures can be transferred without interpretation.

Sending a procurement-grade document at budget stage buries the number. Sending a budget-grade document at procurement stage looks incomplete and gets scored as such.

Silence after a budget inquiry is the normal state

The expensive misreading is not mistaking one stage for the other. It is concluding from silence that there was no interest.

After a budget inquiry, silence is the normal state. The plan is being assembled, competing items are being weighed, and approval sits above your contact. Nothing will be said to you until the envelope is settled, which can take months — and during that time your contact genuinely has nothing to report.

Suppliers who read that silence as rejection stop following up, remove the contact from their list, and are surprised when the tender appears without them. The ones who treat it as a known quiet phase — and who check back once, with a reason and a date — are the ones still in the file when it reopens. If you have an inquiry in front of you and cannot place which stage it is at, we can look at what the wording suggests and what to send back — talk to us about sourcing. How the decision then moves internally is covered under vendor registration.