Research
From research prototype to software that also works outside the lab.
Your method or model works. Now researchers, field workers or external users need to be able to work with it, without help from the person who built it.
From Leuven. With experience at KU Leuven and Scivil, from fieldwork to research data.
What do we build for research?
Zenjoy builds software for research groups and spin-offs: web platforms, research apps and applications around existing models. We turn a working prototype into a product with user roles, reliable data processing and an admin environment. You bring the scientific knowledge; we design, build and maintain the software around it.
Research that finds its way to users
The model works. The product still has to follow.
A prototype helps to test the method. External users also need a clear interface, access and support.
Who enters data, who checks it and which export do researchers need? That decides what goes into the first version.
The original researcher leaves, but the software stays in use. Settle ownership, hosting, documentation and maintenance in time.
Bring input, annotations, corrections and export together, with a clear view of who changes what.
Usable research software supports the method and the work of the people who have to use it.
Software around your research method
A clickable or working prototype to test usage and feasibility. We agree on what stays experimental and what is needed for a next phase.
Collecting data through photos, speech, forms or sensors. With offline use and synchronisation when the context calls for it.
User roles, uploads, annotations, dashboards and exports. Researchers and external users each get a working environment that fits their role.
We connect your existing model to a usable product, with processing, error handling and management. Then we agree on hosting and maintenance.
You remain responsible for the research method and the scientific validation. We take on product design and software development, together with your researchers and IT department.
An existing research package may be enough. Custom software becomes worthwhile with your own models, unusual data flows, fieldwork or external users. Is it mainly about patients or healthcare professionals? Digital health
Often combined with web platforms, mobile apps, targeted AI and Care after the project funding ends.
From research model to daily use
Making an insect model available to growers
MeBioS had a working insect recognition model in a Streamlit prototype. Zenjoy built a platform around it with user roles, mobile photo uploads, processing and an interface to check and correct results. Researchers can export data to CSV or Excel. The original model was kept as it was.
Collecting Flemish speech through citizen science
A lightweight app that lets citizens contribute speech data. The product question: how do we make participation easy while researchers collect usable data? An example of software that supports the research process.
Repeated measurements, manageable for researchers
A short questionnaire for participants, enrolment via QR code and an admin environment for the research team. Personal data and measurement data are kept separate. The patient-facing application is described in more detail on the Digital health page.
Prototype-to-Product Scan
We look at the prototype, code, data, users and management. You get a clearly scoped first version, the technical risks and a proposal for the next step. Privacy and ethics review, solid backups and a watertight retention policy are included where relevant.
Also before funding: a feasibility study or technical assessment at the level of detail the application requires. No guarantee of a grant.
Questions we often get
Often, yes. We look at code, dependencies, permissions and processing. At Phonebox the research model was kept and we built the platform around it. What can be reused, we decide after that exploration.
That depends on the users, data flows, integrations and the state of the prototype. We scope a first usable version within the available budget and estimate management separately. The grant conditions remain your responsibility.
Yes. You know the domain; we take on product development and the technical side. We do not replace the principal investigator or the internal IT department.
That depends on the code that already exists, the integrations and the validation with users. After the exploration we agree on milestones and a feasible first version. We take a funding deadline into account; we do not promise a fixed timeline without a scope.
We agree on that before we build: your IT department, another partner or Zenjoy through Care. We set out who manages hosting, access, documentation and updates, so a researcher leaving does not have to be the end of the road.
Does your research also need to be usable outside the lab?
Show us what already works, who needs to use it and which project deadline applies. Then we look at the next step together.
You talk to someone who thinks along on the substance. No obligation, no standard pitch.