An ISV sells through system integrators by choosing a handful of SIs whose customers and practices match its product, agreeing a commercial model (resale, referral, co-sell or white-label), handing them a complete enablement kit, and running joint pipeline plays on the SI's install base. Recruit in 90 days, then manage partners with a scorecard, not goodwill.
This is the playbook we use with ISV clients: how to score SIs, how to compare commercial models without guessing at market rates, what goes in the kit, and what to send in the first outreach.
Why ISVs sell through SIs
- SIs own the implementation relationship. On many enterprise platform projects, the SI shapes the architecture and recommends the add-ons.
- They bring an install base. A partner with live customers on your platform already has the trust and access you would spend years building.
- They absorb services work. Integration, change management and first-line support stay with the SI, so a small ISV can serve large accounts.
- Platform vendors fund the ecosystem. ServiceNow, for example, announced in January 2026 that its Market Development Fund offers new funding opportunities and 100% reimbursement for select activities, in an ecosystem of more than 2,700 partners.
Platforms are leaning on partners harder. Crossbeam's ELG Insider reported that at Workday, partners now drive more than 20% of net-new ACV, up from less than 3% two years earlier.
The model is not only for large ISVs. Quills AI, a bootstrapped company associated with Antler, sells through SIs that resell it per instance. The math is easy to follow: five SIs each bringing three clients equals 15 instances. Phantom Tech built an SI channel alongside the CEO's LinkedIn and event presence, and 4Ce CloudLabs works with an SI partner network alongside its Salesforce partner ABM.
Choosing SI partners: a fit scoring table
More partners is not better. Three active SIs are worth more than thirty inactive logos on a partner page. Score every candidate before you pitch any of them.
| Criterion | Illustrative weight | Score 5 looks like | Score 1 looks like | Evidence to check |
|---|---|---|---|---|
| Platform alignment | 20% | Certified practice on the platform your product extends | No practice on your platform | Vendor partner directory, certifications |
| Install base overlap | 20% | Many live customers in your ICP industries and company sizes | Few or no relevant customers | Case studies, account mapping |
| Practice lead sponsorship | 15% | A named practice lead wants a differentiated offer | Only a generic partnerships inbox | First call with the practice lead |
| Services gap you fill | 15% | Your product removes custom work they struggle to deliver | Competes with their own IP | Discovery on current projects |
| Sales motion fit | 10% | Sells advisory and implementation to your buyer persona | Staff augmentation only | Proposals, job postings, LinkedIn |
| Geography and vertical | 10% | Same regions and industries you can support | Regions you cannot support | Office locations, customer list |
| Competing products | 10% | No partnership with a direct competitor | Active reseller of a direct competitor | Partner pages, press releases |
Worked scoring example
Illustrative example: an ISV that extends a CRM platform scores three SIs using the weights above.
- SI A (regional, strong vertical base, keen practice lead): 5, 4, 5, 4, 4, 4, 5. Weighted score 4.45.
- SI B (global, huge base, no sponsor, resells a competitor): 5, 5, 1, 2, 3, 3, 1. Weighted score 3.15.
- SI C (boutique, smaller base, deep industry focus): 4, 3, 4, 5, 4, 3, 5. Weighted score 3.95.
Recruit A and C first. Revisit B once you have referenceable deals and B's competing partnership changes. To size install base overlap before the first call, start from partner account lists for your platform.
Commercial models compared
Pick the model that matches how much of the sale the SI controls. We do not quote market rates here because they vary by category, deal size and platform. Model your own margins before you offer anything.
| Model | How money flows | Who holds the customer contract | SI effort | Best when | Watch-outs |
|---|---|---|---|---|---|
| Resale per instance | SI buys from you and resells, often bundled with services; you bill the SI per deployed instance | SI | High: sells, implements, often supports first line | The SI has strong accounts and wants software margin | Price visibility, support boundaries, SI credit risk |
| Referral fee | You contract directly and pay the SI an agreed fee on registered, closed deals | ISV | Low to medium: introduces, may join calls | The SI influences but does not want to hold the contract | Weak commitment; define exactly what counts as a referral |
| Co-sell | You sell software directly; the SI sells implementation services on the same account | ISV for software, SI for services | Medium to high: joint account plans and calls | Enterprise deals that need product and implementation | Account ownership disputes; requires deal registration |
| White-label | The SI sells your product under its own brand | SI | High: brands, sells and supports | The SI wants proprietary IP and you want volume | Your brand is invisible; dependency on one partner |
Quills AI's per-instance resale is the first row in practice. Each SI deployment is a countable unit, which makes partner forecasting and scorecards straightforward.
The partner enablement kit
SIs do not sell what they cannot explain, demo and price in one meeting. Ship this kit before the first joint customer call.
1. Partner pitch deck (10 slides)
- The customer problem, in the SI's buyers' language
- Why current approaches, such as custom builds or the incumbent tool, fall short
- What your product does, in one diagram
- Where it sits in the platform architecture
- Three use cases by industry
- Proof: customer results you are allowed to publish
- Implementation path and the services the SI delivers
- What the SI earns: software margin or fee, plus services
- Deal registration and support process
- Next steps and named contacts
2. Demo environment
- A sandbox per SI with realistic sample data for two or three industries.
- A scripted 15-minute demo and a 45-minute technical deep dive.
- A reset script so the environment is clean before every customer demo.
- Named logins per SI user, removed when people leave the practice.
3. Pricing sheet
- List price, partner price or fee, and what is included per instance or tier.
- The services the SI is expected to deliver, with scope guidance they can quote from.
- Discount rules and who approves exceptions.
4. Deal registration
DEAL REGISTRATION FORM
Partner company: [SI name]
Partner rep: [name, email]
End customer: [legal name, domain, HQ country]
Opportunity: [use case, platform, modules]
Estimated value: [software] / [services]
Stage: [discovery / solution design / proposal / negotiation]
Expected close date: [date]
Competing vendors: [names or unknown]
Customer contacts engaged: [names, titles]
Help requested: [demo / technical validation / pricing / executive sponsor]
RULES (publish before the first deal)
- First valid registration wins; protection lasts [X] days, extendable with activity.
- ISV approves or rejects within [X] business days, with a written reason.
- Conflicts go to [partner manager] and are resolved within [X] business days.5. Battlecards
- Versus the leading competitor: where you win, where you lose, questions to ask.
- Versus custom build: build effort, maintenance load, upgrade risk.
- Versus doing nothing: the cost of the status quo in the buyer's terms.
- Objection handling: security review, data residency, pricing, vendor size.
Joint pipeline plays
Enablement makes a partner able to sell. Joint plays make them actually sell. Run at least one per quarter with every active SI.
Co-hosted webinars
- Pick a problem the SI's customers raise during projects, not your product category.
- The SI practice lead presents the approach, you demo the part your product handles, and a customer joins if possible.
- The SI invites its customers and you invite your prospects, under an agreed policy for sharing registrant data.
- Follow up within 48 hours with a joint assessment offer.
4Ce CloudLabs ran Salesforce partner ABM with migration campaigns such as Veeva to Life Sciences Cloud and CPQ to Revenue Cloud, supported by webinars. Migration themes like these suit joint plays because they target customers who already run a system that needs to move.
Joint ABM on the SI's install base
- Run account mapping with the SI in a neutral tool such as Crossbeam or Reveal, or a spreadsheet exchange under NDA.
- Segment the overlap: SI customers who are not yours, sorted by fit and trigger such as an upgrade, migration, renewal or new module.
- Build 20 to 30 account briefs together.
- The SI account manager makes the introduction; you supply content and a specialist.
- Check whether the platform vendor's MDF can fund the campaign. Our partner MDF guide and ServiceNow MDF guide cover eligibility and claims.
Our account-based marketing service runs these joint waves, from mapping through meetings.
The partner scorecard
| Metric | Definition | Review cadence |
|---|---|---|
| Trained reps | SI sellers and consultants who completed your enablement | Monthly |
| Deals registered | New registrations, by count and value | Monthly |
| Sourced pipeline | Registered opportunities the SI originated | Monthly |
| Influenced pipeline | Your direct opportunities where the SI took part | Quarterly |
| Win rate on registered deals | Closed-won divided by all closed registered deals | Quarterly |
| Instances or customers live | Deployed instances, for resale models | Quarterly |
| Time to first deal | Days from signed agreement to first registered deal | Per new partner |
| Joint activities completed | Webinars, ABM waves and events run together | Quarterly |
| Customer health | Adoption and renewal signals on partner-led accounts | Quarterly |
Review the scorecard with each practice lead every quarter. A partner with no registered deals after two quarters moves to a lighter tier, and your team's time goes to partners who are producing.
The 90-day SI recruitment plan
| Weeks | Focus | Actions | Illustrative exit criteria |
|---|---|---|---|
| 1-2 | Define | Write the partner ICP, choose the commercial model, draft program terms, build the scoring sheet | Terms and scoring approved internally |
| 3-4 | Shortlist | Pull 30 to 50 SIs from platform partner directories and LinkedIn; score them; pick the top 10 | Ranked list with named practice leads |
| 5-6 | Outreach | Send the outreach template; executive-to-executive notes; ask customers which SIs they use | First calls booked with most of the top 10 |
| 7-8 | Qualify | Discovery calls, account mapping, two joint target accounts identified per SI | Three or four SIs agree to a pilot |
| 9-10 | Enable | Kit delivered, sandboxes live, training sessions run, deal registration open | Reps trained at every pilot SI |
| 11-12 | Launch | First joint play, first registrations, scorecard baseline | At least one registered deal per pilot SI |
Partner outreach template
EMAIL TO SI PRACTICE LEAD
Subject: [Platform] customers asking for [capability]
Hi [first name],
Your team's work on [specific project, case study or certification] caught
our attention. We build [product], which [does one specific thing] for
[platform] customers in [industry].
Where it helps SIs: [removes custom build for X / shortens phase Y /
adds a recurring software line to services projects].
How partners work with us: [resale per instance / referral / co-sell],
with a partner sandbox, pricing sheet and deal registration from day one.
Would 30 minutes make sense to compare notes on [two or three account
types or a named migration theme]? If we see overlap, we can map accounts
under NDA and pick two to work on together.
[Name], [title], [company]
LINKEDIN NOTE
Hi [first name], saw [their post, talk or case study]. We build [product]
for [platform] customers and work through SIs. Open to connecting?
FOLLOW-UP (5 business days later)
Hi [first name], one concrete idea: [customer type] on [platform] often
struggle with [problem]. We have a joint assessment offer SIs can run in
[scope]. Worth 20 minutes?
FIRST CALL AGENDA (30 minutes)
1. Their practice: platforms, industries, typical project (10 min)
2. Our product and where it fits in their projects (8 min)
3. Commercial model options (5 min)
4. Account overlap: two or three example accounts (5 min)
5. Next step: account mapping or pilot (2 min)Common mistakes
- Signing many partners and enabling none of them.
- Recruiting through partner managers only, instead of the practice leads who staff and sell projects.
- Positioning the product against the SI's own IP or services.
- No deal registration, so the first channel conflict ends the relationship.
- Expecting SIs to create demand on their own without joint plays.
- Choosing a commercial model before learning who holds the customer contract today.
Where Lemniscate fits
We build partner-led pipeline for ISVs and SIs, from account mapping to joint ABM and events. See our system integrators practice, including programs for Salesforce partners. Make sure buyers and AI assistants can find your partnerships with AEO for system integrators and our guide to partner ecosystem AI visibility.
