Labo
Real problems, better software.Good tools often start from a very concrete problem. We work with public teams to understand these problems, imagine solutions and build software that can be useful elsewhere too.
01
We start by watching how staff work and listening to what the public needs. Before building anything, we check that new software is the right answer.
Johannes Eckstein, John Freeth and His Circle, 1792. Birmingham Museums Trust.
02
We build a first version and put it in the hands of the people who will use it. Their feedback guides what comes next.
Joseph Wright of Derby, The Alchemist, in Search of the Philosopher’s Stone, Discovers Phosphorus, 1771. Derby Museum and Art Gallery.
03
We build, deploy and document the software. The aim: that your teams can use it and develop it for the long term, without depending on us.
Pieter Bruegel the Elder, The Harvesters, 1565. Metropolitan Museum of Art.
Document search, help with writing, controlled automation and integration with existing tools.
Open software that other administrations can take up, with APIs and architectures built to last.
You can come with a problem and no technical solution in mind: a procedure that takes too long, a tool your staff work around, requests nobody manages to keep up with.
We study it with you, then choose together the right form: a partnership, a prototype, or new software that other administrations can take up.
Sometimes the right answer is to build nothing. In that case, we tell you.
Tell us about your project, even if it is only just beginning. We will be glad to discuss it with you.
Or book a call in the calendar.
[Cal.com calendar: link to confirm]