For manufacturers
Log of search for first corporate customers
Where production should look for its first corporate customers, how to verify the presumed need, and how to write an outreach message with a specific reason for the conversation.
How to use
- Select a customer segment and formulate a demand hypothesis.
- For each company found, create a journal entry with the source and date.
- Justify the contact with a specific task, not a mass mailing.
Result: log of reasons, responses, and next actions.
Working files
Files are available without registration. Save a copy and fill in your company details. Downloadable files are in Russian; the instructions on this page are translated.
Register a company from ChinaLog of search for first corporate customers
Purpose: to select companies based on a verifiable reason for contact and then record the outcome of the conversation.
Our offer
- Products or operations: [list].
- Materials and constraints: [verified information].
- Order format: [one-time/small batches/repeat batches].
- Source data for evaluation: [list].
- Supporting materials: [what may be shown].
- Contact for technical questions: [details].
Candidate log
| Company and Tax ID | Basis for inquiry | Our suitable job | Contact and action | Result |
|---|---|---|---|---|
| [data] | [fact, reference, date] | [specific proposal] | [to whom; question; deadline] | [need confirmed/no/clarification needed] |
| [data] | [data] | [data] | [data] | [data] |
For a completed project, mark separately that the source is historical. Do not present a hypothesis about a need as a known fact.
First letter
Good afternoon. On your website [link], [product/project] are presented. Our production performs [specific work], which may relate to this area. Please let us know whether you consider external contractors for such tasks and where to send the capabilities sheet? It specifies [operations, materials, limitations, evaluation procedure]. Contact for discussion: [details].
What to consider after the inquiry
- Need identified: [date, response].
- We have received the documentation: [list and versions].
- Calculation prepared by: [number, date].
- Terms are under discussion: [open questions].
- Reason for stopping: [no task / another technology / batch / other answer].
- Next action: [what, who, deadline].
What the first work log looks like
Let's continue with the training example. These are fictional actions and responses, not the result of outreach to real companies. The workshop had previously selected series of shafts and bushings based on ready-made drawings; it did not include custom part development based on a sample in the quotation.
| Date and company | What we found out | Next action |
|---|---|---|
| October 1, component manufacturer A | In the training response, consideration of external contractors was confirmed; requested the capabilities profile | Send the card on October 2, clarify the documentation format |
| October 2, repair company B | No drawing; development is needed based on a worn sample | First find out who is responsible for documentation; do not promise manufacturing price |
| October 2, manufacturer B | A request to assemble a cabinet was found; no turning work was found | Exclude from this selection; do not consider any procurement request as an indication of demand for bushings |
A has the next conversation. B has a task outside the original proposal. C is excluded due to a mismatch with the subject. None of these records means an actual order received. The log is needed to see which action is justified today and not repeat an unsuitable approach.
Sources and limitations
- Federal Tax Service: Transparent Business — The availability of legal entity search was checked; demand for services is not determined by this service. Checked: .
Next step
Updated: . Training examples do not confirm experience in fulfilling a real delivery.