Use case 04

Certified, listed, badged. And the referrals still are not coming.

You passed the exams, you are on the marketplace, you have the logo in your footer. The ecosystem was supposed to send deals. Instead you are one of several hundred partners in the same tier, invisible to the vendor's own sellers, waiting for a referral that has no reason to arrive.

The short answerPartner ecosystems produce pipeline for the partners who bring their own demand, not for the ones waiting to be allocated it. The fix is to stop selling your certification and start owning a wedge: one platform, one migration or practice area, one named account list where you can prove results. Then you give the vendor's sellers a reason to co-sell, build the proof the end customer needs, and claim the market development funds the vendor already offers for exactly this work.

The situation

How it gets described on the first call.

We are a premier partner. We have never had a referral from the vendor.

Managing Partner, consulting firm

The account executives at the vendor do not know we exist.

Head of Alliances, system integrator

Our marketplace listing gets views and nothing else.

CEO, implementation partner

We have funds we have never used because nobody has time to apply.

Partner marketing lead

Why the ecosystem is quiet and why that is predictable.

A vendor's partner program exists to extend the vendor's capacity, not to distribute leads fairly. The vendor's sellers co-sell with partners who make their quarter easier: partners with a named account already in motion, a credible point of view on a specific migration, and proof that the implementation will not blow up. Being certified says you are competent, which every partner in your tier also claims. It gives a vendor seller no reason to pick you on a Tuesday afternoon.

The second problem is positioning. Most partner firms describe themselves by the platform they implement, which is the one thing they share with everyone they compete against. An end customer searching for help does not search for a partner, they search for the problem: a specific migration, a compliance deadline, a practice area, an industry outcome. If your site says what the vendor's site says, a buyer has no way to choose and a model composing an answer has nothing to distinguish you by.

Third, the funds go unclaimed. Most large vendors operate market development funds or co-investment for exactly the work that would generate pipeline: campaigns, events, content and demand generation around their platform. Terms and eligibility differ by vendor and change often, so confirm current terms in your own partner portal. We keep a guide to how partner funds work by vendor, and the pattern we see is not that firms are refused, it is that nobody owns the proposal, so the money sits there for another year.

Why the usual fix fails

What gets tried first. And why it does not hold.

These are the four moves we see before we are called, and each one treats the ecosystem as a channel to be joined rather than a market to be earned.

More certifications and a higher tier

The team invests in exams and the tier badge upgrades. Nothing changes in the pipeline, because the constraint was never capability. There are hundreds of other firms at the same tier making the same claim.

Relationship building with the vendor's field team

Coffees, dinners and a quarterly check-in with the alliance manager. Useful, and completely dependent on individuals who get reassigned. Without a repeatable reason to co-sell, the relationship resets every time the territory does.

A marketplace listing and a partner directory page

Both are necessary hygiene and neither creates demand. They are places a buyer who already decided to find you can verify you exist. They do not reach a buyer who has not started looking.

Generic services marketing

A website that lists the platforms, the capabilities and the regions, written the way every competitor writes it. It cannot be chosen between, it cannot be cited in an AI answer, and it gives the vendor's seller nothing to forward.

The 80:20 cut here

The fifth of the work that moves this number. One wedge, one list, one proof story.

Partner firms want to be visible for everything they can do. The fifth that works is the opposite: get famous in a narrow slice where you can prove results, then widen.

The cut for this situation

The fifth of the work that moves the pipeline number, and the four fifths that can wait the vital fifthDoes the pipeline number move?One wedge: a named migration, practice area orindustry outcomeA named account list built on real buyingsignalsOne reference story the vendor's sellers willforwardA funded program, with the proposal actuallysubmittedthe trailing four fifthsNobody can say what it changedMarketing every platform you are certified onMore certifications and tier upgradesBrand campaigns about your consultingphilosophyWaiting on referral allocation from the vendorFor every piece of work, ask whether a vendor account executive could forward it to a customer tomake their own quarter easier. If not, it is not the fifth we run first.
What the first quarter buys: a wedge the vendor's sellers can use, a list to run it against, and the funds to pay for part of it.
Vital fifth

One wedge: a named migration, practice area or industry outcome

Specific enough that an end customer searching for the problem finds you, and that a vendor seller can describe you in one sentence. A platform name is not a wedge. A named migration with a deadline, a regulated industry workload or a practice area with a hiring signal is.

Vital fifth

A named account list built on real buying signals

