Work moves between products. The record moves with it.
When one product finishes its part, the next starts with the context already attached — by event, not by re-keying. These are the journeys MaeOne is designed around.
Five journeys across the suite.
Pick a journey to see who does what, which product owns each step, and what the person at the end receives.
- 01 · MaeOne People
The employee record exists before day one
No access is granted and nothing is provisioned yet.
- 02 · MaeOne Desk
Provisioning tickets open
Email, VPN and system access are requested from the onboarding checklist and tracked to closure.
- 03 · MaeOne Asset
Equipment is requested for the role
Requests, not assignments: the laptop is booked against the employee on the day it is handed over.
- 04 · MaeOne Doc
Joining documents are read and checked
Names and dates are extracted and compared with the employee record; a mismatch goes to review.
- 05 · MaeOne Pulse
Monitoring waits for consent
The disclosure is shown and consent captured. Nothing is collected before the joining date, or without consent.
Illustrative scenario with example data.
- 01 · MaeOne Doc
Classified and read
The invoice is recognised and every field is extracted with its page and position.
- 02 · MaeOne Doc
Validated before it is trusted
Line items that do not add up to the total send it to review, however confident the read.
- 03 · MaeOne Doc
Corrected by a person
The reviewer sees the field highlighted on the page, and the original value is kept beside the correction.
- 04 · MaeOne Asset
Assets proposed, not invented
Serialised hardware becomes proposed registrations with cost, warranty dates and vendor.
- 05 · MaeOne Asset
Serials scanned on arrival
Each unit is scanned when it arrives, and each asset links back to the invoice page it came from.
Illustrative scenario with example data.
- 01 · MaeOne Desk
The ticket lands on the account
Support volume, SLA breaches and satisfaction trend become part of the customer record.
- 02 · MaeOne Reach
Account health recalculates at once
On the event, not overnight — and with the contributing factors shown, not just a number.
- 03 · MaeOne Reach
The renewal is flagged at risk
The account owner sees it months before the renewal conversation, not when the customer declines.
- 04 · MaeOne People
Ownership survives a resignation
If the account owner leaves, their accounts are reassigned by territory rules. An at-risk renewal is never left unowned.
Illustrative scenario with example data.
- 01 · MaeOne Network
One root cause, its symptoms grouped
Devices behind the switch are marked unreachable, not down, and join one alert group.
- 02 · MaeOne Endpoint
Silent agents join the same group
A server behind the switch stops reporting; its alert becomes a symptom, not a second fault.
- 03 · MaeOne Desk
One incident opens
Routed to network operations, with every affected device linked and the SLA in the site’s own calendar.
- 04 · MaeOne Asset
Owner, warranty and AMC attached
The failed switch arrives on the incident with its support contract.
- 05 · MaeOne People
Affected people, not just devices
Custody and sign-in show who is affected; employees reporting the outage join a known issue instead of opening duplicates.
Illustrative scenario with example data.
- 01 · MaeOne People
Access ends with the exit
Revoked immediately, and every product holding something for this person is told.
- 02 · MaeOne Endpoint
Devices flagged for revoke-and-lock
A security officer issues it and a second person approves, both with step-up MFA.
- 03 · MaeOne Asset
Recovered, then disposed of
The laptop is returned and later disposed of with a sanitisation certificate.
- 04 · MaeOne Network
It reappears on the guest network
Months later the same device is seen again — a critical alert, because it was never wiped or it was stolen.
- 05 · MaeOne Desk
Security gets an incident
With exactly where the device is connected right now.
Illustrative scenario with example data.