The operating layer for your business
Your business.
Working as one.
lgOS is being built as one operating layer across your business: finance, operations, documents and decisions. It is designed to work with the software you already use, prepare routine work, and bring you the issues that need your decision.
In development · Not yet generally available
An invoice that needs review
Supplier invoice
Example Supply Co.
- Invoice number
- INV-10482
- Total
- $2,450.00
- Status
- Needs review
- Reason
- A required invoice detail could not be established from the document.
- Preparation
- Payable not prepared — review required.
01The problem
Your business has systems.
It doesn’t have a system.
Documents, email, finances, projects and commitments live in different places. Your team does the work of bringing them together, checking the details, and following up.
02The approach
Keep the software. Add the layer.
lgOS is being built to organise that information across the tools you already use, around your companies, projects and decisions, without losing where it came from.
03The first workflow
Details brought together.
For supplier invoices, lgOS checks required details and, when those checks permit it, prepares an internal, unapproved payable for review.
Operate by exception.
When a required detail remains unresolved, the invoice comes to you with its source document, the issue, and the review status.
The issue, with its context.
The source document, proposed details, and reason for review — together in one view.
An invoice that needs review
Supplier invoice
Example Supply Co.
- Invoice number
- INV-10482
- Total
- $2,450.00
- Status
- Needs review
- Reason
- A required invoice detail could not be established from the document.
- Preparation
- Payable not prepared — review required.
Prepared for human review — not posted or paid.
Final coding, tax treatment, approval, posting and payment remain with the people authorised to perform them.
04Across the business
One layer across the whole business.
Invoices are the first workflow. The same approach is being developed across the work of running a business: gather the supporting records, prepare the routine work, bring you the exceptions, and leave the decision with you.
The questions it is being built to answer, one workflow at a time:
- ExecutiveWhat needs my decision this week, and why?Current focus
- KnowledgeWhere is the document that explains this?Current focus
- AccountingWhich invoices are ready, and which need a person?Current focus
- FinanceWhat changed, and which records explain it?Direction
- OperationsWhat is overdue, unresolved, or coming due?Direction
- AcquisitionsHow does the next company join the same way of working?Direction
Designed for owners managing several companies: see across the group while keeping each company’s information separate.
Our objective
Reduce administrative overhead without sacrificing accuracy, control, or customer experience.
05Control
Intelligence is not authority.
- See the source.
- Work should be reviewed alongside its supporting records.
- Understand the issue.
- An exception should explain what needs attention and why.
- Keep the decision.
- Preparing work is not the same as approving it.
06Operational replay
Prove it before production.
Selected workflows can be tested in isolation, without making changes in connected business systems.
Your business already has software.
Make it work as one.
lgOS is in development and not yet generally available. Tell us about your business and register your interest in future access.
Submitting a request does not create an account or guarantee access.