Solutions

Customized Solutions

Built on the XOP platform

Not every operation fits a template. Build on what's already there.

Start with one. It is already connected to the rest.

What it does

When an operation needs something the eleven solutions above don't cover, Touchwork builds it on the same XOP platform and data model, not as a separate system with its own login and its own export.

Proof
  • Built on the same platform and data model as every other XOP solution
  • Scoped per engagement, by the team that builds the core platform
  • Sits alongside XOP Listen, XOP Audit and the rest, not apart from them
  • Same record-keeping and reporting as the rest of the platform
Questions

What people ask before they implement XOP.

What counts as a custom project?

A workflow, an integration or a form that the eleven standard XOP solutions don't already cover, something specific to how one operation runs, rather than a gap in the platform generally.

Does a custom project still sit on the XOP platform?

Yes. A custom project is built on the same data model and record-keeping as every other XOP solution, so it shows up in the same dashboards and cases rather than living in a separate tool with its own export.

How is a custom project scoped?

In a discovery call with your operations team and ours, working from what the standard solutions don't fit, not from a blank page. Most custom work extends an existing solution rather than starting from nothing.

Who maintains it after it ships?

Touchwork does, the same as the rest of the platform. A custom project is not a one-off build handed over and forgotten. It is maintained and upgraded alongside everything else on XOP.

Know sooner. Act faster. Improve continuously.

Discover what XOP can do for your operations.