One platform, eighteen services - Cogent OS at the core.
Every service line is a module on the same core, sharing the same ticket model, the same asset and CMDB records, the same workflow engine and the same audit trail. Click any line to see the service it delivers.
What it actually looks like
Flat, matte and deliberately unglamorous. The platform is built for people working a queue at three in the morning, not for a product screenshot.
Every open work order across nineteen entities, with SLA clocks, assigned worker and parts position.
The record behind every visit: scope, parts, worksheet, photographic evidence and signature.
ITIL incident and request queues with live SLA clock states, per-country calendars and language routing.
Stock at bin and serial level across nineteen owned hubs, with customer-owned stock held separately.
Capability catalogue, auto-match against tier and clearance, screening status and utilisation.
Multi-entity, multi-currency billing reconciled against delivered work, with one consolidated client invoice.
Why owning the platform matters
Most global providers assemble a service desk tool, a field app, a warehouse system and a payroll platform, then spend their margin reconciling them. Every seam between those tools is a place where evidence goes missing and reporting becomes a monthly reconstruction.
Because we built Cogent OS, the dispatch that sends a worker to Frankfurt draws the part from the same stock record the warehouse team manages, against the same asset record the service desk sees, billed from the same work order finance invoices. There is one audit trail, one data-handling policy and one version of the truth.
It also means we can change it. When a client needs a worksheet template, an approval step or a report that does not exist yet, that is a development ticket on our own roadmap rather than a feature request to a vendor who will consider it next year.
One audit trail
Every action, approval and evidence item timestamped against the same record, immutably.
One data policy
A single hosting, retention and access position rather than four vendor policies to reconcile.
Modules that talk
Dispatch, stock, workforce and billing read and write the same objects, without integrations to babysit.
Single source of truth
Your report and our report are the same query, so the monthly review is a discussion rather than a dispute.
ITIL-based, not ITIL-flavoured
The processes below are enforced by the platform rather than described in a policy document, which is why evidence is a by-product of the work instead of a reporting exercise.
Incident management
Priority matrix, SLA clocks against the local working calendar, escalation paths to a named Cogent manager, and major-incident handling with comms cadence.
Request fulfilment
A service catalogue with approval routing, standard tasks and lead times, so a new starter build or a site move follows a defined path rather than an email chain.
Change & CAB
Change records with risk assessment, CAB approval, maintenance windows, rollback plans and post-implementation review captured against the change.
Problem management
Repeat incidents raised as problem records with root-cause analysis and CAPA actions tracked to closure, reviewed at the quarterly business review.
CMDB & assets
A live configuration and asset register updated as work completes, reconciled against procurement, warehouse stock and certified disposal.
Evidence-first closure
A work order cannot close without its worksheet, photographs, serial capture and signature - so the audit file assembles itself.
The platform, from outside
Cogent OS powers three external portals. Access is by invitation and role-based - your team sees your estate, a worker sees their jobs, a vendor sees their own commercial record.
Customer Portal
Everything your team needs to see what we are doing and what it costs - without asking anyone.
Field Worker Portal
A progressive web app for the person on site, built for one hand and a poor signal.
Vendor Portal
For suppliers and specialist partners working alongside us, with the same discipline we hold ourselves to.
Where your data sits, and who can reach it
The platform is a processor of your operational data, and we treat that position seriously enough to write it down rather than assert it.
Questions buyers ask
Do we get access, or only reports?
Access. The Customer Portal is included with the service, not sold as an upgrade, and it shows live ticket status with SLA clocks, your asset and CMDB records, invoices and quotes, project and wave progress, and your 3PL stock. If a number appears in your monthly report, you can see the records behind it.
Can Cogent OS integrate with our ITSM tool?
Yes. Where you want to keep ServiceNow, Jira or a similar system as your system of record, we integrate at ticket level so records flow both ways and SLA measurement stays consistent. We are candid about the trade-off: integration adds a seam, and the evidence model is tightest when the work order lives with us.
Is it really your own platform?
Yes - built and maintained by our own development team, formerly named Cogent Engine. That is why bespoke worksheet templates, approval steps and reports are a matter of our roadmap rather than a vendor feature request, and why we can offer the same platform behind a channel partner brand.
What happens to our data if we leave?
It is exported and handed over. Asset and CMDB records, ticket history, evidence files and disposal certificates are exportable in standard formats, and the exit process is a contractual deliverable rather than a negotiation at the end. Documentation is written on the assumption that someone else may inherit it.
Does the field app need connectivity on site?
It works offline where it has to. The Field Worker Portal is a progressive web app that caches the job, worksheet templates and captured evidence locally, then syncs when signal returns - which matters in basements, plant rooms and data centre halls where coverage is poor.
See Cogent OS with your data.
Book a walkthrough and we will run your estate, your countries and your SLA model through the platform rather than showing you a demo tenant.