At The Lookout Way, important product knowledge lives across code, workflows, documentation, team conversations and deep internal expertise.

For customer-facing and operational teams, that can make some questions hard to answer quickly. Not because the knowledge doesn't exist, but because it often sits between technical logic, product context and operational experience.

Compiler gave The Lookout Way a faster way to reach the product knowledge inside the codebase and turn it into something the wider business could use.

The challenge

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 complexity creates questions that don't always resolve neatly through a help article, a search or one person’s memory.

What changed last week?
Who made this update?
How often does this API run?
What happens between invoice submission and claim approval?
How are public holidays handled in budget workflows?

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

Compiler gave teams a faster first place to ask, with answers grounded in the code and workflows behind the product.

From code-level logic to support context

The shift showed up quickly in customer support.

In one internal discussion, the team needed to understand how budgets built from rosters handled public holiday rates. The question was checked through Compiler first, helping the team surface what the system supported, where customer judgement still applied and how the behaviour could be explained clearly.

“Compiler is changing our world.”

Kate Parkin
Chief Customer Officer, The Lookout Way

Kate later connected the impact directly to ticket movement:

“For the first time ever, we are getting ticket velocity up.”

Compiler did not remove the need for expertise. It gave support teams more context at the start of an investigation, helping them move faster, ask better follow-up questions and reduce reliance on technical handover.

From one answer to reusable knowledge

As teams became more comfortable using Compiler, the value moved beyond one-off answers.

The training team used it to work through complex product questions, understand the logic behind them and turn that understanding into material other people could use.

“The training team have been using this to get answers to complex questions but also build training material and articles.”

Jodi Kaur
Training Operations Lead, The Lookout Way

The same pattern appeared in customer-facing preparation, with sales using Compiler before an important demo.

The important shift was not just that Compiler could answer questions. It helped teams turn product knowledge into support answers, training content, documentation and more confident customer conversations.

From technical change to business context

Compiler also helped product and engineering context travel further through the business.

In one internal update, 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, Compiler helped turn them into a clearer changelog for the wider team.

That is where the broader value became clear: Compiler was helping product knowledge move from code into everyday work.

From useful tool to working habit

Because The Lookout Way operates in a sensitive care environment, adoption depended on trust. Compiler was added to the company’s approved AI tools for responsible use, giving teams a clearer way to use it in everyday work.

Within the first few months of internal use, the pattern was visible in the product data:

1.9K conversations
3.8K messages
104 shared answers
Growing weekly active usage

The stronger signal was not the initial launch. It was that people kept coming back.

Support investigations, training material, demo preparation, product changes, customer explanations and internal handover all created new reasons to ask.

Shared understanding across the business

Compiler didn't replace The Lookout Way’s internal expertise. It made that expertise easier to access, reuse and share.

It became part of how product knowledge moves through the organisation: from code and workflows into support answers, training material, demos, changelogs and customer conversations.