Prioritize the likely answer path
Leroy is designed to avoid unnecessary work when exact Turnover evidence can answer the question quickly, while still escalating to deeper reasoning when the request needs it.
Turnover Intelligence
Use the knowledge your operation already has, faster.
Turnover Intelligence is the enhanced reasoning and automation layer for Turnover Core. Leroy was built in-house to prioritize speed and source-grounded reasoning. Auto Jobs watch supported Program conditions. Advanced TurnBase Context Packets and the Intelligence Import Library help teams reuse knowledge instead of rebuilding context from scratch.
Leroy advanced reasoningAuto Jobs + custom triggersAdvanced TurnBase context
One intelligence layer
LeroyFAST + GROUNDED
Proprietary in-house reasoning and retrieval using authorized Turnover evidence.
Auto JobsWATCH + PREPARE
Recurring oversight, trigger checks, notifications, and supported Program-wide intelligence work.
TurnBaseCONTEXT
Advanced Context Packets and reusable curated knowledge layered onto customer-owned TurnBase content.
Leroy
Built in-house to prioritize speed without detaching the answer from evidence.
Leroy uses a proprietary reasoning and retrieval architecture developed inside Turnover. The method itself remains confidential; the customer-facing result is designed to be fast, role-aware, evidence-backed, and useful across real Program work.
Keep the sources visible
Where supported, answers retain record identity, scope, source, freshness, and the evidence that produced the response.
Reason in the user's context
The same Program question can matter differently to an operator, engineer, maintenance person, project manager, or leader. Leroy can account for authorized role context without broadening permissions.
REAL TURNOVER SOFTWARE · CORE + INTELLIGENCE
The fault came back. The team’s experience was ready.
Follow a Line 8 Oven drive fault from a live record, through Leroy’s historical search, to a saved TechNote and the shared TurnBase knowledge pool.
Five moments. One connected record of what the team learned.
Active work in TurnoverActual application interface
01 · LIVE WORK
A drive faults on Line 8 Oven
A technician captures the fault in a Technical LiveNote while the issue is active.
Why it matters: Core records the issue; Leroy can assist when Intelligence is enabled.
1 / 5
Showroom incident shown in the real Turnover interface. Historical TechNotes are context to verify, not automatically approved instructions. New TechNotes become available through the supported TurnBase sync/indexing process.
See the Core technical workflow →Auto Jobs + notifications
Let Turnover keep checking after the screen is closed.
Auto Jobs can work across supported Program areas, not just TurnBase. They can prepare recurring intelligence work, evaluate customer-defined conditions, and notify designated people when configured criteria are met.
Conditions that match your work
Authorized teams can configure relevant conditions against supported Program information rather than relying only on a fixed list of alerts. Availability depends on the job type, permissions, and eligible evidence.
Recurring reviews
Use supported jobs for aging work, project status, safety follow-up, inventory, management summaries, and other recurring oversight that would otherwise be rebuilt manually.
Tell the people who need to know
When configured criteria are met, automatic notifications can surface the result to designated recipients without requiring them to keep the Program open.
Advanced TurnBase
TurnBase stays useful in Core. Intelligence makes it more computationally useful.
Think of it as a shared pool of experience. Completed TechNotes can join the Program-wide TurnBase source through supported synchronization. Authorized users can find that accumulated history, and Leroy can use relevant indexed records when Intelligence is enabled.
Core users can capture, browse, search, and export authorized customer-owned TurnBase knowledge. Intelligence can select relevant sources, connect TurnBase with related Program evidence, and build richer Context Packets for Leroy or approved external-model analysis.
- Customer-owned knowledge remains exportable through authorized Core workflows
- Advanced Context Packets can combine relevant knowledge with connected Program evidence
- Permissions still determine what a user or job can retrieve
- External AI use remains a deliberate customer-directed workflow rather than unrestricted live access
TurnBase value path
CaptureCORE
Preserve useful organizational knowledge while the people who know it are still available.
ExportCORE
Take authorized customer-owned knowledge into approved analysis workflows.
Connect + reasonINTELLIGENCE
Build richer context, select related evidence, and use that knowledge directly with Leroy.
Intelligence Import Library
Do not make every customer rebuild the same useful reference layer.
Intelligence customers can use a shared library of Turnover-curated resources, then import or subscribe to the pieces that fit their operation.
Names people actually use
Equipment, manufacturer, product, acronym, and terminology aliases can help connect different ways people refer to the same thing.
Reusable structures
Templates, indexes, knowledge structures, and industry starter resources can shorten the path from empty repository to useful organizational context.
Manuals and technical resources
Turnover can curate manuals or other reference material where redistribution rights permit. Where they do not, Turnover can preserve metadata or links and let the customer attach an authorized copy.
Founding Intelligence pricing
+$10 per user each month, Program-wide.
Founding Customers receive the Intelligence layer at 50% off the planned +$20 standard rate. Intelligence is enabled for the Program and billed across every user in that Program. Local Admin controls which authorized users can use specific Intelligence capabilities. Core remains the required working system underneath it.