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.
IT Distribution · Salesforce Partner Ecosystem Management
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.
from first intake to activation
cleaner vendor data from day one
for every Marketing Development Plan
status, documents, and fund usage in a read-only portal
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.
3Eye's partner ecosystem and marketing programs were growing quickly. The processes behind them hadn't kept up.
As partner volume kept rising, all of this put extra strain on 3Eye's internal teams.
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.
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.
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.
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.
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.
We stayed close after go-live. A shared issue log and regular check-ins kept small problems small.
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.
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.
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.
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.
Each Marketing Development Plan records committed budgets and expense allocations, so teams see spent vs. remaining funds at a glance.
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.
Two business dashboards built on standard reports cover vendor approvals, onboarding progress, MDP progress, and orders.
| Area | Before | After |
|---|---|---|
| Vendor onboarding | Split across NetSuite, documents, and informal workflows | One five-stage lifecycle in Salesforce with clear owners |
| Vendor data | Static, ad hoc PDFs | Structured Dynamic Forms with required fields |
| Agreements | Stored in different places | Signed via Adobe Acrobat Sign and saved on the vendor record with timestamps |
| Renewals | Easy to miss | Start, end, and renewal dates tracked, with reminders |
| MDP / MDF | Tracked by hand | Commitments and spend vs. remaining in one view |
| Vendor updates | Back-and-forth email | Read-only portal with status, documents, and fund usage |
| Finance | NetSuite | Still NetSuite, with no overlap in Salesforce |
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.
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.