Talk to UsScoping Session
Systems
AI SystemsMethodWorkOperationIndustriesField Notes
Solutions
EnterpriseRegulated IndustriesProcessesIntake and ServiceDocument ReviewReconciliation
Integration
Systems of RecordModel GovernanceAudit TrailChange ControlBlueprintData Residency
Company
AboutEngagementsSecurityOversightCareersContact
EngagementsNews
Talk to UsScoping Session
NewField noteMoving AI beyond the pilot

Start from
the work.

Our engineers sit with the people who do the job, write down how it actually runs, and build the system inside the platforms your teams already use.

lyrion scope --process renewals --with underwriting

Talk to us about a process

Read the field notesChangelogOur method

Our method

Scoping

We start with the people who do the job, not with a template.

  • The process recorded as it actually runs, including the exceptions nobody documented
  • Rules taken from the people who apply them
  • Every finding written down for your team to check
systems/renewals underwriting

lyrion scope --process renewals --with underwriting

Thought for 2.5s

Recording how renewals run today, with the underwriting desk

The process as it actually runs

The exceptions nobody documented

The rules, from the people who apply them

Every finding written down for your team to check

blueprint · review

Blueprint

A written blueprint before anything is built.

  • Nothing is built until the blueprint is signed off by your team
  • Comment on any step, change it, or rewrite it entirely
  • Every approved change shows up as a clean, reviewable diff
systems/renewals underwriting

Route renewal exceptions to the underwriting desk.

Thought for 4.1s

blueprint.md

  1. The task
  2. Route renewals outside the rules to an underwriter, with the working attached.
  3. Approach
  4. • Read the renewal rules from the policy admin system.
  5. • Flag every case that crosses a referral threshold.
  6. • Draft the referral for the underwriter to approve.

[a]pprove[c]omment[q]uit blueprint

blueprint · review

Connections

Built into your systems, reviewed by your engineers.

  • Every connection to a system of record listed in one place
  • Read-only by default, write access only where the blueprint says so
  • Salesforce, SAP, Guidewire, ServiceNow, Snowflake and your own systems
systems/renewals underwriting

review the policy admin connection

ApprovalsConnectionsScopingSystems of record

/ to searchEnvironment ⌄

› policy-admin(read)[approved]

› claims-system v2(read)[approved]

› ledger v4(read)[approved]

› audit-trail v1(read)[approved]

blueprint · review

Questions

We ask the questions that decide how a system behaves.

  • Ambiguous rules get a clear question for the person who owns them
  • Who signs, when, and on what evidence
  • Answers go straight into the blueprint
systems/renewals underwriting

Waiting on answers for 3 questions[blueprint review]

1Route to the underwriterEvery case outside the rules goes to a person

2Hold for reviewThe case waits until the desk opens

3Approve within limitsInside agreed limits, drafted for sign-off

4OtherDefine the rule yourself

[1/3]↑/↓ navigate←/→ questionEnter select

blueprint · review

Parallel work

Several engineers and systems work through a process at once.

  • Large processes are split into parts that can be built and checked separately
  • Each part keeps its own context and its own owner
  • Every part is reviewed before it joins the whole
systems/renewals underwriting

exploreExplore the renewal queueexplore · blueprint

exploreExplore the policy recordsexplore · blueprint

exploreExplore the claims historyexplore · blueprint

exploreExplore the referral rulesexplore · blueprint

exploreExplore the approval stepsexplore · blueprint

exploreExplore the audit trailexplore · blueprint

find where renewal exceptions are decided today

blueprint · review

Talk to us about a process

One scoping session to start. Every process, every system of record, every industry.

lyrion scope --process renewals --with underwriting

Everything a system needs in production

One firm for the whole path: scope, build, run and extend.

  • Written blueprintSigned off before anything is built
  • Parallel workRun beside the existing process until its output is trusted
  • ScopingReusable rules taken from the people who do the job
  • ApprovalsChecks on every record a system changes
  • Systems of recordBuilt into the platforms your teams already use
  • Your conventionsYour naming, your controls, your review steps
  • ContextDecisions carried from one department to the next
  • Record searchEvery figure traced to the record it came from
  • Multi-system changesOne change across several systems, reviewed once
  • Change controlNothing reaches production without your approval
  • ExceptionsHanded to a person with the working attached
  • MonitoringWatched in production by the engineers who built it
  • Your engineers' reviewEvery connection is code your team can read and sign off
  • Runs without a screenInvisible systems that work behind your software
  • InterfacesOr a screen your team works in, decided at scoping
  • Your environmentAble to run inside your own environment where residency requires it
  • OperationWe run what we build, after go-live
  • Your lookInterfaces in your own colours and terms

Start with one process

Tell us about the process you want handled. We start with a scoping session with the people who run it.

lyrion scope --process renewals --with underwriting
Read the field notesTalk to Us