Most of our work arrives through someone who has already worked with us.
This is how that is handled properly.
Two ways to work with us without becoming a client: send us a requirement you cannot serve yourself, or deliver alongside us on a programme neither of us would take alone. Both are written down before anything starts, which is the only part that actually matters.
A referral and a partnership are not the same thing.
Confusing them is how these relationships go wrong. One ends when the introduction is made. The other runs for the length of a programme.
Refer a requirement
You know a team that needs SAP testing, automation, assurance or consultants, and it is not work you do. You make the introduction; we take it from there and tell you what happened either way. You carry no delivery obligation and sign nothing beyond the introduction itself.
Deliver as a partner
You hold the client relationship and need SAP quality capability behind it — or we hold it and need yours. Scope, ownership, who is client-facing and who invoices are agreed in writing before the first conversation with the client, not after the work starts.
Supply consultants
You are a consultancy or an independent with SAP people on the bench. We share the requirement, you propose, and we tell you plainly whether it went forward. Profiles are never forwarded to a client without your knowledge, and never used to price against you.
What we commit to, and what we will not do.
Referral relationships fail on the things nobody wrote down. So these are written down.
The commercial arrangement is settled before an introduction is made — not negotiated afterwards, when there is a live opportunity and much less room to disagree.
We record who introduced whom, and when. If the same organisation later arrives from a second direction, the first registration stands.
Where you hold the relationship, we do not approach that client independently for the agreed period. This is the clause partners actually care about.
Including when it went nowhere, and why. An introduction that vanishes into silence is worth less than a clear no — and silence is why most people stop referring.
Profiles, client names and requirement detail move only where the person or organisation concerned has agreed. That protects your information exactly as it protects a client’s.
You stay free to refer the same work elsewhere and to work with anyone else. A programme should go where it will be delivered best.
Commercial terms are specific to the arrangement and are agreed directly, in writing, before anything begins — so nothing is published here. Ask, and you will have them before you introduce anyone.
Being clear about the fit saves everyone a meeting.
It works well for: system integrators who need independent quality capability they are not marking themselves on; consultancies strong in one SAP area and asked for another; independents and former colleagues who hear about a requirement they cannot serve; technology and staffing firms who meet SAP quality work outside their scope.
It works badly for: anyone who wants a logo on a website without work behind it, and anyone who needs the arrangement to stay verbal. Both end the same way.
Tell us what you have in mind, and we will send you the terms before you introduce anyone.
Write to contact@rufouss.com with a line about what you do and which of the three arrangements fits. You will get the specifics back, and a straight answer if it is not a fit.
Have SAP consultants on the bench? Send profiles to jobs@rufouss.com rather than here.