Accounts with live job postings for the platform, announced migrations, or a compliance deadline. Signal beats firmographics here, because the platform purchase usually precedes the services purchase by a quarter or two. We publish sample partner account lists by ecosystem.

Vital fifth

One reference story the vendor's sellers will forward

The outcome, the systems, the timeline and the risk you removed, written for the end customer rather than for the vendor. This is the artifact that turns an alliance relationship into recurring co-sell, because it makes a vendor seller look good.

Vital fifth

A funded program, with the proposal actually submitted

Someone owns the fund proposal, the proof of execution and the reimbursement claim. The work is the same work you were going to do, with the vendor carrying part of the cost. Confirm current terms in your partner portal, since programs change.

What we park, and tell you we are parking

  • Marketing every platform you are certified on. One wedge until it produces deals, then the second
  • More certifications and tier upgrades. Capability was never the constraint
  • Brand campaigns about your consulting philosophy. Nobody buys a methodology from a page
  • Waiting on referral allocation from the vendor. Treat referrals as an outcome of your own demand, not a source

First ninety days

What we actually run. In the order it has to happen.

This runs alongside your delivery work, so the sequence assumes one owner internally and a few hours a week of practice-lead time, not a new department.

The first ninety days, in three blocks of work Days 1 to 30Choose the wedgeRead your own won deals bypractice and industryPick one migration orpractice area to ownBuild the signal-basedaccount listMap the vendor funds you areeligible forDays 31 to 60Build the wedge proofPublish the wedge page andthe comparison materialWrite one reference story avendor seller can forwardBrief the alliance and fieldteams with one sentenceSubmit the fund proposal forthe programDays 61 to 90Run it at the accountsOpen outreach into the signallistRun one closed-door sessionfor the wedgeCo-sell plays with namedvendor sellersReport meetings, sourced andco-sold separately
The first ninety days. Nothing in block three starts before block one is answered.

Days 1 to 30: Choose the wedge

We look at where you already win, not where you are certified. One wedge is chosen on evidence: margin, repeatability, and whether the demand signal is observable from outside. In parallel we map which vendor funds apply and who inside your firm will own the proposal.

Days 31 to 60: Build the wedge proof

The wedge becomes real: a page an end customer searching for the problem can find, a reference story written for that customer rather than for the vendor, and a single sentence the vendor's sellers can repeat. The fund proposal goes in during this block, because approval cycles are slow and the work is already scoped.

Days 61 to 90: Run it at the accounts

Now the list gets worked: outbound and LinkedIn into the accounts showing the signal, one closed-door roundtable or technical session for the wedge, and specific co-sell plays with the vendor sellers who cover those accounts. Reporting separates what you sourced from what the ecosystem brought, because those are different arguments to make internally.

Buying group

Who has to agree inside the end customer. The vendor relationship does not cover any of them.

Partner deals carry an extra complication: your champion is often the platform owner, who has to sell a services spend to people who do not care which partner you are.

Who a program usually reaches, who still has to agree, and what has to travel between them reached by youThe championOne person who takes the call, reads the page and wants this to work.reached only through the champion, or not at allPlatform ownerBusiness sponsorSecurity and ITProcurementFinanceThe delivery teamwhat has to survive being forwardedA reference story in their industry on the same platform, the implementation plan and risk register, theintegration and security answers, and a business case that survives a procurement review.
The platform owner is usually your champion, and the least able to approve the spend on their own.

What to measure

The numbers we report and the ones we refuse to lead with.

MetricWhy it is the right one hereWhen it should move
Meetings in wedge accountsThe wedge is either producing conversations with accounts showing the signal, or it is the wrong wedge.From week six
Co-sell plays active with named vendor sellersCounts relationships that have a deal attached, which is the only kind that survives a territory change.From the second month
Pipeline sourced by you versus sourced by the ecosystemKeeps the two honest. Partner-sourced pipeline usually grows as a consequence of your own, not instead of it.Monthly
Funds approved and claimedConverts marketing cost into vendor-funded cost. It is also the clearest internal proof the alliance is working.One to two quarters, depending on the vendor's cycle
Win rate when the vendor is in the dealTells you whether co-sell is adding anything or just adding a meeting.Reviewed quarterly

Reported, never led with: certifications held; tier level; marketplace listing views; alliance meetings attended.

Proof

Teams that arrived here. And what we built with them.

“What differentiated Lemniscate Growth is that they started with the buyer. On the inbound side, gated assets built for our category, a maturity assessment tool, and a search strategy that covers SEO alongside answer engine and generative engine visibility. On the outbound side, tiered account lists and multi-touch sequencing. We went from single digit qualified meetings in a month to tens of qualified meetings in a month. They operate like an extension of our own team.”
Sunil Masand
Sunil MasandHead of Product and Marketing, Aavenir

