Three ways to buy the same person. Each one is priced on the page, and each one ends with a platform that is still tidy in year three, because the person who designed it is the person who picks up the phone afterwards.
Built on the base rather than around it. Foundation data first, then the processes, then the catalogue people will actually use. The same person designs it, builds it and picks up the phone afterwards.
What it looks like: a design you can read before anything is built, work delivered in update sets you can see, testing on your sub-production instance with your people, and a handover that is written down rather than remembered. An existing instance starts with the onboarding assessment, so the design is made against what is actually there.
Architecture reviews, upgrade planning, integration design and the awkward question of what to undo. Somebody who has watched each of those decisions play out ten times elsewhere.
What it looks like: the days come with the package and are spent on your backlog, refined once a month with you and released once a month after you have tested. A day on a term costs less than the rate card; an extra day is charged at it, agreed before it is used. The annual ServiceNow upgrade is planned and led, and on a Bridge it is scheduled against the days rather than charged on top.
Alchemist Connect reads your instance every day and I answer the phone. One package: a fixed day a week for six months, with everything the console does included. Twelve months at two days a week if six is not enough.
What it looks like: Connect watching round the clock and raising incidents on your own instance, a monthly report somebody wrote, a quarterly review, and me on the end of the phone within the response times on the packages page.
Support on an existing instance starts with the onboarding assessment, £2,500 once, free if I built the instance. Details on the packages page.
An architecture question, a platform in trouble, or a support package: support@alchemist-it.uk.