Bespoke Software Engineering

When this fits

You need a system built around a problem no product fits, and you want to own the result.

What the work covers

• Requirements and acceptance criteria written first.
• Interface, services, data and infrastructure built as one system.
• Tests, observability signals and documentation for each release.

What you receive

• The system, its source and its tests.
• Runbooks, deployment steps and recovery steps.
• The record of what was tested and what was not.

How completion is decided

Every acceptance criterion in the written proposal is met, or a named exception is accepted in writing. Transfer is complete when the customer has built, deployed, restored and changed the system without RJV.

What you provide

• A named person with authority to decide scope and accept the work.
• Access to the people and systems the software touches.

What RJV does not promise

• A fixed price or duration before the scope is known.
• Regulatory approval or a certificate; the customer remains the regulated party.
• A result outside RJV's control, such as the behaviour of a third-party service.

How to start

Describe the problem on the Work with Us page. Every engagement follows the stages on the engineering page, and the commercial terms explain what determines scope and how the work is charged. Ownership at handover is described in deployment and ownership.