Code Development
New functionality written into your environment by the product engineering team when a business requirement falls outside what configuration can reach.
Continuous support
Support from the engineers who wrote the code
Get support directly from the expert team. A question about a posting rule, a slow report or an interface that needs extending goes to the people who build and maintain the platform — not to an outsourced desk reading the same manual you already have.
Code development, performance tuning, custom extensions, interfaces and configuration — handled by the engineers who maintain the platform itself.
Additional support and service coverage
Six things support can actually do for you.
Most vendors define support as answering questions. Ours includes writing code, because the engineers on the other end of the request own the product.
Development Support
Working alongside your own developers or partners — data model guidance, review of what they are building and help getting it running against the platform.
Optimization and Performance Tuning
Investigating the screens, postings and reports that have grown slow as your transaction volume climbed, and tuning them back into shape.
Custom Extensions
Purpose-built additions to standard modules — extra fields, validations, documents and workflows that match how your business trades.
Custom Interface
Connections between the platform and the systems either side of it: banks, marketplaces, payroll bureaux, tax portals, devices and machines on your floor.
Custom Configuration
Reworking roles, approval chains, numbering, document layouts and posting rules as the organisation restructures, opens a site or changes how it reports.
The support model
One queue. No translation layer.
A request does not travel through a reseller, then a distributor, then finally reach somebody who can read the code. It lands with the same organisation that shipped the release, and it is worked by people who already know your configuration because they built it.
- Your implementation history and design document stay attached to the account, so nothing has to be explained twice
- Teams in Princeton Junction, Oxford and Chennai, so cover follows the working day rather than one time zone
- Environments hosted in a company-owned exclusive cloud facility, so infrastructure and application issues are handled by one organisation
- A direct path from a support request into engineering when the answer turns out to be a code change
3
Support Offices — USA, UK, India
6
Additional Service Coverage Lines
2007
Supporting This Platform Since
1
Escalation Path Into Engineering
Questions
What support covers.
Our own support engineers, working in the same organisation as the product team that writes the platform. When a request turns out to need a code change, an extension or an interface, it moves internally to the engineers who maintain that area rather than being closed as out of scope.
Yes — code development, custom extensions, custom interfaces and custom configuration are part of the service coverage, alongside development support for your own team. Scope and commercial terms for a build are agreed with you before work starts.
That is exactly what optimization and performance tuning exists for. We look at the queries, indexes, report design and configuration behind the slow area, and because your environment runs in our own cloud facility we can investigate the infrastructure side at the same time.
Yes. We start with a review of the existing configuration, extensions and interfaces so the support team knows what it is holding, and we document the gaps we find. Talk to us about the environment you are running and what has been changed in it.
Get help
Send it to the people who built it.
A tuning problem, an interface to a new bank, an extension your finance team has been asking for — describe it and the right engineer picks it up.