Your ERP, your HR, and Agent Q, in a pocket.
Job cards, attendance, payslips, stock moves, and approvals on a phone, with Agent Q answering from the same ledger. Including when the phone has no signal — which on a plant floor or a basement plant room is most of the time.
iOS and Android·Works offline·Same permissions
What people actually do on a phone.
Scoped to the work that genuinely happens away from a desk. A phone app that tries to be the whole ERP is one nobody uses twice.
For everyone
The things every employee needs and nobody wants to open a laptop for.
Approvals
The queue, with the document and the reasoning attached, so approving on a train is a real option rather than a risk.
Attendance
Check in and out with geolocation where your policy requires it, resolving into the same attendance record.
Leave
Balance, application, and approval, checked against the same leave ledger as everything else.
Expenses
Photograph the receipt at the point of spending, which is the only time anybody reliably has it.
Payslips
The current and historic slips, under the employee's own login and nobody else's.
On the floor and on site
Where the work is, rather than where the desk is.
Job cards
Start, pause, and complete an operation, logging time and quantity against the work order.
Stock movements
Transfers, issues, and receipts with barcode and batch scanning against the camera.
Quality inspections
Readings entered against the template at the point of inspection, with photographs attached to the record.
Field service
The visit, the parts consumed, the customer signature, and the completion status.
Deliveries
Proof of delivery with signature and photograph, written back onto the delivery note.
Offline
The part that decides whether it is used at all.
Works without signal
The data needed for your role is held on the device, so a basement or a plant floor is not an outage.
A visible queue
What is waiting to sync, and how long it has waited — on the device, not implied.
Ordered replay
Queued work submits in order when the connection returns, posting exactly as it would have.
Conflicts surface
Anything that cannot post — a closed period, a changed price, a consumed batch — becomes an exception rather than being dropped.
Survives a restart
The queue persists across an app restart and a device reboot. That is the whole point of it.
Agent Q on a phone
The same agent, the same limits.
Ask from the floor
Operational questions answered from live records, with the documents named, in the place the question actually arises.
Same permissions
The phone is not a looser context. Row-level permissions and redaction apply exactly as on the desktop.
Actions still gated
Anything above a limit routes to a named person. A small screen does not relax a ceiling.
Voice input
For the hands that are holding something else, with the transcript kept on the record.
From store to shop floor.
The second step is the one that decides adoption: a role-scoped app shows five things a person needs, not four hundred they do not.
- 01
Install
From the public app stores, or distributed through your own MDM where policy requires it.
- 02
Scope
The app shows only what the person's role covers, so a machine operator sees job cards rather than a menu of modules.
- 03
Cache
The records that role needs are pulled to the device, sized to the role rather than the database.
- 04
Work
Online or off. Queued work replays in order, and anything that cannot post is raised rather than lost.
The specification.
What a mobile rollout and a security review each need to know.
- Platforms
- iOS and Android, native shell
- Distribution
- Public app stores or your own MDM
- Offline
- Role-scoped local cache with a persistent queue
- Sync
- Ordered replay; conflicts raised as exceptions
- Permissions
- Identical row-level rules to web and API
- Device data
- Encrypted at rest; remote wipe via MDM
- Capture
- Barcode, camera, signature, geolocation
- Auth
- SSO with your identity provider, biometric unlock
What the app deliberately is not.
Scoping a mobile app is mostly deciding what to leave out, so here is what we left out and why.
- Not the whole ERP
- You cannot configure a chart of accounts or build a workflow from the phone. Those are desk jobs and pretending otherwise produces an unusable menu.
- Not offline for everything
- Offline covers the role's own working set. Running a consolidated group report needs a connection, and the app says so rather than failing oddly.
- Not a looser permission context
- Nothing is more accessible because it is on a phone. Where that is inconvenient, the fix is the role, not the app.
- Not indefinitely offline
- A device that has not synced for a long period is stale, and the app will say so and require a sync before it accepts more work.
Next step