The referral model: introduce the opportunity, keep your role.

A referral is one sentence that arrives with context: who the customer is, what hurts, and why they would listen to you. Everything after that — the qualification, the design, the quote, the delivery — runs through us. You stay in the role you already have.

01 / 모델의 형태

이렇게 맞을 때
가장 좋습니다.

가장 좋은 경우 you know the customer and the problem, and you do not want to deliver hardware.

This model exists for consultants, adjacent suppliers, facility and systems people, and anyone whose relationship with a customer is trusted but is not a hardware business. If the customer would be surprised to receive a quote from you for readers and tags, the referral model is the right shape: the commercial relationship runs to the party that can actually carry it, and your part — getting the right conversation started — is treated as the contribution it is.

프로그램 페이지에서 세 가지 모두 비교

You introduce the opportunity and stay in your own role.
We run the technical and commercial process with the customer.
Your introduction is acknowledged, and the terms of that acknowledgement are stated in the agreement.
The customer relationship stays with whoever owns it — we do not use an introduction as a route to go around you.

02 / 누가 무엇을 맡는가

양측 사이의
경계선.

여러분이 맡는 것

소개와 그 배경

The introduction, and the context that makes it useful: who decides, what the operation is trying to see, what has already been tried or rejected.
An honest read of the customer’s appetite. A warm introduction to a cold buyer wastes everyone’s time; tell us what you actually know.
Being reachable if the pursuit needs something only you can supply — a second introduction, a correction to the context.

우리가 맡는 것

이 모델에서 우리가 지는 책임

Qualification: whether the problem is RFID-shaped at all, and what the honest alternative is if it is not.
The technical and commercial process end to end — item review, testing, configuration, quote, delivery and support.
Status on the opportunity you introduced, for as long as the pursuit is live.

여기에 있는 어떤 것도 수락이 가능한 제안이 아닙니다. 마진, 담당 지역, 딜 등록, 지원 의무는 파트너별·시장별로 협상되는 서면 파트너 계약에서만 존재합니다.

03 / 다른 모델과의 비교

같은 결정,
세 가지 방식.

모델을 고르는 것은 비교하는 것이므로, 모든 모델 페이지에 이 표가 있습니다. 지금 읽고 있는 열이 표시되어 있습니다.

	Referral (이 페이지)	Reseller	Solution partner
고객과 청구	We hold the customer for this scope; your introduction sits beside that relationship.	Yours, entirely — the quotation and the invoice are your documents, not ours.	Yours, including the design and the delivery decision.
기술적 소유권	All of it — qualification, testing, configuration, delivery and documentation.	Yours, with our pre-sales support before the close and escalation behind it.	You design and integrate; we validate the read, confirm the variant and supply the equipment.
지원 경로	The customer is supported by us directly; you stay out of the escalation path.	You at first line, us on the technical escalation path you define in your agreement.	You on site; escalation reaches a named engineer rather than a queue.

04 / 의무

이 모델이 양측에
요구하는 것.

이것은 모든 파트너가 하는 일(지명된 기술 담당자, 정직한 보고, 인증 경계 존중) 위에 더해집니다. referral에 특화된 부분입니다.

여러분의 몫

Do not quote or commit on our behalf. The moment an introduction turns into a promise, it has stopped being a referral.
Tell us if the customer already has another vendor working the same scope. We would rather know before the first meeting than discover it in the room.

우리의 몫

The acknowledgement is agreed before the first introduction is made, and it is written into the agreement — not left to goodwill.
An introduction is never used as a route to go around you at that account.
You hear how the pursuit ended. A no is still an answer, and you are owed one.

05 / 좋은 시작

좋은 첫 지원이란
어떤 모습인가.

The kinds of accounts you reach and the sectors you are actually trusted in.
Whether a live opportunity is already in front of you, or whether you are deciding how you would want to work with us in general.
How you would like the acknowledgement handled — many partners want it discussed in writing before the first name changes hands, and that is a fair starting position.

지원해도 파트너 관계가 만들어지지 않으며, 양식 뒤에 자격 기준은 없습니다. 유용한 신호는 정직하게 설명된 실제 상황입니다.

referral 파트너로 지원하기

06 / 자주 묻는 질문

일찍 물어볼
가치가 있는 질문.

Do I need to be an RFID company to refer?

No. Most useful introductions come from people who know the customer’s operation and none of the technology. We qualify the opportunity; your job is the context, not the configuration.

What does an introduction have to include to be protected?

The customer name, the scope you heard about, and enough context that we can tell whether the pursuit is live. Vague leads are not registrations. The mechanics of how an introduction is logged and acknowledged are agreed and written down before the first one happens.

What if the opportunity does not go anywhere?

Nothing is owed either way, and there is no minimum. A referral relationship that only counts wins is not a relationship — we would rather you kept sending the honest ones.

지원 전에

이웃 모델과 나란히
읽어 보세요.

RFIDBRIDGE / 파트너

실제
기회를 가져오세요.

첫 대화는 회사 프로필보다 실제 고객 상황이 더 유용합니다. 둘 다 환영하지만, 전자가 더 빠르게 진행됩니다.

지금 지원

The referral model: introduce the opportunity, keep your role.

이렇게 맞을 때가장 좋습니다.

양측 사이의경계선.

같은 결정,세 가지 방식.

이 모델이 양측에요구하는 것.

좋은 첫 지원이란어떤 모습인가.

일찍 물어볼가치가 있는 질문.

이웃 모델과 나란히읽어 보세요.

실제기회를 가져오세요.