Partners • lanes • Deal ID • RID continuity

Partner motion built for procurement and scrutiny

Partner routing for opportunities, portfolio programs, delivery, and integrations. Output stays board-readable and evidence-first, with tracking anchored to a Request ID (RID).

Evidence discipline
Board formatting
Procurement-safe motion
RID continuity
Register a partner deal Ecosystem programs Partner intake Status Gate
Procurement (Invoice/PO) Partner structure Notes
Tracking key: — stays attached across Gate, Procurement, Status, and submissions. Public pages are non-confidential by design.
Deal Registration Programs Lane Procurement Lane

Partner Deal Registration

Generate a Partner Deal ID, capture progression signals, and route the buyer cleanly. Protection is 90 days from Noetfield acceptance (Deal Accepted email), subject to the terms below. Target: 1 business day • SLA: 2 business days.

Open deal registration Portfolio / programs Invoice / PO lane

Deal protection terms (compact)

Designed to reduce channel conflict and keep co-selling defensible. Acceptance is confirmed by email after basic validation.

Acceptance
Protection begins when Noetfield sends a Deal Accepted email after validating minimum fields.
Protection window
90 days from acceptance, provided progression signals remain current.
Minimum fields
Org name, champion role, stage, next-step date, lane, acknowledgements, and a short non-confidential note.
Review SLA
Target 1 business day • SLA 2 business days (Accept / Clarify / Decline).
Conflicts
First complete registration timestamp plus progression signals (meeting scheduled/held, lane confirmed).
Scope boundary
Protection applies to the named organization and registered opportunity; public tenders may override.
Public boundary: do not submit credentials, tenant identifiers, customer content, or regulated personal data. Sensitive context begins only after NDA + executed SOW (via Procurement lane).

Tiers (public-safe)

Tiers govern partner involvement. Commercial terms (rates/bonuses) are provided under the partner agreement.

  • Referral — warm intro and routing discipline.
  • Channel — active co-selling support through qualification and buyer routing.
  • Prime Channel — partner-sourced account + two buyer-side meetings + close support through signature and payment/PO.
  • Delivery — deliver Noetfield artefacts under evidence discipline (RACI aligned).
  • Integration — implement controls (M365/Purview posture, connector governance, enforcement + audit hooks).
Net Fee concept: partner compensation is computed on fees excluding taxes and pass-through costs (defined in agreement). Payment triggers after client funds clear.
Deal

Register & protect

Issue a Deal ID, capture progression signals, and route the buyer with procurement-safe language.

  • Deal ID + RID continuity
  • Progression signals: meeting + lane confirmed + close support
  • Routing: Gate → Procurement → Status

Protection: 90 days from Noetfield acceptance (Deal Accepted email).

Deal registration Procurement lane
Channel

Originate

Introduce aligned organizations and keep the buyer path clean from first touch to procurement.

  • ICP-aligned intros (Microsoft-heavy, governance + procurement pressure)
  • Clear buyer routing: Gate → Procurement → Status
  • Boundary discipline (public vs post-kickoff)
Channel lane Register deal
Programs

Portfolio routing

Accelerators and studios: cohort-ready governance outputs that reduce procurement friction.

  • Two models: program contract or company-by-company
  • Standardized artefacts (snapshot + memo format + evidence index starter)
  • Optional anonymized cohort summary (non-confidential)
Programs lane Portfolio offer
Delivery

Deliver

Deliver Trust Brief / Trust Ledger outputs with evidence capture and board-ready writing.

  • Board memo + MAP discipline (Owner / Due / Evidence ID / Status)
  • Fixed-scope habits + measurable acceptance checks
  • Red-line escalation for privacy/security/procurement blockers
Delivery lane Partner intake
Integration

Implement controls

Wire identity, logging, DLP, retention, and enforcement so claims remain provable over time.

  • M365/Purview posture hardening (DLP, retention, audit)
  • Connector governance + least-privilege patterns
  • Operational evidence hooks (exports, labels, audit trail)
Integration lane Partner intake

Partner Pack (request)

Positioning, routing rules, and public-safe tier definitions.

Request pack Partner intake

Pack is issued after intake validation. RID is included automatically.

Co-sell play (request)

Warm intro templates + procurement-safe language + RID-preserving routing links.

Request co-sell play Procurement lane

Procurement teams should use Invoice/PO lane, not partner intake.

Programs Pack

Portfolio offer overview for accelerators, venture studios, and scale-up programs.

Open portfolio offer Programs lane

Use non-confidential cohort nomination workflow.

Standards (non-negotiables)

Rules that keep delivery quality defensible.

  • Public = non-confidential: no secrets/credentials/customer data/regulated personal data in forms.
  • Named artefacts: memo/control taxonomy/evidence index formats remain consistent.
  • Evidence IDs: material claims require traceable references (export, screenshot, policy, log).
  • Red-lines: escalate blockers fast (privacy/security/procurement) and document disposition.
  • RID discipline: use RID in subjects, filenames, and status checks.

Onboarding flow

Fast validation, then lane activation.

  • Step 1: Partner intake (high-level, non-confidential).
  • Step 2: Lane fit + scope boundaries confirmed.
  • Step 3: Enable routing pages + handoff checklist + evidence patterns.
  • Step 4: Operate with RID tracking and Status visibility.

For procurement (Invoice/PO): Procurement lane.
For portfolio programs: Programs lane.

Partner FAQ (compact)

What counts as acceptance for protection?
Protection starts when a Deal Accepted email is issued after minimum fields validate (org, champion role, stage, next-step date, lane, acknowledgements).
What happens if two partners register the same organization?
Resolution uses first complete registration timestamp plus progression signals (meeting scheduled/held, lane confirmed).
Where should procurement teams go (Invoice/PO)?
Route to Procurement (Invoice/PO) for vendor onboarding, purchasing lanes, and procurement pack.
How does the Programs lane work?
Two models: program contract (portfolio package) or company-by-company routing. See Programs lane.
Decision rule: repeatable delivery, clean scope boundaries, and evidence capture habits that scale.
A strong partner makes a board decision easy and a regulator conversation calm.