How we work

We don't build in the dark

Most software vendors hand you a requirements spreadsheet and disappear for six months. We think that's how programs end up with software that fights their practice.

Here's how a Clair build actually works

Sketch — together

A working session with your team, at a whiteboard. We bring the platform; you bring the program. We leave with a shared picture, not a contract exhibit.

Prototype

We build something clickable — a thing your staff can touch, not a spec to read.

Test-drive

Your frontline staff walk real (anonymized) scenarios through the prototype and tell us what's wrong. That's the point. We want it wrong now, on a prototype, not in production.

Refine, then build

We iterate until it fits your practice — and only then write it into the platform.

The pattern underneath: your program's framework is yours. Clair doesn't impose a methodology. We model the phases, teams, plans, and criteria you already run — and make them effortless to operate.

Start with a sketch.

The first working session costs you 60 minutes and a whiteboard.

Book a working session