Azulou

Azulou covers products, services, contacts, POS, work orders, finance and scheduling, with modules customers can install and remove. Development and design ran at the same time, and every customer request pulled the product in a different direction.

Many of those requests came from pet shops. Specializing brought new rules: the owner is the customer and the pet is a sub-customer, with its own history.

A CSD matrix and Sexy Canvas to align what we knew about the two profiles: the business owner, who decides what each employee can see, and the employee, who runs the day-to-day.

Then, mapping the core flows, prioritized by effort × impact with the stakeholders. In a modular system, a loose rule becomes a bug. That's why each flow got user story mapping with its rules tied down before it went to the screen.

A benchmark of Quaddro, Reservio and Gendo showed the same bottleneck in all of them: customer data typed by hand when booking. Azulou already had the customer base, and that became an advantage.

Web and app with the same language: scheduling, sales, finance and reports, with the modules each business chooses to turn on.