IT Distribution · Salesforce Partner Ecosystem Management

How 3Eye Technologies Moved Vendor Onboarding and MDF Tracking Into Salesforce

Built in Phase I on Salesforce Partner Ecosystem Management. 3Eye now approves vendors, tracks agreements, and manages marketing funds in one spot, while NetSuite still runs the finance side.

Outcome Highlights

  • Vendor onboarding, all in Salesforce

    from first intake to activation

  • Forms in place of static PDFs

    cleaner vendor data from day one

  • MDF spend vs. commitment in one view

    for every Marketing Development Plan

  • Vendors see it themselves

    status, documents, and fund usage in a read-only portal

Project at a Glance

Client
3Eye Technologies
Industry
Specialist technology distribution (IT channel)
Headquarters
Battle Creek, Michigan
Salesforce products used
Salesforce CRM, plus Partner Ecosystem Management (PEM)
E-signature
Adobe Acrobat Sign
Systems kept in place
NetSuite stays the financial system of record
Services
Discovery and solution design, configuration, reporting and dashboards, testing and UAT, training, deployment, hypercare
Approach
Phase I (MVP), built with standard Salesforce configuration and no custom code
Timeline
9–11 weeks, plus 2 weeks of hypercare

Summary

3Eye Technologies is a specialist, solutions-led technology distributor. It links best-of-breed vendors with resellers and partners across the IT channel. Growth brought more vendors and more partner programs, and the work behind them ended up scattered across NetSuite, static files, and informal workflows.

Stack Intelligence made Salesforce Partner Ecosystem Management the home for vendor lifecycle work and partner programs. NetSuite still handles billing, invoicing, and payments.

The Challenge

3Eye's partner ecosystem and marketing programs were growing quickly. The processes behind them hadn't kept up.

  • Onboarding was scattered.

    Qualifying a vendor meant hopping between NetSuite, static documents, and email threads. Asking where a vendor stood rarely got a quick answer.

  • Vendor details arrived as static PDFs.

    Each one came in a little different, so checking the data was slow and reporting on it was harder.

  • Agreements were hard to track.

    NDAs, distribution agreements, and required documents weren't stored in one place, and renewal dates were easy to miss.

  • MDF lived in manual records.

    Marketing Development Plan (MDP) commitments and MDF spend were kept by hand. Comparing what was spent to what was promised took real digging.

  • Status checks meant email.

    Without a shared view, every status check meant another email back and forth.

As partner volume kept rising, all of this put extra strain on 3Eye's internal teams.

Our Approach

Phase I had a clear brief. Get the core processes standardized and visible, and track commitments in a way people could trust. We kept the scope MVP on purpose. Nothing was over-automated, and financial work stayed out of Salesforce.

How the project ran:

  • Discovery and solution design

    2 weeks

    We sat down with 3Eye's vendor workflows, data, and process diagrams across NetSuite and other tools. Before any building, both teams agreed on what was in scope and what wasn't.

  • Build

    5 weeks

    Partner Ecosystem Management went on top of the Salesforce platform. That covered workflows and validation rules, the fields to hold vendor data, plus reports and dashboards.

  • Testing, UAT and training

    2 weeks

    Our own QA came first. Then 3Eye ran two rounds of user acceptance testing, and their teams joined four live training sessions built around their roles.

  • Deployment and cutover

    2 weeks

    Configuration froze before launch, and both sides signed off at a Go/No-Go meeting. After the production deploy, we rechecked the vendor approval, onboarding, and MDP workflows.

  • Hypercare

    2 weeks

    We stayed close after go-live. A shared issue log and regular check-ins kept small problems small.

What we built

  1. 01

    A clear vendor lifecycle.

    Five stages take a vendor from start to finish: Intake / Qualification, Internal Review, Approved, Active, and Onboarding. Missing data or documents? The vendor waits where it is. When the business calls for it, a step can be skipped or revisited.

  2. 02

    Dynamic Forms in place of PDFs.

    Vendors share their company profile and partner details through structured forms. There's a questionnaire on channel goals and partner maturity, too. W-9s, ACH forms, and marketing collateral get uploaded through those same forms.

  3. 03

    Agreements and renewals in one place.

    MNDAs and distribution agreements go out for signature through Adobe Acrobat Sign. Once signed, each copy lands on the vendor record with an audit timestamp. Salesforce watches contract dates and renewal windows, and sends reminders before they come up.

  4. 04

    Approvals first, then tasks.

    Review checkpoints sit before activation. Once a vendor goes active, Salesforce creates a standard set of go-to-market tasks from an agreed template, with owners and basic sequencing.

  5. 05

    Partner programs and MDP tracking.

    Each Marketing Development Plan records committed budgets and expense allocations, so teams see spent vs. remaining funds at a glance.

  6. 06

    A read-only vendor portal.

    Vendors can see their status, signed agreements, approved MDPs, and fund usage. Filling in an assigned form or uploading a file is allowed. Contract terms, budgets, and approvals stay locked.

  7. 07

    Dashboards for the team.

    Two business dashboards built on standard reports cover vendor approvals, onboarding progress, MDP progress, and orders.

Before vs. After

AreaBeforeAfter
Vendor onboardingSplit across NetSuite, documents, and informal workflowsOne five-stage lifecycle in Salesforce with clear owners
Vendor dataStatic, ad hoc PDFsStructured Dynamic Forms with required fields
AgreementsStored in different placesSigned via Adobe Acrobat Sign and saved on the vendor record with timestamps
RenewalsEasy to missStart, end, and renewal dates tracked, with reminders
MDP / MDFTracked by handCommitments and spend vs. remaining in one view
Vendor updatesBack-and-forth emailRead-only portal with status, documents, and fund usage
FinanceNetSuiteStill NetSuite, with no overlap in Salesforce

Tech Stack

  • Salesforce CRM
  • Partner Ecosystem Management
  • Dynamic Forms
  • Flows and approval processes
  • Lightning record pages
  • Standard reports and dashboards
  • Adobe Acrobat Sign
  • NetSuite (still the financial system; no integration in Phase I)

FAQs

Salesforce Partner Ecosystem Management (PEM) extends partner relationship management with tools to onboard, enable, and manage partners. At 3Eye Technologies, Stack used it to bring vendor intake, approvals, onboarding, and Marketing Development Plans together inside Salesforce CRM.

No. Salesforce now runs the day-to-day vendor and partner program work. Billing, invoicing, and vendor payments still happen in NetSuite, the financial system of record. A Salesforce–NetSuite integration was kept out of Phase I and can be scoped as a later phase.

Each vendor gets a read-only view of their own status, signed agreements and approved Marketing Development Plans, plus how much of their fund is spent and what's left. They can fill out assigned forms and upload documents. Contract terms, budgets, and approvals are locked.

Running Partner Programs Across Too Many Tools?

How do vendor onboarding and MDF tracking work on your end right now? We'll show you what a cleaner setup in Salesforce could look like.