M AND R SOLUTION
Choose how you’d like to reach our team.
DEV · Education & services
Define the evidence needed to accept an implementation.
Discuss QA, engineering and testing requirements, including test scope, representative scenarios, defect review, and acceptance responsibilities.
Contact us for pricingConfirm modules, services, and commercial terms in a written proposal.
Discuss the modules, users and deployment your business needs.
Built around your work
DEV concerns QA, engineering, and testing around an implementation. Define what must be demonstrated, who reviews the result, and which issues must be resolved before a business workflow is accepted. Agree the deliverables, access requirements, test evidence, and acceptance responsibilities with the team before the engagement begins.
A demonstration can appear complete while important exception cases, acceptance criteria, and ownership of unresolved issues remain undefined.
Identify the modules, operating scenarios, and expected outcomes that stakeholders need to review during an implementation.
Prepare synthetic examples covering normal work, corrections, and exception paths without exposing customer or production records.
Agree how findings are described, prioritised, retested, and presented to the person responsible for acceptance.
Example workflow
State the business action, sample input, and expected result before testing.
Compare the observed result with the agreed outcome and describe any difference.
Retest the relevant change and obtain the agreed stakeholder's acceptance.
Operational visibility
Bring the fields, reporting periods, and examples your team uses. Agree the available formats and any additional report work in the implementation scope.
Before you decide
The catalog identifies its engineering and testing purpose. Availability, deliverables, access, and commercial treatment should be discussed with the team for the specific engagement.
Bring the business workflow, expected outcomes, proposed modules, and examples of corrections or exceptions. Use synthetic data to establish test cases, required evidence, and the person responsible for accepting the result.
Bring a representative business example for DEV, including a correction or exception. Review the steps on this page with the team and agree which are supported by the proposed release, configuration, and services.
Request a proposal listing the selected modules, users, locations, deployment, migration, training, and support. Ask for taxes and ongoing charges to be itemised, with acceptance criteria and responsibilities agreed before implementation.
Configuration & support
Choose a configuration with clear responsibilities and commercial terms.
Confirm modules, users, branches, integrations and deployment requirements in your proposal. Displayed prices apply to the listed configuration.
Ask us to itemise taxes, hosting, migration, training and ongoing support. Support, updates and annual maintenance, where applicable, depend on your purchased plan and signed agreement.
Your next step
Discuss QA, Engineering & Testing, review your requirements, and agree the configuration, services, and next steps with our team.
