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.

ПАРТНЁРЫ / REFERRALОДНА ИЗ ТРЁХ МОДЕЛЕЙУсловия фиксируются в письменном партнёрском соглашении, а не на этой странице.

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 (эта страница)ResellerSolution 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 / ВОПРОСЫ

Вопросы, которые стоит
задать заранее.

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.

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.

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 / ПАРТНЁРЫ

Принесите реальную
возможность.

Первый разговор полезнее, когда к нему приложена реальная ситуация клиента, а не профиль компании. Приветствуется и то и другое; одно движется быстрее.

Подать заявку