ServiceNow work, in preparation
ERP and EDI is open now. ServiceNow comes next, from the side I know: the process, the data the platform depends on, and the acceptance of what gets built.
This page is a draft in public. It shows where the practice is heading, not what is on offer today: no engagement, price or vendor credential is claimed here.
Three jobs around a ServiceNow build
Requirements and process
A workflow has to be written down before it is configured: who raises what, who approves, what counts as done.
- Request and incident flows mapped to how the business actually works, not to the default form.
- Catalogue items written plainly: the fields, the approvals and the fulfilment steps.
- Change and approval rules the change board can read and challenge.
The data the platform depends on
A service platform is only as good as the records it relies on: assets, configuration items, locations, suppliers.
- Asset and configuration data checked for duplicates, gaps and owners before go-live.
- Rules for who may change a record, so the data stays right after the project ends.
- Load templates and reconciliation checks for every import.
Acceptance and handover
The platform is accepted by the people who will use it, against a script written from the process.
- Test scripts written against the agreed process, not against the configuration.
- User acceptance run with the people who will live with it, defects logged and closed.
- A short runbook the in-house administrator can keep.
What is planned first
A readiness read
A short written read of the current service desk, the data behind it and the gaps, before any platform decision is made.
An acceptance pack
The test script and acceptance plan for a build someone else is configuring.
A data clean-up before load
The asset and configuration records checked, de-duplicated and owned.
What this page does not claim
- No ServiceNow engagements are on offer yet and no price is printed.
- No platform credential or partner status is claimed. None will be until it is earned and can be checked.
- Platform configuration and development are not on offer here yet. When they are, this page will say so, and on what terms.
If a project of yours has a gap on the process, data or acceptance side, a short note now shapes what gets built. Twenty minutes on a call, and a straight answer on whether it is a fit.
Bring one problem.
Twenty minutes on a call. Within two business days, a one-page written scope and quote, or a straight "not me" and a pointer to who can.