LUdev

Software development & engineering at Leiden University

Student software engineering teams deliver a scoped prototype or MVP over one academic semester (February–June), supervised by experienced, academic staff.

Trusted by partners across sectors

  • Accenture
  • Belastingdienst (Netherlands Tax Authority)
  • C-Job Naval Architects
  • Centre for Human Drug Research (CHDR)
  • The Hague University of Applied Sciences
  • Eskişehir Technical University
  • Naturalis Biodiversity Center
  • Record Industry: Europe's vinyl pressing plant
  • Delft University of Technology (TU Delft)
  • Leiden University
  • University of Seville

Why collaborate with us

LUdev in brief

LUdev connects organisations with dedicated software development teams of final-year bachelor students in Computer Science and Data Science & AI at Leiden University. Through our Software Engineering course, these teams work on real-world challenges, where they translate project proposals into tangible software deliverables over one academic semester (February-June). Teams typically consist of six students, following the regular Computer Science and Data Science & AI curricula as well as those specialising in areas such as bioinformatics and business.

This model differs from traditional commercial software development: timelines are fixed, scope must be clearly defined upfront, and projects prioritise feasibility and educational value. Production readiness is not guaranteed.

Team & process

A team consists of approximately six students, who collectively contribute around 500 hours to your project. Teams are self-organising and work according to Agile methodologies, taking responsibility for planning, task allocation, and day-to-day collaboration. Through iterative development, students familiarise themselves with your organisation and its context, refine requirements, and prioritise development.

Timeline

Projects run for one academic semester (February-June, approximately five months). Students work in biweekly sprints and meet with you at least once every two weeks to discuss progress and gather feedback. Each team is supported by an experienced student mentor, with whom they meet weekly. Faculty staff provide academic supervision and assess teams at midterm and at the end of the semester. See our project timeline for more details.

Compared with internships

Rather than integrating individual students into your organisation, you work with an independent development team. Students work part-time and primarily remotely, with LUdev providing organisational support and teaching staff academic supervision. This keeps integration overhead low and lets you focus on product direction and feedback rather than day-to-day management. Unlike an open-ended placement, the collaboration centres on a clearly scoped software project.

From project proposal to working software

How we work

1. Submit your project

Submit a project proposal describing your software development challenge. Projects are evaluated based on their feasibility within one semester, technical depth, educational value, and clarity of scope. A substantial software development component is essential; proposals focused primarily on research, or with little or no software development are not suitable.

2. Matching & scoping

A team of approximately six students is assigned based on their interests and relevant skills. Together, you refine the project scope, success criteria, and constraints to establish a clear direction for the semester. LUdev facilitates the matching and scoping process and ensures a well-defined starting point for the project.

3. Development & delivery

Development runs from February to June in biweekly sprints. Day-to-day collaboration takes place directly with the student team, while LUdev continues to provide organisational support throughout the semester. The project concludes with the delivery of a prototype or MVP, source code, and agreed-upon documentation. The semester wraps up with our Project Fair — see how the latest edition went.

A successful collaboration requires active involvement

Client responsibilities

Kickoff

Be available, either online or in person, for the project kickoff in February.

Meetings

Participate in biweekly meetings with your student team to discuss progress and align on priorities.

Feedback

Provide feedback on demonstrations within a few days to help the team maintain momentum and make informed development decisions.

Time commitment

Commit approximately one hour per week on average throughout the project. See our project timeline for an overview of key milestones and expected involvement.

Preparation

Provide all required data, systems, and specialised hardware before the project starts. LUdev provides a development environment for students to work in and track their progress.

Evaluation

Complete short midterm and final evaluation questionnaires. Your feedback is taken into account during the grading process.

What to expect when working with LUdev

Our approach & deliverables

A collaboration with LUdev is a two-way investment. You get a dedicated student team working on a software development challenge relevant to your organisation, while students gain practical experience applying their knowledge to a real-world project. See our portfolio for examples of previous projects and their outcomes

  • What you can expect

    1. A concrete software deliverable. A functional prototype or MVP, including source code and instructions for running the software.
    2. Fresh perspectives. An opportunity to work with students bringing new ideas, knowledge, and approaches to your organisation.
    3. Potential for continued collaboration. It is not uncommon for students to be offered internships or to continue working with their project partners after the LUdev project has concluded.
    4. A foundation for further development. Software that can be evaluated, experimented with, and used as a starting point for future development.
  • What we cannot guarantee

    Software development is inherently challenging, and project outcomes can be difficult to predict. Our student teams carry out projects as part of their Software Engineering course, alongside other academic commitments. While teams work towards the agreed deliverables throughout the semester, no guarantees can be made regarding completeness or production readiness. Software is provided "as-is", without warranties. Hosting, maintenance, and post-project support are not included.

Usage & ownership

  • Intellectual property remains with LUdev and/or the student team until formally transferred.
  • Before transfer, usage is limited to evaluation and internal purposes.
  • A standard NDA/CDA can be provided upon request. Only the student team signs the NDA/CDA; course staff do not. Any requirement for an NDA/CDA must be communicated before project acceptance.

Transparent & fair

Costs

We believe financial constraints should not stand in the way of a potential collaboration. At the same time, we consider it fair that organisations with project funding contribute, where possible, towards supporting LUdev and our educational initiative.

Non-commercial projects

€500, suitable for non-profit work, including charitable and educational initiatives.

Academic projects

€2,500, suitable for projects part of competitively funded research (e.g., NWO or EU projects).

Free, for projects part of non-competitively funded research at a scientific institute.

Commercial projects

€5,000 per project, suitable for commercial collaborations.

€2,500 for qualifying, commercial startups — see our Terms of Service for eligibility criteria.

Meet the team

Current Board

LUdev is student-led, with support from faculty in both advisory and supervisory roles. Together, they run the organisation and guide project teams.

The 2026/2027 LUdev board to the side of the Leiden University Faculty of Science Gorlaeus building.
2026/2027 LUdev board

Board members for 2026/2027

  • Jort van Leenen
    Jort van Leenen, CEO

    Jort van Leenen

    CEO

    I'm a final-year MSc Computer Science student with a strong interest in software engineering, especially as applied to formal methods. After serving as CTO of LUdev, I'm staying on for another year, now as CEO. In this role, I lead the organization's overall direction and management, with a focus on strengthening our partnerships, supporting our team, and growing LUdev as a bridge between students, academia, and industry.

  • Niels Versteeg
    Niels Versteeg, CTO

    Niels Versteeg

    CTO

    As a final-year Computer Science MSc student specializing in Advanced Computing and Systems, I have developed a strong interest in software engineering, systems, and infrastructure. As this year's CTO, I look forward to applying this systems knowledge in practice by helping students and clients with technical challenges, supporting projects and deployments, and building and maintaining LUdev's own infrastructure.

  • Catherine Smeyers
    Catherine Smeyers, CCO

    Catherine Smeyers

    CCO

    As a returning member of LUdev, I am excited to continue contributing to the organization, this time as CCO. Currently pursuing an MSc in Computer Science, I look forward to combining my technical background with my role in managing partnerships, maintaining relationships with existing and new companies, and creating opportunities for collaboration between businesses and students.

  • Lana van Sprang
    Lana van Sprang, COO

    Lana van Sprang

    COO

    As a final-year MSc student in Computer Science: Artificial Intelligence, I am particularly interested in Software Engineering and Human-Centered AI, and I am excited to explore these areas further through LUdev. As COO, I focus on keeping LUdev organized and moving forward. I am responsible for overseeing our internal operations, coordinating our activities, and supporting the other board members where needed.