LUdev

We build software at Leiden University.

Student teams of about six, supervised by faculty staff, deliver a scoped prototype or MVP over one academic semester (February–June).

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 assembles teams of final-year bachelor students (Computer Science, Data Science & AI, Bioinformatics, Informatics & Economics at Leiden University) to execute software projects within a fixed academic semester (February–June). Projects are selected based on feasibility, educational value, and clarity of scope. Each team works in Agile sprints with biweekly check-ins and faculty supervision. Deliverables typically include a functional prototype or MVP, source code, and documentation.

This model differs from commercial development: timelines are fixed, scope must be well defined upfront, and outcomes prioritise learning and feasibility over production guarantees.

Team & process

A team consists of approximately six students who together dedicate around 500 hours in total to your project. The team is self-organizing and works according to Agile methodologies, taking responsibility for planning, task allocation, and day-to-day collaboration. Development is structured around defined deliverables (see our timeline), through which students iteratively familiarize themselves with your organization and context, refine requirements, and prioritize development.

Timeline

The project lasts one academic semester (February–June, 5 months). Students work in biweekly sprints with at least biweekly meetings with the client. Each team is supported by an experienced student mentor, with whom they meet weekly. A midterm evaluation is conducted by faculty and teaching staff. More details can be found in the project timeline.

Compared with internships

Teams work largely independently from your internal processes, part-time, and remote from the university, resulting in minimal integration overhead. LUdev is responsible for supervision and grading, allowing you to focus on product direction and feedback rather than day-to-day management. Additionally, the focus is on delivering a clearly scoped MVP rather than open-ended placement work.

A straightforward collaboration that respects your time and delivers concrete outcomes

How we work

1. Submit your project

Submit a clearly defined project proposal. Projects are evaluated on feasibility within one semester, technical depth, and educational value. The project must involve a substantial software development component; proposals focused primarily on research with little to no code output are not suitable.

2. Matching & scoping

A team of approximately six students is assigned based on skill fit and interest. Together, you refine the scope, success criteria, and constraints. LUdev transitions to a supervisory role; day-to-day collaboration takes place directly with the student team.

3. Development & delivery

Development runs from February to June in biweekly sprints. You participate in regular progress meetings and provide timely feedback. The project concludes with the delivery of a prototype or MVP, source code, and agreed-upon documentation. The semester wraps up with a public project fair — see how the latest edition went.

Active involvement increases project success

Client responsibilities

Kickoff

Be available (online or in person) for the project kickoff in February.

Meetings

Participate in biweekly meetings with your student team.

Feedback

Provide feedback to your student team on their demos within a few days to maintain progress.

Time commitment

Commit approximately 1 hour per week on average.

Preparation

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

Evaluation

Complete short midterm and final evaluation questionnaires. These are taken into account during the grading process.

What to expect when working with LUdev

Our approach & deliverables

Partnerships are two-way investments: you receive fresh perspectives and software that may range from a prototype to a fully working solution, while students gain real-world experience. See our portfolio for previous outcomes.

  • Realistic outcomes

    1. A focused MVP or working prototype, including source code and run instructions.
    2. A chance to meet and work with talented students who may become future employees.
    3. A mutual learning experience with potential for continued collaboration. It is not uncommon for students to be offered internships or to continue collaboration beyond LUdev.
    4. Software suitable for evaluation, experimentation, or as a foundation for further development.
  • Not a guarantee

    Projects are executed in an academic setting. No guarantees are made regarding delivery timelines, completeness, or production readiness. Software is provided "as-is" without warranties. No hosting, maintenance, or post-project support is 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

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.

Get started with LUdev

Projects run from February to June and require active client participation.

Meet the team

Current Board

LUdev is led by students, 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.