Processes
Your operating procedures, modelled instead of remembered.
Most businesses run on processes nobody has written down. G1 models them as steps, owners and conditions, so the handover between two people stops being the weakest link.
- Category
- Operations
- Status
- In development
- Depends on
- Nothing
- Connectors
- 4
What it does
Processes, in practice
The parts that matter day to day, not a feature matrix.
- RequestSite
- ApproveBudget holder
- OrderBuying
- ReceiptWarehouseWaiting on a goods receipt — three-way match cannot complete without it.
- Bill matchedFinance
2 instances waiting · routed by rule, escalated after 48 hours
Illustrative product screen — sample data, not a measured result.
Works with
Modules that sit beside this one
Often switched on together
- In developmentExplore
Workflow
Approvals and routing across the business, not just finance.
- PlannedExplore
Inventory
What you hold, where it is, and what it is worth.
- In developmentExplore
Procurement
Requests, orders and receipts that line up with the bill.
- In developmentExplore
Projects
Cost, revenue and progress on the same record.
Industries
Where this does the most work
Problems it removes
What people come to us with
Connects to
Connect what you already use
Connector status is stated honestly. Only file import and export are live today; the rest are planned or built on request.
The layer on top
What G1 notices in this data
Analysis reads the same records the ledger writes, under the same permissions.
Agents that read it
Operations
Processes is on the way. Tell us how you would use it.
What gets built next is decided by the businesses that need it. That conversation is how a module moves up the list.