Half the company uses it.
Every month.

The Lookout Way operates in a high-context care environment, where rostering, budgets, service plans, funding, claims, support and reporting all interact inside one platform. That creates questions that don’t resolve neatly through a help article, a search or one person’s memory.

Before Compiler, answering them often meant finding the right person, searching through past conversations, checking documentation or asking engineering to explain how the system behaved.

The shift showed up quickly in customer support. When the team needed to understand how budgets built from rosters handled public holiday rates, they checked it through Compiler first.

It didn’t remove the need for expertise. It gave support more context at the start of an investigation, so they could move faster, ask better follow-up questions and rely less on technical handover.

As teams got comfortable, the value moved beyond one-off answers. The training team used it to work through complex product questions and turn that understanding into material other people could use. Sales used it to prepare for an important demo.

CTO Tate Johnson used Compiler to generate a review of recent product changes from commit activity. Instead of leaving technical updates buried in commit history, it turned them into a clearer changelog for the wider team.

Product knowledge was moving from code into everyday work.

Because The Lookout Way works in a sensitive care environment, adoption depended on trust. Compiler was added to the company’s approved AI tools for responsible use.

The stronger signal wasn’t the launch. It was that people kept coming back.

Compiler didn’t replace The Lookout Way’s internal expertise. It made that expertise easier to access, reuse and share: from code and workflows into support answers, training material, demos, changelogs and customer conversations.