Built with your team.
Run by ours.
Every system starts in a scoping session with the people who do the work. We write the blueprint, build it inside your systems, and operate it after go-live.
Built with the team
Each stage starts with what the team says in the room. Switch tabs to follow one process from the first session to go-live.
We open every claim by hand before nine. Sit with the desk for a morning and write down how it actually runs, including the exceptions.
Turn what you saw into a written blueprint: every step, every rule, every approval, and who signs for what.
Build it inside Guidewire and Outlook. Nothing migrated, nothing replaced, and your engineers review every connection before it goes live.
Run it on live claims with the desk approving each letter, then keep operating it after go-live, under the same controls.
What will we build together?
Intake
Claims, submissions and requests, read and filed.
Scope intakeReview
Contracts, policies and site reports checked against your standard, with every exception sent to a person and logged from the start.
Scope a reviewReconciliation
Ledgers, bank files and invoices, matched every morning.
Scope a reconciliationReporting
Connected to your systems of record, so the figures that matter arrive as live charts and filterable views, each one traced back to the record it came from.
Scope the reporting
Lyrion Scoping SessionRequests Open
Map the process in one session.
Our engineers sit with the people who run one process and map how it actually works, exceptions included.
Requests are read by an engineer · Scheduled around your team
- San Francisco or on site
- With the people who run the process
- Written blueprint afterwards
Why request one
What you'll get
The process, mapped
How the work actually runs, written down with the people who do it, including the exceptions nobody wrote down.
Meet the team
Meet the engineers who would scope the system, build it, and run it after go-live.
A written blueprint
What would be built, where it would run and who signs for it, before anything is built.
Nothing is built yet.
The session ends with a written blueprint, not a contract.
Requests are read by an engineer · Nothing is copied out of your systems
FAQ
Frequently asked questions
Who should attend?
The people who run the process, and the person who signs for it. Most sessions start with a small group.
Where does the session take place?
In San Francisco, or on site with your team, wherever the process actually runs.
Which processes are a good fit?
Quoting, intake, document review, reconciliation and renewals are common first choices, in insurance, construction, energy and financial services.
Do we need to prepare anything?
No. Bring the process as it actually runs, including the exceptions. We'll help you decide who else should be in the room.
What happens to our data?
Nothing is copied out, and nothing is uploaded to us. The session works from how the process runs, not from your systems.
What happens after the session?
You receive a written blueprint. If it is worth building, we scope the engagement from there; if not, the blueprint is yours to keep.
Start with one process
Bring the people who run it to a scoping session, and describe the work as it actually happens. The blueprint is written before anything is built.