Four ways to build on VEYQON.
An open core and a documented schema mean a partner can build things we have not built and sell into markets we do not cover. What follows is what each kind of partner gets, what each is expected to hold up, and where we stop competing with you.
Four partner types·Published margins·No channel conflict clause
The four types.
Pick the one that matches how you make money. A partner can hold more than one, but the agreement is written per type rather than as a single tier.
What a partner actually gets.
Enablement that is real rather than a portal login and a PDF of the deck.
What we expect back.
Short list, held firmly. A partner who cannot hold these makes us slower rather than faster.
- Certified people on delivery
- At least one certified consultant per active programme, named in the project. Not a certificate held by somebody who left.
- The published wave plan
- If you sell a VEYQON programme, it runs in waves with a first go-live early and rollback points. That commitment is ours as well as yours.
- Honest scoping
- Tell the customer what the platform does not do. We publish boundaries on our own pages and we will not put a partner in front of a customer who does the opposite.
- Incidents reported
- Anything touching data or agent scope reaches our security rota the same day, regardless of whose environment it happened in.
The directory.
Certified partners, listed by region and vertical, with the consultants each has certified. The listing goes live with the first cohort — an empty directory is more useful than a padded one, because the first person who calls a name on it and finds nobody there will not call the second.
The first cohort is in certification.
Listings go up as consultants complete the practical track, with the region and vertical each partner covers and the named people who hold the certification.
The rest of the company, in the same words.
Next step
Start with a conversation, not a form.
Tell us which of the four types you are and what market you already serve.