Discuss your migration
Menu

Know what changes
before you change models.

When your model is being retired or your requirements change, start with the evidence you already have. Pisama prepares and runs the comparison. Your team confirms the criteria, resolves focused questions and decides whether to switch.

Assisted Migration Assessment · $500 introductory price per scoped workflow.
For text-based AI workflows that retrieve information and generate answers.

What your team can inspect

Read-only launch scope

Same ticket.
Different routing decision.

A read-only assessment checks the decision your product consumes. This example shows what reviewers would inspect, without sending a message, issuing a refund or changing customer data.

Support ticket routing

Illustration only. No measured model results.
Same inputs

“I was charged twice for my annual plan.”

The frozen policy lookup says duplicate-charge tickets require billing review. Both configurations receive the same ticket, policy response and output schema.

Meets the agreed rule

Billing review

{
  "queue": "billing_review",
  "needs_review": true
}

The output marks this case for the correct review queue.

A difference to investigate

General support

{
  "queue": "general_support",
  "needs_review": false
}

Valid JSON, but the routing decision misses the required review.

In your assessment

Pisama runs the comparison against agreed criteria, documents differences and reports quality, cost and response time across the scoped model candidates. Findings that need your expertise come with the relevant context and a focused question.

Written example, not a customer result or evidence that a particular model passes. The research tabs contain separately labeled real executions.

See the $500 assessment

Better overall can still break what matters.

An average score can hide a decision your current model gets right and its replacement gets wrong. A fluent response can omit a field the next system needs.

Pisama makes those differences visible. Improvements and regressions are reported separately. Your business rules define success, even when the old model was wrong.

Bring what you have.
We’ll prepare the comparison.

Four steps for your team. Pisama handles preparation, testing and investigation.

What the work produces

An assessment built from your evidence

  • Permitted cases and existing outcome records organised
  • Current model, API route and settings identified
  • Replay feasibility and evidence gaps recorded

Share what already exists. We agree how to address the gaps.

A decision your team
can inspect.

You receive the model, API route and reasoning settings tested, the changes that matter, and the evidence behind the recommendation.

Some candidates fail. Some results remain inconclusive. Either finding can prevent a poorly understood switch.

Download sample report (PDF)

Research sample from a simulated benchmark.
Candidate screening: 29–30 September 2026.

  1. 01

    Decision and scope

    What meets the agreed limits, what does not, and what remains uncertain.

  2. 02

    Behavioral evidence

    Changed decisions, content and output compatibility, traced to individual cases.

  3. 03

    Serving conditions

    Observed latency, reliability and cost for the model and provider tested.

  4. 04

    Handoff and fallback

    A configuration record, a canary plan, and a fallback that does not rely on the retired model.

Assisted Migration Assessment

$500

introductory price per scoped workflow

Bring your own provider keys.
Inference billed directly by your providers.
No Pisama token markup.

Bring your existing evidence. Pisama prepares the assessment, investigates what changes and delivers a recommendation your team can inspect.

  • Prepare approved logged requests and capture the baseline
  • Prepare acceptance criteria for your experts to confirm
  • Test the recommended direct swap first, with up to three development configurations in total
  • Investigate regressions and run one final assessment of a locked candidate
  • Deliver a scoped recommendation, case evidence, unresolved issues and configuration handoff

Replay feasibility checked, with scope and inference estimates agreed before engagement. More complex work quoted separately.

Your expertise, where it matters.

Start with your existing logs, policies and examples. Pisama prepares the comparison and brings the evidence to questions that need your expertise. You confirm the criteria and make the rollout decision.

Pisama handles

  • Evidence preparation and proposed assessment criteria
  • Model comparisons, investigation and focused review questions
  • Evidence, recommendation and configuration handoff

Your team contributes

  • Existing evidence and agreed provider access
  • Confirmation of criteria and answers to domain questions
  • The rollout decision and deployment
Fits
One text workflow with structured decisions, a callable current model, up to three model calls and one read-only tool.
Review
Pisama prepares the relevant context and differences for review. Your experts resolve ambiguous outcomes and review an agreed audit sample. We identify gaps in the evidence and agree any additional review before work begins.

Free readiness guide

Prepare your migration

Start with one workflow and the evidence you already have. Use these five steps to locate existing materials, note gaps and agree the support a useful comparison needs.

This guide helps you prepare. It does not test models or recommend a replacement.

