How ReleaseProof works

Compare two versions before releasing an assistant update.

ReleaseProof compares the current and new versions of an AI assistant. Both versions receive the same customer requests and are checked against the same release criteria.

From customer cases to a release decision.

  1. 01

    Describe the update.

    Name the assistant and record what changed.

  2. 02

    Prepare the cases.

    Add representative, redacted customer requests and the responses from both versions.

  3. 03

    Set the criteria.

    Define exact rules, semantic expectations, and decisions that require a person.

  4. 04

    Review the result.

    Inspect improvements, regressions, evidence, and cases that need human confirmation.

For teams and independent builders who update AI assistants.

Use ReleaseProof when you change an assistant’s instructions, model, knowledge, routing, or workflow and need to confirm that the update has not broken behavior people or the business already rely on.

The current version is your baseline. The new version is the update you plan to release.

ReleaseProof does not judge an answer in isolation. It compares how both versions handle the same situation and shows whether the new version improves, preserves, or degrades the expected behavior.

A customer scenario is a representative request with a clear expected behavior.

It can be a question about price, eligibility, territory, booking, support, or the next step in a sales conversation. Remove personal data before adding the scenario.

Customer request

Can an adviser call me tomorrow? I’m available after 2pm.

ACurrent version

BNew version

Expected behavior

Offer the approved booking route. Do not promise a time that has not been confirmed.

Check the behavior that matters in production.

  1. 01

    Lead qualification

    Does the assistant collect the information needed to understand and route the request?

  2. 02

    Customer-facing answers

    Does it use the correct facts, language, tone, and level of certainty?

  3. 03

    Booking and handoff

    Does it offer an approved next step without inventing a meeting, callback, or commitment?

  4. 04

    CRM-ready data

    Does it return the status, category, and next action expected by the client’s workflow?

  5. 05

    Human escalation

    Does it recognise when the conversation should be passed to a person?

Choose the input method that fits your test setup.

  • 01

    Prepared responses

    Paste or import the answers produced by both versions.

  • 02

    Version instructions

    Provide the current and new instructions and generate both sets of replies from the same customer requests.

  • 03

    Compatible test endpoints

    Connect two test endpoints that accept a JSON request containing { input }. An optional access token stays in the browser between sessions, is sent through the ReleaseProof server only when the endpoint is called, and is not saved to the database.

A report to review before release.

The report shows the score of each version, improvements, regressions, evidence by case, and a pre-release status: ready to confirm, review required, or do not release yet.

The status supports a release decision. It does not replace human confirmation of important findings.

Compare an update on your own customer scenarios.

Important limitation

ReleaseProof supports a release review. It is not legal, financial, or compliance certification.

Read data and privacy details