Office and collaboration
Microsoft 365 and Copilot
Outlook, Teams and SharePoint. We help you choose between Copilot, Copilot Studio and your own workflow.
Integrations
AI only works once it knows your systems.
An AI workflow has to read and write where your work already lives: in your mailbox, your CRM or your case files. Zenjoy has been building integrations between software for fifteen years. We use that experience to fit AI safely into your systems.
At a glance
- First
- We check what your software can already do itself
- Then
- The simplest connection that you can still maintain three years from now
- Always
- As little access as possible, and an AI fact sheet for every integration
Honest advice
Sometimes you don’t need us
Microsoft, Odoo, Teamleader and Exact are building AI into their own software. Sensitive data alone is no reason for custom work. A built-in feature is enough if the task stays within one package and the package meets your agreements on access, hosting and retention. A custom integration makes sense if the task spans several systems, if you need a review step or logging that the package doesn’t offer, or if you want to choose yourself which model sees which fields.
-
One package, a standard task
Our adviceUse the AI that’s already in your software.
What we doWe help with agreements, permissions and a short training for your team.
-
Data from several systems
Our adviceAn integration with a fixed review step.
What we doWe build, test and maintain the connection, with an AI fact sheet to go with it.
-
Sensitive data or strict rules
Our adviceCheck first, then choose.
What we doWe hold the built-in feature up against your agreements: where the model runs, who sees what and what gets stored. If it’s enough, you stick with it. If not, we build something custom.
Systems
What we connect AI to
We chose the systems that SMEs, care, education, research and non-profits run on. The most important ones have their own page.
ERP and administration
Odoo
Customer data, contracts and invoicing. Zenjoy has already built integrations with SAP, Odoo, Salesforce and Airtable, among others.
Accounting
Accounting and Peppol
Exact Online, Octopus, Billit and Yuki. Peppol invoices already arrive as data; we help with what’s left.
Research
Research systems
Publications and research data. Fetch, link and keep data from research repositories and databases up to date automatically.
Education
Smartschool
Smartschool only allows limited integrations. So a workflow usually starts outside Smartschool, for example in the school office’s mailbox, and connects where Smartschool allows it.
CRM
Teamleader, HubSpot and Salesforce
Requests, contacts and campaigns. Forms, emails and notes land in your CRM in a structured way, with no retyping.
Is your software not listed?
We check whether there’s an API, webhooks or a secure export, and tell you honestly whether an integration is feasible.
How we connect
Connecting with as little access as possible
Minimal permissions
An integration only sees the fields the task needs. Each integration gets its own key, which you can revoke yourself.
Tested on what goes wrong
We test with incomplete data, duplicate records and a system that briefly stops responding. Not just with the ideal case.
Direct where possible
Zapier or n8n is handy for a quick start, but every extra step can break. We choose what you can still maintain three years from now.
An AI fact sheet for every integration
Which data passes through, which model reads it, where it runs and how you stop it: all on one page.
What AI may do on its own
Some doors open both ways, others only one way.
Opens both ways
AI may do this itself
What you can undo and what stays inside your organisation.
- Filling in a field
- Labelling an email
- Preparing a draft
Opens only one way
A colleague first
What goes outside or decides about a person.
- Sending an email
- Deciding about a customer, pupil or member
- Final booking or payment
What AI may carry out on its own, when someone has to approve and when the workflow stops: we agree on it up front. It’s in the AI fact sheet.
Who builds it
A new brand, not new to software that keeps working
Ethic is the AI studio of Zenjoy, the digital product studio from Leuven. Since 2011, Zenjoy has designed, built and maintained software, platforms and integrations for more than 400 organisations. You can tell from how we build AI: with tests, documentation and maintenance, so it still works three years from now.
We’ve been using AI in our own work for years. With Ethic, we now bring that experience to organisations where it matters: care, education, research and non-profits.
- You talk to the people who build
No account manager in between: whoever designs your project also builds it. - Code, documentation and access in your name
The prompts too. If you later want to carry on with your own team or another partner, you can. - Maintenance and support after launch, by the same team
If a supplier changes something, the same people who built it make the adjustments.
15 years
building and maintaining software
400+
organisations
4 years
using AI daily in our own work
Phonebox · KU Leuven
What Zenjoy built around researchers’ AI
The researchers built an AI model that recognises insects on sticky traps. Zenjoy built the product around it: web application, cloud and UX, so the model became usable in the field.
Do we have to change software?
No. We work with the software you use today. Only if a system has no secure way of exchanging data at all do we discuss alternatives.
Why not just use Zapier or n8n?
They’re handy for a quick start, and sometimes we recommend them too. For a workflow that has to run for years, every extra step is another subscription and another place where something can break. For each integration, we choose what’s easiest for you to maintain.
What if the supplier changes its software?
Every integration has checks and error alerts. Under a maintenance agreement, we follow the supplier’s changes and adapt the integration before your team notices any trouble.
What data does the AI see?
Only the fields we agree in advance. That’s in the AI fact sheet, together with the model that reads the data and where it runs.
Who owns the integration?
You do. Code, documentation and access are in your organisation’s name. You can carry on with us, with your own team or with another partner.
How much time does this take from our team?
Not much. We need someone who knows the process and can give access to the systems. Then your team tests the integration with real cases before it goes live.
Which systems need to talk to each other?
Tell us which software you use and where your team is still retyping. We’ll tell you honestly what your software can do itself and where an integration pays off.