Tudu

Matthew Martin has spent more than a decade in early years. He runs Little Beehive, a group of nurseries, and like every provider he was carrying more and more paperwork: risk assessments to keep current, daily checklists across every room and outdoor space, problems to log and chase, quality checks to prove. All of it on paper, in folders, in different hands.

Paper fails twice. It will not tell you what has been done today, and it cannot prove what was done six months ago. When an inspector asks, someone goes looking.

Before this project we had already built Matthew a first, throwaway version to test the idea. It worked, so we put it aside and started the real product from nothing, because building for one nursery and building for thousands are two different jobs.

We started with the nursery day, not the software. What happens at 8am in a pre-school room, who does it, who checks it, and what happens when something is wrong. That gave us the shape: areas, checklists with time windows, risks and quality checks attached to the jobs people already do, and a record that writes itself.

The app is for someone standing up, holding a phone, with children in the room. Big buttons, one thumb, a clear submit, and a checklist you can finish between two other jobs. Every entry records who did it and when. Managers see every area live and a score they can act on. Owners and inspectors get the evidence without a search.

Five things sit in the one platform: risk assessments, daily checklists, quality checks, problem reporting and staff training. Each can be set up to suit the provider, because a childminder's day and a 90 place nursery's day are nothing alike.

There was no brand when we started. No logo, no colours, no idea of how it should sound. Our design team built Tudu's identity from a set of conversations: the wordmark, the mint and deep green palette, the illustrations and the tone. It had to be warm enough for a nursery and credible enough to sell to a group.

We built the marketing site too, with a separate landing page for each of the three audiences, plus pricing, demo booking and a blog. Settings, clubs and childminders buy for different reasons, so each gets its own pitch rather than one generic message.

Matthew's vision mostly lived in his head. A lot of our job was getting it out, ordering it, and questioning the parts that needed it. Our developers did not just build the brief. They challenged it, and often proposed a better answer.

It is easy to build what someone asks for. Building what they actually need takes a team willing to push back and a client willing to listen. Tudu came out of that, not out of a spec being ticked off.