Case studies

These pages describe client work AR Labs has done, written for someone who wants to see how we approach a real business problem rather than a demo. The first engagement is the design of an enquiry-to-schedule system for a regional in-home music school, and its pages cover the situation, how discovery was run, what the evidence showed, and the design that followed, with diagrams of the workflows and the system architecture.

Clients are not named. Businesses are described by type and region, and people by their role, such as the owner or the administrator. Each page says plainly what stage the work reached: a design is presented as a design, and nothing is described as running unless it is.

The companion pages go deeper into the methods a case study relies on, such as how we map a small business's workflows from screen recordings before designing workflow automation, and how an interface is designed around a decision that stays with a person.

To apply the same approach to your own business, start with the music school scheduling guide or the general guide on how to map a business process before automating it. The client delivery framework describes the stages an engagement runs through.