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.

PARTNERS / REFERRALONE OF THREE MODELSTerms live in a written partner agreement, not on this page.

01 / THE SHAPE OF IT

Best when
it fits this way.

Best when 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.

Compare all three on the programme page
  • 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 / WHO HOLDS WHAT

The line between
your side and ours.

YOU OWN

The introduction and its context

  • 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.
WE OWN

What we are accountable for under this model

  • 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.
Nothing here is an offer capable of acceptance. Margins, territory, deal registration and support obligations exist only in a written partner agreement, negotiated per partner and per market.

03 / AGAINST THE OTHER MODELS

The same decision,
three ways.

Every model page carries this table, because choosing a model means comparing it. The column you are reading is marked.

  Referral (this page)ResellerSolution partner
Customer and invoice 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.
Technical ownership 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.
Support path 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 / THE OBLIGATIONS

What this model
asks of each side.

These sit on top of what every partner does — a named technical contact, honest reporting, respect for the certification boundary. They are the parts that are specific to referral.

OF YOU

  • 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.

OF US

  • 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 / STARTING WELL

What a good first
application looks like.

  • 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.

Applying does not create a partner relationship, and there is no qualifying threshold behind the form. The useful signal is a real situation described honestly.

Apply as a referral partner

06 / FAQ

Questions worth
asking early.

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 / PARTNERS

Bring a real
opportunity.

A first conversation is more useful with a live customer situation attached than with a company profile. Both are welcome; one moves faster.

Apply now