Why a wedge beats a capability list

Every partner firm's instinct is to show range, because range is what wins a competitive bid once you are in it. The problem is getting into it. A buyer with a specific problem, and a vendor seller with a specific account, both need to be able to say in one sentence why you rather than someone else. Range cannot be said in one sentence. A named migration, a regulated workload or an industry outcome can.

4CE CloudLabs is the clearest example in our portfolio. Rather than marketing Salesforce capability in general, the programs were built around specific migration paths, with account-based marketing and webinars aimed at the companies facing those exact moves, plus a network of larger integrators who needed that specialist capacity. The wedge made the firm legible to both the end customer and the ecosystem.

  • A wedge is something a vendor seller can repeat from memory
  • Pick it on evidence: margin, repeatability and an observable demand signal
  • Widen only after the first wedge is producing meetings

Reading the hiring signal

In partner ecosystems the most reliable buying signal is public: an account posting roles for the platform, or announcing a program that requires it. Hiring for a platform almost always precedes or accompanies a services purchase, because internal capacity is never sufficient at the start. That makes job postings a better targeting input than company size or industry alone.

The practical workflow is to monitor postings and announcements across your ecosystem, score accounts by how recent and how senior the signal is, then build the buying group for the top tier. This is the basis of the account lists we publish by ecosystem, and it is work any firm can do for itself with discipline.

Making the funds work without a dedicated team

The common reason funds go unclaimed is that nobody owns the paperwork, and the paperwork arrives in the middle of delivery crunch. The fix is unglamorous: one named owner, a calendar reminder tied to the vendor's cycle, a proposal template reused each time, and evidence of execution collected while the campaign runs rather than reconstructed afterwards.

Terms, splits and eligibility differ by vendor and change often, so we check your own partner portal rather than relying on anything published. Our partner funds guide sets out how the main programs work and what each one usually asks for, with the caveat that your portal is the only authority on your terms.

Questions buyers ask us. Answered plainly.

Still unsure? Ask us directly.

Why does the vendor not send us referrals?

Because referral flow follows the partners who make a vendor seller's quarter easier, not the partners who are most certified. A seller forwards an opportunity to the firm with a named account already in motion, a specific point of view on the problem, and a reference story that reduces the risk of a messy implementation. Build those three and referrals start arriving as a consequence of your own demand rather than as a substitute for it.

We implement four platforms. Do we really have to pick one?

For the first quarter of marketing, yes, and you keep selling all four the whole time. The choice is about where the demand work points, not what you deliver. Firms that market all four equally end up with messaging that matches the vendor's own site, which gives neither a buyer nor a vendor seller a reason to choose them. Pick the one with the best margin, repeatability and observable demand signal, then add the second once the first produces meetings.

Can partner funds really pay for this?

Often partly, and the rules are vendor-specific and change, so your partner portal is the only authority on your terms. The pattern worth knowing is that most programs fund exactly the activity that generates pipeline around the platform: campaigns, content, events and demand generation. The usual blocker is not eligibility, it is that no one owns the proposal and the evidence of execution. We assign that owner in the first thirty days.

Does this work for a small firm competing against the large integrators?

It works better for a small firm, because a wedge is a credible claim at your size and an implausible one at theirs. A hundred-person firm that is the obvious choice for one migration in one industry wins deals a global integrator never sees, and it does so without a bid team. SystemSoft, a firm of over a thousand people, still runs this way deliberately, building pipeline practice by practice rather than as one brand.

How do we stop depending on one alliance manager?

By making the co-sell reason structural rather than personal. A reference story, a named account list and a one-sentence description of your wedge survive a territory change, because any new seller can pick them up. We also deliberately spread relationships across several sellers in the territories that matter, rather than routing everything through the alliance contact, so one reassignment does not reset the pipeline.

Tell us where it is stuck. Twenty minutes is enough to find out.

Bring the revenue target, the account list if you have one, and last quarter’s pipeline. We will tell you which fifth of the work we would run first, and what we would stop.

  • 20 minutes with a senior operator, not an SDR
  • Bring your revenue target and markets; we bring the pipeline math
  • Slots across US, Canada, India, Singapore and GCC time zones

Prefer email? growth@lemniscategrowth.com

Pick a 20-minute slotStraight to a senior operator. No SDR screen.