See the assisted assessment
  1. Find your configuration and deadline

    Locate the existing configuration or request logs that identify the provider, exact model ID, API route, reasoning level, prompt version and generation settings. Confirm any retirement date in the provider’s official notice, then note your decision deadline.

    If missing. Ask the engineering contact where the configuration is stored. Note missing settings and keep an unconfirmed retirement date marked as unresolved.

  2. Locate evidence you are allowed to use

    Find existing log exports, tests, typical requests, known failures and trusted outcomes for one workflow, including the context each model receives. Check permission to use this evidence. Agree approved access and handling before sharing sensitive records; keep them out of an initial enquiry.

    If missing. Note which records are unavailable or need approval. Any use of anonymized or synthetic evidence, and its limits, can be agreed during scoping.

  3. Bring existing policies and trusted outcomes

    Locate current policies, output requirements, tests and examples of trusted decisions. During the assisted assessment, Pisama prepares proposed comparison criteria and questions for your domain reviewer to confirm, including required behavior and quality, cost and response-time limits. Your domain rules remain the reference when the current model is wrong.

    If missing. Missing or uncertain trusted outcomes are assessed during scoping, along with the review needed to establish a useful comparison.

  4. Agree access and check replay scope

    Arrange the agreed access to existing configuration, logs and approved tool responses needed for replay. Confirm the current model is still callable and identify any documented model-call order and tool dependencies. The assisted scope covers one text workflow with structured decisions, up to three model calls and one read-only tool.

    If missing. List unavailable models or unreplayable dependencies before agreeing scope. Saved outputs can help, but may not support a fresh baseline comparison.

  5. Agree contacts, review effort and inference

    Name an engineering contact and a qualified domain reviewer who can answer questions and confirm the rules that matter. Agree with Pisama what needs review, who will review it and separate estimates for domain review and engineering involvement before work begins. Budget for provider inference separately, using your own provider keys.

    If missing. Note gaps in contact availability and any limits on time or spend. Agree the review plan, access needs and inference estimate during scoping.

Before we start.

Can we start without a paid assessment?

Yes. Use the free readiness guide to find existing logs, policies and outcome records, and note what is missing. It is available without an account. If you already have a suitable evaluation setup and can investigate the results, you may be able to carry out the comparison yourself. The assisted assessment is for teams that want Pisama to undertake that work with them.

What is included in the price?

The $500 introductory service fee covers the full assessment of one agreed workflow: evidence preparation, replay setup and incumbent capture, proposed criteria confirmed by your experts, comparison and investigation across up to three development configurations in total, one final assessment of a locked candidate, and an evidence-backed recommendation and handoff. Inference is separate. Payment is $250 (50%) at accepted scope and $250 (50%) at delivery of the agreed evidence package, whether the result is pass, fail or inconclusive.

How does bring-your-own-keys work?

You use your provider accounts and pay the providers directly for inference. Pisama charges the assessment fee without token markup. We agree on scope and estimate inference across the required runs before starting. BYOK is a billing choice; it does not mean execution is customer-hosted or that data stays inside your environment.

Can Pisama manage the inference billing?

Yes, by agreement. The same assessment fee applies, plus an inference allowance agreed before work begins and billed transparently. We agree any additional allowance before further testing.

Which workflows does the launch offer cover?

One text workflow with structured decisions, up to three model calls and one read-only tool. Fine-tuned incumbents can be assessed. Training delivery, write tools and autonomous agents are outside the initial scope.

We compare model responses to recorded requests, using the context and prior tool responses already in your logs. Live tool execution and end-to-end workflow behavior need separate validation.

Do we need to build our own evaluation system?

No. Start with the logs, policies, tests and outcome records you already have. Pisama identifies usable evidence, prepares the replay and proposes criteria for your experts to confirm. We run the model comparisons and investigate the results. Replay feasibility and any missing inputs are checked before the engagement is accepted.

Can we assess a workflow with sensitive data?

Your team supplies approved cases. We agree what data can be used and how it will be handled before testing. Customer-prepared anonymized or synthetic cases must preserve the context needed to judge outcomes, and any coverage limits are recorded. Do not include sensitive records in the initial enquiry.

Will the result always be a replacement we can use?

No. A candidate may pass, fail or remain inconclusive within the tested scope. You are paying for the evidence needed to make the decision, including a clear finding that a configuration is unsuitable.

Can we stay with our current provider?

Yes. We start with the provider’s recommended replacement and the minimum integration changes it needs. Other models or serving routes are considered when the evidence gives a reason to explore them.

What does our team need to contribute?

Share existing evidence you are permitted to use, identify your current configuration and name a domain contact. Tell us about your decision deadline. We agree provider access and data handling with you before testing.

Your experts confirm the proposed criteria, answer focused questions with the evidence alongside them and review an agreed audit sample. Pisama handles evidence preparation, model comparisons and investigation. Where existing evidence is insufficient, we identify the gaps and agree any additional expert review before proceeding.

Before work begins, we agree the review plan and estimate expert review and engineering effort separately. Your team also owns deployment and the rollout decision.

Can we reuse what we have already agreed?

Yes. Approved rules and reviewed examples provide a starting point for comparable cases. We check that they still apply when your workflow or policies change, and bring exceptions back for review. Assessment criteria are agreed before model comparisons begin and stay fixed for final confirmation.

What needs to stay true
when your model changes?

Tell us what you run today and what is changing.
We’ll start with the decision you need to make.

Discuss your migrationScoped to your workflow.
Backed by evidence you can inspect.