Planning a Supplier Introduction Meeting Around San Techno's Published Background

Why a short introduction meeting needs a plan

A supplier introduction meeting is easy to schedule and surprisingly easy to waste. Forty-five minutes pass quickly when the first ten are spent finding the right document and the next ten are spent asking questions the supplier's public pages already answer. For a Singapore procurement team sourcing, receiving and documenting semiconductor and solar materials, the meeting is usually the first structured contact with a supplier, so it carries more weight than its length suggests.

The useful approach is to treat the supplier's published background as preparation material, not as the agenda. Read what the company says about itself, note what is relevant to your sourcing situation, and then build a short agenda around the gaps. That keeps the conversation focused on your requirements rather than on a general company tour.

San Techno Pte Ltd is a Singapore-based company working in semiconductor and solar materials, silicon recovery, specialized power module development, and botanical extracts under the ST GREEN brand. That breadth is itself a planning consideration: a single meeting cannot cover every branch, so decide in advance which part of the business your enquiry actually touches.

Start with the published background, not the pitch

Before the meeting, spend twenty minutes on the supplier's own material. The About page is the natural starting point because it usually explains how the company describes its history and its current focus. For San Techno, the published background states that the company was incorporated in 2006 and began as a wholesaler and distributor of semiconductor- and solar-grade silicon materials. It also describes a continuing role since 2006 in semiconductor and solar materials, specialized power-module designs and biological solutions.

Those two statements are useful anchors for an introduction meeting. They tell you the company frames itself as long-established in materials distribution and as having expanded into other areas. What they do not tell you is anything about your specific requirement, your volumes, your specifications or your timelines. Keep that distinction in mind when you draft questions.

A simple preparation note works well: list three things you learned from the public background, three things you still need to ask, and one thing you want the supplier to confirm in writing afterwards. This is an author heuristic, not a formal method, but it keeps the meeting from drifting.

A fictional 45-minute agenda you can adapt

The following agenda is an example only. Adjust the timings to your own meeting length and to how many people attend.

Minutes 0 to 5: introductions and purpose. State plainly what your team sources and what you hope to learn. Ask the supplier to confirm who is attending and which part of the business each attendee represents.

Minutes 5 to 15: supplier background in the supplier's own words. Invite a short summary of how the company describes its history and current activities. This is where the published background helps you listen actively rather than take notes blindly.

Minutes 15 to 30: your requirement. Describe the material category, the documentation you typically need and the questions your internal stakeholders will ask. Leave room for the supplier to say what they can and cannot address.

Minutes 30 to 40: open questions. Use the gaps you identified during preparation.

Minutes 40 to 45: next steps and owners. Agree who sends what, and by when, without committing to dates you cannot keep.

If your enquiry touches silicon recovery, the published background notes that San Techno helps recover non-usable silicon from integrated-circuit fabs, silicon wafer manufacturers, solar cell companies and chip packaging facilities. That is a useful prompt for a question about which sources the supplier typically works with, but it is not a substitute for asking about your own material stream.

Separating who attends from what must be confirmed

One of the most common sources of confusion after an introduction meeting is the difference between a person's role and a company's position. A meeting attendee may speak knowledgeably about a topic without being authorised to confirm it on behalf of the company. Build this into your notes.

A practical split looks like this. In one column, record who attended and which part of the business they represented, based only on what they said in the meeting. In a second column, record the company history points you intend to rely on, and mark each one as either confirmed in the meeting or still to be confirmed in writing. Do not merge the two columns.

The published background offers a clear example of why this matters. It attributes the founder role to a named individual and separately describes company-level activities. Treat the personal attribution as belonging to that individual, and treat the company statements as company statements. If your documentation needs a company-level confirmation, ask for it rather than inferring it from who was in the room.

This is a documentation habit, not a mandatory check. Use it where your own process requires a written record.

Questions that suit a first meeting

A first meeting works best when the questions are broad enough for the supplier to answer without preparation but specific enough to be useful. The following are examples, not a required list.

Ask how the supplier describes its current focus areas and which of them are relevant to your enquiry. Ask which parts of the published background are current and which describe earlier phases of the business. Ask what documentation the supplier typically provides at an early stage of an enquiry. Ask who within the company would own your enquiry after the meeting.

Where your interest is in power modules, the published background describes an intelligent IGBT power-module concept centred on double-sided cooling for an EconoDUAL 3-class package format, and notes that detailed architecture, materials, dimensions and assembly processes remain confidential. That is a useful thing to know before the meeting: you can ask about the programme's focus without expecting technical detail to be disclosed. The same background describes custom double-sided cooling power modules developed with industry specialists for high-voltage and high-temperature applications where durability is essential.

For botanical extracts, the published background describes ST GREEN as a brand owned by San Techno and as a botanical concentrate derived from plant, seed and vegetable-oil extracts. If your enquiry is in that area, ask which formulations are relevant to your market rather than assuming a fit.

What to leave out of the first meeting

A short introduction meeting is not the place for a full technical review, a commercial negotiation or a site assessment. Trying to cover all three usually means none of them is done well.

Leave pricing structures, volume commitments and delivery schedules for a later conversation once both sides understand the requirement. Leave detailed technical specifications for a session with the relevant technical stakeholders present. Leave any question that depends on confidential information, because the supplier may not be able to answer it and the meeting will stall.

The published background is explicit that some power-module detail remains confidential, which is a helpful reminder that not every gap in public information is an oversight. Where information is withheld, note it as an open item rather than pressing for it in a first meeting.

It also helps to avoid treating public statements as verified performance claims. The published material describes what the company says about itself; your own due diligence sits alongside it, not inside it.

Closing the meeting with a usable record

The value of an introduction meeting is largely in what survives it. Within a day, write a short record covering the attendees and the parts of the business they represented, the questions asked, the answers given, and the items still open. Keep sourced statements separate from your own notes.

Where a statement came from the supplier's published background, note that it is a public statement rather than a meeting confirmation. Where a statement was made in the meeting, note who made it. Where a statement is still unconfirmed, mark it clearly so that a colleague reading the file later does not mistake it for settled.

If your team needs a follow-up conversation, the supplier's own contact route is the appropriate channel. The published material lists a phone number and a WhatsApp number for direct contact, and the company describes its base as Singapore. Use the channel your own procurement process recognises rather than improvising one.

Finally, review the agenda against what actually happened. If a section ran long or a question went unanswered, adjust the next meeting rather than repeating the same structure. The goal is a short, well-prepared conversation that leaves your team with a clearer picture and a tidy record, not a longer meeting for its own sake.