The organisations we work with
No single company covers the whole of compliance work. We work with organisations that connect our products to their own, take on the legal side of compliance, or bring the products to their own customers.
For us a partnership is not a reseller list, it is a division of the work. The partner takes responsibility in its own field of expertise; we provide the product, the implementation and technical support. Who delivers what is written down from the start, so the customer is never caught between two suppliers.
Three kinds of partnership
Which one you enter determines what you deliver and the commercial model. A mixed model is also possible.
Technology partnership
Organisations that connect our products to their own systems, or provide the infrastructure we integrate with.
- Product and API integration
- Integration on identity, logging and infrastructure
- Joint solution design and technical validation
Consultancy and legal partnership
Consultancies and law firms that take on the legal and administrative side of compliance.
- KVKK consultancy and legal opinion
- Document set, VERBİS and audit readiness
- Independent review and risk assessment
Channel partnership
Organisations that bring our products to their own customer base and run the first contact.
- Sales and the first conversation
- The customer relationship after implementation
- Growth focused on a region or a sector
What comes out of the partnership
We keep the promise concrete: these are the things a working partnership actually delivers.
Shared opportunities
When a compliance need comes up at your customer, the product and the team are ready; when work comes up on our side, we point it to your expertise.
Training and product knowledge
We train your team on implementing and managing the products and on the situations that come up most; attendance is recorded.
A technical team behind you
For implementation, integration and breach response you reach our team directly. You are not left alone in front of the customer.
The rules we follow ourselves
We apply the controls we recommend to customers in our own processes; data sharing within the partnership is governed in writing too.
How we start
Four steps from application to the first joint engagement. The commercial model is settled in these conversations; we do not publish a rate card, because the scope differs from partner to partner.
Introduction
We talk about what you do and which customer base you work with.
Scope and model
The kind of partnership, who delivers what, and the commercial model are put in writing.
Training
Your team learns the products and the implementation flow; a technical channel is opened.
First engagement
We run the first project together, then simplify how we work from there.
Would you like to become a partner?
Tell us what you do and the kind of collaboration you have in mind; we come back within a few days.
Write to us about partnership