Case study
What it actually takes to launch a net-new ISV on the Salesforce AppExchange
A revenue operations software company in Toronto had a working product and no presence in the Salesforce ecosystem: no AppExchange listing, no AE relationships, no partner agreements. NVG8 embedded as their fractional ecosystem lead and built the go-to-market from the ground up, across two and a half years. This is what that process actually looked like.
Josh Weckesser · June 2026 · 10 min read
Why this is hard
The Salesforce AppExchange has over 7,000 listings. The ones that generate meaningful partner-sourced revenue are not the ones with the best technology. They are the ones where an AE has seen the product close a deal, told three colleagues, and now has a reason to bring it up in customer conversations unprompted. Getting from a new listing to that state is not a marketing problem. It is a relationship and trust problem, solved over quarters, not weeks.
Most ISVs underinvest in the ecosystem motion because they cannot see the ROI until it starts compounding, which takes longer than a single quarter. The result is a graveyard of AppExchange listings that never generated a single co-sold deal.
The client in this case study avoided that outcome. Here is how.
The build, phase by phase
Describing this as a linear sequence is a simplification (several workstreams ran in parallel) but the sequencing of what depended on what is real and matters if you are trying to replicate it.
Phase 01
Months 1–3
AppExchange fundamentals before anything else
The AppExchange partner program has real prerequisites: security review, Trailhead certifications, ISVforce compliance, a functioning demo org. Most founders underestimate this phase because it looks administrative. It is actually your proof of fitness. Salesforce AEs will not introduce a product to a customer that has not passed security review. We worked through the Trailhead modules (AppExchange App Selling, ISVforce Guide, Channel Order App, Partner Intelligence) not as busywork but because understanding how Salesforce measures partner performance changed how we built every report and conversation that followed.
Phase 02
Months 2–5
Mapping the field before engaging it
The Salesforce Revenue Cloud field is large and not uniform. Different RVPs have different receptivity to ISV partners. PAMs vary by how actively they support their ISV roster. The first job is not to email everyone. It is to find the five people whose number one goal for the quarter creates a natural opening for your product. We built a structured tracker: named contacts, roles, meeting status, account counts, relationship notes. For a product in the revenue operations space, the target cluster was the Revenue Cloud GM, VP of Commercial Sales, Senior Director of Product Marketing, and regional PAMs. We got on calendar with all of them within the first four months. The process was not magic. It was methodical outreach with a prepared point of view on how the product complemented what they were already selling.
Phase 03
Months 4–8
First revenue from field-sourced pipeline
The first Salesforce-co-sold deals closed in the first two quarters. They were not large. They mattered because they created case studies we could use in every future AE conversation. The pattern that worked: a Salesforce AE introduced us to an existing Revenue Cloud customer who had a gap our product filled. Short demo, fast close. We documented each win as a two-paragraph story and put them in the Salesforce Partner Community, in the joint Slack channel we ran with the Revenue Cloud team, and in the first call deck. Social proof in the Salesforce ecosystem compounds: one AE who has seen it work will tell three others.
Phase 04
Month 9
The strategic ISV reseller partnership
The highest-leverage move of the engagement was not with Salesforce. It was a reseller agreement with a major Salesforce incentive compensation ISV. Our product was complementary: their product handled the compensation calculation, we handled the revenue operations visibility layer. Their installed base was a warm market for us. Building the partnership took four months of negotiation across a dozen workstreams: revenue share, reseller and mCSA agreements, co-selling, enablement, customer success SLAs, co-marketing, and a migration path for existing partner customers. The reseller project plan had over fifty named tasks across commercials, product, support, marketing, and customer success. Each workstream had a ZINKT lead, a partner lead, a status, and a due date. Partnerships of this kind do not close on goodwill. They close on specificity.
Phase 05
Months 10–18
SI partner program from scratch
A Salesforce ISV needs System Integrators. SIs bring implementation capacity, customer relationships, and co-selling reach that no ISV can replicate with a direct sales team. We identified SI targets with active Revenue Cloud practices, built the ZINKT Certified Practice framework, wrote the training and certification materials, created the scoping guide for SI AEs (how to qualify a good fit, how to scope the implementation), and ran the first enablement sessions. The Trailhead certification badge took time to build correctly: it had to meet Salesforce's partner program requirements and actually test meaningful product knowledge, not just be a completion checkbox.
Phase 06
Year 2
FY24 GTM: building the demand engine
By year two the foundation was in place. The FY24 plan targeted $500K net new ARR and $1M ARR total. The strategy shifted from relationship-building to demand generation: AppExchange marketing promotions, a content marketing foundation (educational thought leadership, customer spotlights, monthly email cadences), a customer advisory board, and a BDR program launch. The Revenue Cloud collection placement on the AppExchange was upgraded. Four customer case studies (with named customers and documented outcomes) were distributed to the Salesforce field. The reseller partnership moved from signed to active co-selling, with joint pipeline reviews and declared revenue flowing in both directions.
What made it work
A structured engagement cadence, not ad hoc outreach
Every named Salesforce contact had a meeting status, a relationship note, and a next action in our tracker. Weekly syncs with the Revenue Cloud team covered joint pipeline, product feedback, and upcoming events. This sounds obvious. Most ISVs do not do it because it requires someone to own the maintenance of the relationship, not just the initial meeting.
Social proof before scale
We did not try to activate the entire Salesforce field at once. We found the five AEs most likely to co-sell, got them one win each, documented it, and let word of mouth do the rest. Four published customer case studies (with named customers) were the most effective field activation tool we had. An AE forwarding a case study to a prospect is more credible than any one-pager we could have written.
The reseller partnership was built on specificity, not goodwill
A signed reseller agreement requires fifty-plus documented tasks across commercials, product, support, marketing, and customer success, all with named owners and due dates. The partnership moved when we treated it like a project plan, not a relationship-building exercise. Both sides had a shared document with status columns. Stalled tasks got a direct question, not a follow-up email.
SI partners need a reason to learn something new
System Integrators have full pipelines. Adding a new product to their practice is a cost for them before it is a revenue opportunity. The certification badge, the scoping guide, and the AE enablement deck existed to reduce that cost. The question we answered for every SI conversation was: what does your team need to know to scope and sell this in under thirty minutes?
What we would do differently
Start the SI program earlier
SI partners take six to twelve months to generate their first referral after being activated. We started the SI program in month ten. If we had started it in month three, in parallel with the Salesforce field work, the pipeline contribution from SIs would have arrived earlier and at higher volume by year two.
Case studies are a leading indicator, not a lagging one
We treated case study production as something that happened after enough customers had been won. The better approach is to instrument the first customer win for documentation from day one (a brief call, a few quotes, a two-paragraph outcome) so the case study is ready the week the deal closes, not months later. The Salesforce field has a short memory. Stories need to be current.
Reseller economics need modeling before the term sheet
The revenue share negotiation would have moved faster if we had arrived at the first meeting with a modeled deal calculator, showing what a typical customer looked like, what the reseller’s share would be, what NPS and retention looked like for co-sold customers. We built this eventually. Building it first would have shortened the commercial negotiation by a month.
The takeaway
An AppExchange listing is not a go-to-market. A go-to-market in the Salesforce ecosystem is a set of active relationships, proven co-sell motions, and live commercial agreements, each of which requires sustained operational attention to build and maintain.
The companies that generate meaningful partner-sourced revenue from the AppExchange treat the ecosystem as a sales channel that requires the same investment as a direct sales team. That means dedicated headcount (or a fractional operator who owns it), consistent measurement, and a clear answer to the question every Salesforce AE is implicitly asking: why should I spend fifteen minutes of a customer call on your product instead of the twelve other things I could talk about?
If you are building a Salesforce ISV go-to-market, or trying to get more out of one that is not producing, the Partnerships & Ecosystem workflows we have productized at NVG8 came directly from engagements like this one. The Workflow Design Hour is the fastest way to pressure-test whether one of them fits your situation.