What it takes, and how long it takes.
The requirements, the five stages, and what each side is committing to. Roughly six to eight weeks from first conversation to your first certified programme — most of which is your team learning the platform properly rather than paperwork.
Five stages·6–8 weeks typical·Requirements published
Before you apply.
We would rather you read this and decide not to than spend six weeks discovering it. Requirements differ by type; these apply to all of them.
The five stages.
Each one has an output. If a stage produces nothing you can hold, it did not happen.
- 01
Conversation
Which of the four types, which market, and whether there is a genuine fit. Forty-five minutes, and it can end here without anybody having wasted a week.
- 02
Technical fit
Your engineers and ours, on the platform. For technology partners this is where the connector is scoped. Output: a written note on what you would build.
- 03
Agreement
The partner agreement for your type, with margins, deal registration terms, and the support path in it. Output: a signed agreement and a named contact each side.
- 04
Certification
Your consultants through the practical track, ending in a build against real data. Two to four weeks depending on how many people. Output: named certified consultants.
- 05
First programme
Your first customer, with our engineer available and not in charge. Output: a live deployment with your name on the delivery.
What each side commits to.
Written as two columns because the failure mode of partner programmes is one side doing all the committing.
What VEYQON commits to
- Certification and enablement
- Delivered at no cost, including the sandbox tenants and seeded demo data per vertical.
- Deal registration honoured
- For a fixed period, visible to you, and not quietly overridden by our own team.
- Engineering access
- A named contact, a shared channel, and escalation into the same rota our direct customers reach.
- Published commercials
- Margin and fees per type, in the agreement, reviewed annually rather than renegotiated per deal.
What the partner commits to
- Certified staffing
- At least one certified consultant on every active programme, named on the project.
- The published plan
- Programmes run in waves with an early first go-live and rollback points at each one.
- Honest scoping
- Boundaries stated to the customer before the sale, in the way our own pages state them.
- Same-day incident reporting
- Anything touching data or agent scope, in your environment or ours.
The questions we get asked before signing.
Answered here rather than on the third call.
- Will you compete with us on our own deals?
- Registered opportunities are yours for the registration period and our team can see the registration. That mechanism is the answer; a non-compete clause without it is decoration.
- Who owns the customer relationship?
- For implementation and OEM partners, you do — including the contract, in most cases. We will not approach your customer directly about licensing without you in the room.
- What does certification cost?
- Nothing, other than your people's time. We would rather have well-trained partners than a training revenue line.
- Can we build on top and keep the IP?
- Yes. Extensions you build on the platform are yours. We ask only that anything you contribute to the open core is contributed under its licence.
- What happens if it does not work out?
- The agreement has an exit with a wind-down period so live customers are not stranded mid-programme. Their exit rights are unaffected either way.
The rest of the company, in the same words.
Next step
Tell us which type, and which market.
partners@veyqon.com. Two paragraphs is enough to know whether the first conversation is worth booking.