Co-selling and referrals: honest strategies while programs mature

The awkward middle

Most partner advice assumes a program already exists. It tells you how to hit tier thresholds, how to register a deal, how to claim co-marketing funds. That advice is useless during the period most partnerships actually start in — the stretch where the vendor has real product, real customers, and no published terms.

FastYoke is in that stretch right now, and we'd rather say so than imply otherwise. Our Channel Partners page says "Coming soon" in as many words, and the note at the bottom is blunt: it's a placeholder while we shape the program, and specific terms, pricing, and signup mechanics will land there when the early-access window opens. A partner-management dashboard, branded tenant onboarding, and a multi-tenant operator console are described there as preview access for early partners — not things you can go click today.

That is genuinely awkward, and it is also the normal condition of an early partnership. Two firms are already working with us inside it — Pay n Go Systems in retail, point-of-sale, and food service, and iNetko on frontline support, sales engineering, implementation, and consulting. Neither of them waited for a terms sheet, and neither of them bet the business on one.

So: what can you actually do in the middle period, and how do you keep yourself safe while doing it?

Referral, co-sell, resell — pick one on purpose

These three get used interchangeably in conversation, and they are completely different economic and risk positions. A lot of partner relationships go badly because nobody named which one they were in.

Referral. You make an introduction. The vendor runs the cycle, signs the customer, and owns delivery. You take a fee and carry essentially no delivery risk. This is the lowest-effort position and the lowest-margin one, and it's the right starting point when you don't yet know how the product behaves in production.

Co-sell. You're in the room. You bring the domain credibility and the customer trust; the vendor brings product depth. You split the work, and — this is the part people underestimate — you split the credibility. If the deployment disappoints, that disappointment lands on both of you, because you were the one who said it would work. Co-selling is where most agencies and systems integrators should live, because it's the position where your own expertise is the differentiator.

Resell. You own the paper. You bill the customer, you hold the margin, and you absorb the support burden and the renewal risk. That's a real business, but it's a different business from the one most services firms are running, and it demands terms you can model out years.

The failure mode is drifting into resell by accident. It starts as a referral, then you're helping with the implementation, then you're the first call when something breaks — and now you're effectively providing support with none of the margin or contractual standing of a reseller. Decide which position you're in, say it out loud to both the vendor and the customer, and change it deliberately rather than by drift. If you do eventually want the reseller seat, that is a separate decision to make with open eyes — and a heavier one than it looks.

What to do before a program exists

Write the arrangement down anyway. Informal is fine; undocumented is not. Even a one-page email both sides acknowledge should cover: who owns the account relationship, how an introduction is attributed and for how long, what happens on renewal, and what happens if the customer churns. Deal registration as a practice is worth asking any vendor for — but be clear-eyed that with a maturing program you're agreeing to it in writing between two companies, not clicking a button in a portal that exists.

Start with one joint win, not a framework. A signed framework with no reference customer behind it is a document. One deployment both sides can point to is leverage — in the next customer conversation, and in whatever terms negotiation eventually happens. Sequence it that way.

Sell your own differentiated work. The durable revenue in an early partnership is implementation, domain expertise, data migration, training, and ongoing operations — the things you do that nobody else can reprice. Margin you're reselling on someone else's product can be compressed by a future program. Margin on your own work cannot. That's the case for building a services practice around a platform rather than a resale margin on top of one, and it applies double before terms are published.

It helps that the platform economics are already public and don't depend on a partner agreement. The apps install at $0 — the Logistics core, CRM Suite, Inventory, Accounting, Project Tracker, Field Service, and Forms, with Warehouse Management in early access — and platform usage is metered above a free tier. You can scope a customer engagement against published pricing today without knowing what your eventual partner economics look like. The technical claims are equally checkable: each customer gets their own database file rather than a shared table, every state change lands in an append-only audit log, and the workflow engine is an explicit state machine. Those you can demonstrate in a room without citing a roadmap.

Attribution is what actually goes wrong

If you take one operational habit from this post, take this one.

Verbal attribution decays. The person who agreed the introduction was yours changes roles. The customer signs eleven months later through a different channel and nobody connects the two conversations. Renewal comes around and the original thread is nowhere in either CRM.

So write it down at the moment it happens: who introduced whom, on what date, to which named contact, and what both parties understand the attribution window to be. Send it as an email so there's a timestamp on each side. Ask explicitly what happens at renewal — a fee that evaporates at month twelve is a very different arrangement from one that persists, and the difference is invisible until it isn't.

Five minutes per introduction. It's the highest-return habit in early partnering.

What to watch for

Don't build a business whose margin depends on unpublished terms. Early-access programs change. The terms a first cohort gets may end up better than what follows, or worse. Either way, a P&L that only works at a discount nobody has committed to in writing isn't a plan.

Keep the customer relationship yours. It's the one asset no program revision can take away — the relationship is the moat. If the vendor's terms shift, a partner who owns the trust has options. A partner who was only a routing layer does not.

Be honest with the customer about what's mature. If you tell a client a preview capability is production-ready and it isn't, you burn your own credibility first — not the vendor's. You were the one they trusted. Say which parts are shipped and proven, say which parts are early, and let them decide. Customers reward that far more reliably than they punish it.

Be equally honest with yourself about what you're getting. Architecture access, early feature preview, and joint case-study coverage are real value. They are not revenue share. Don't quietly book them as such.

The takeaway

If you're an agency, ISV, or systems integrator sizing up a partnership before the program is finished: pick your position deliberately, write down the arrangement and the attribution even when it's informal, sell the work only you can do, and land one reference-able joint win before you chase a framework.

If the early-access track fits your shape, the concrete next step is to get on the first-cohort list — mail partners@fastyoke.io, the same address on the Channel Partners page. Then, while the terms take shape, go find the joint win. The partner who is genuinely useful to the customer independent of the program is the one holding the strongest hand when the program finally arrives.