Partner referral terms

Warm intros with clear economics and relationship protection.

You keep the client relationship. MLDeep scopes and ships the technical data, AI, analytics, and automation layer behind the client problem.

Use this page when you have a client who needs a senior technical operator for CRM-to-warehouse reporting, AI readiness, data foundation repair, production workflow automation, or a 90-day retained execution path.

Send a client scenario Book partner fit call

Best first step: send one current client scenario. We will reply with good intro, bad fit, or different owner.

Commercial paths

Pick the contract shape before the client intro.

Path When to use it Partner economics
Direct client engagement MLDeep contracts directly with the referred client. 10-15% of the first paid engagement. Default is 15% for a strong warm intro with useful context.
White-label delivery Your firm owns the client contract and invoices the client. You mark up MLDeep's scoped fee. The commercial relationship stays under your brand.
Joint proposal Both firms appear in the scope with a clear role split. Fee split agreed before the scope is sent to the client.
Reciprocal referral Both sides can send better-fit work to each other. No cash fee unless agreed in writing before the intro.

Payment trigger

The referral fee is owed only after a warm introduction leads to a signed or approved first paid MLDeep engagement, MLDeep receives the client's first payment, and the partner is logged as the referral source before the first scope note is sent. Payment is made within 30 days of MLDeep receiving payment.

Best-fit referrals

Send situations where the technical layer is blocking the business decision.

Strong referral signals

  • The client already trusts you.
  • There is a named owner and near-term trigger.
  • The pain touches CRM, warehouse, BI, APIs, automations, reporting, or AI readiness.
  • Your current scope stops before technical implementation.
  • The client can approve a $5,000-$8,000 sprint, $15,000 audit, or retained execution path.

Weak referral signals

  • "They might need AI" with no named workflow.
  • No buyer, owner, urgency, or budget path.
  • Pure dashboard maintenance.
  • Procurement-led RFP with no partner influence.
  • Client wants a large bench, SOC 2 vendor, or staff augmentation.

Useful client context

  • Who owns the decision?
  • What workflow, data issue, or AI question is stuck?
  • Why does this matter in the next 30-90 days?
  • Which systems are involved?
  • What budget shape is realistic?
Relationship protection

The role split is written before any client work starts.

Partner owns

  • Client relationship
  • Strategic framing
  • Business process authority
  • Stakeholder communication outside the technical scope
  • Renewal or expansion conversations for partner-owned work

MLDeep owns

  • Technical scoping
  • Data, API, and workflow implementation
  • Technical documentation
  • Risks and tradeoffs inside the technical scope
  • Delivery handoff for MLDeep-owned work

MLDeep commits to

  • Acknowledge every referred lead within 1 business day.
  • Reply to the referred client within 1 business day after the intro lands.
  • Give the partner a short fit-call update.
  • Decline bad-fit work instead of forcing a project.
  • Never pitch partner-owned services to the referred client.
Next step

Send one current client scenario.

The fastest way to test partnership fit is not a broad capabilities call. Send one real client situation, the systems involved, the owner, urgency, and what decision is stuck.

Send a scenario Book partner fit call

Responds within one business day · calls run 17:00-22:00 IST / 07:30-12:30 ET · no slide deck.