We scope the task
We define the product scenario, the audience for the result, the document types, and the business goal.
usually 1-2 business daysB2B pilot & pricing
Wizey B2B pilot pricing
Wizey B2B has no off-the-shelf tiers: terms depend on the scenario, volume, white-label or API format, data requirements, support, and how the result fits into the partner's processes.
Terms depend on the scenario, volume, and security perimeter, so we work with each partner individually. After a short scoping of the task, we lock in a clear plan with stages and evaluation criteria.
Pricing
What the price depends on
The cost is built from the practical scenario: who uses the result, what text-based medical data comes in, what response format is needed, and how deeply Wizey is embedded into the product or operational process.
scenario volume white-label API data requirements support
Pilot
How the pilot launches
A pilot exists to quickly validate value in a real B2B scenario: result quality, format convenience, the load on the team, and clarity for the doctor, patient, or operator.
We agree on the format
We lock in the response structure, tone, branding, user roles, and data requirements.
3-5 daysWe run a test launch
We test the chosen flow on a limited set of examples and collect feedback.
1-2 weeksWe decide on scale
We discuss refinements, support, the commercial model, and terms for further onboarding.
after the pilotTimelines
Approximate ranges
Exact dates depend on the integration format, security requirements, and the makeup of the team on the partner's side. Below are soft benchmarks we see in practice.
Pilot 14-21 days From the agreed format to collected feedback and a decision on the next step.
From first contact to launch 2-4 weeks Including task scoping, format agreement, and preparation of the test data flow.
Success criteria 3-5 days Agreed in the first days after the start, so the scaling decision is transparent.
Partner outcome
What's included in the pilot
If the "How the pilot launches" section describes the steps we take together, here are the artifacts, access, and support that stay with the partner by the end of the pilot.
Agreed output format
A description of the report blocks, terminology, explanation tone, disclaimers, and level of detail, captured in a document.
Test access
A demo perimeter to validate the scenario: white-label delivery, integration into the interface, or connection via the programmatic perimeter, depending on the chosen format.
Data handling for your perimeter
An agreed flow of text-based medical data that accounts for roles, de-identification, and the partner's data requirements.
Sample analyses
Finished results on a limited set of documents: material for the medical, product, and operational teams to assess quality.
Support during the pilot
A channel for questions, a review of feedback, and format refinements based on the test launch.
Report and next-step plan
A summary of the pilot results: what was confirmed, what needs refinement, and a proposal for volume, support, and commercial terms going forward.
Straight talk
Who it fits, and who it doesn't
To avoid wasting time on both sides, we show upfront which pilot scenarios are ours and which are better solved with another tool or provider.
A fit if
- There's a recurring scenario for analyzing text-based medical data: lab results, conclusions, discharge summaries, prescriptions.
- You're ready to agree on the result format for the user — patient, doctor, operator, or product.
- There's a product, medical, or operational team that will evaluate the pilot.
- You see B2B integration as a long-term process, not a one-off task.
- You're ready to discuss data, de-identification, and security-perimeter requirements.
Probably not a fit if
- One clinic and a one-off task with no long-term integration into a product or process.
- The scenario needs analysis of MRI, CT, or ultrasound scans — we work only with text-based conclusions and descriptions.
- There's no patient consent to process and de-identify data for the pilot.
- You need an urgent launch in 1-2 days — without a scenario session and format agreement.
- You expect guarantees of a diagnosis, treatment, or a replacement for a doctor's visit.
FAQ
Common questions about the pilot
Short answers on price, timelines, scope, and how terms are discussed after the pilot. For the full summary and partner-perimeter nuances, see the B2B FAQ.
How much does a Wizey B2B pilot cost?
The exact pilot price is locked in after a short scoping of the task. The cost depends on the scenario, volume, integration format, data requirements, and support. We don't publish a price grid on the public page: a B2B project can be a pilot for a laboratory, a white-label module, or an integration into a product, and these options require a different scope of work.
What does the pilot price depend on?
The price is built from the use scenario, volume, the choice between white-label and API, data requirements, and the support format. It also factors in how deeply Wizey is embedded into the partner's product or operational process.
Is there a free B2B pilot?
There are no free B2B pilots with commercial guarantees. The first step is a short scoping of the task and agreement on the pilot format. At this stage, we jointly assess how much work is needed to test the hypothesis.
What are the pilot launch timelines?
Timelines depend on the pilot scope, the integration format, security requirements, and the makeup of the team on the partner's side. After scoping the task and agreeing on the format, we lock in a clear plan with stages and evaluation criteria.
What is usually included in the pilot scope?
A scenario session, output configuration, work with data, the choice between white-label and API, feedback collection, and a scaling plan. The full scope of work is discussed for the specific task and locked in before the start.
How are commercial terms discussed after the pilot?
After the pilot, we discuss volumes, support, documents, timelines, and the commercial model for the next stage. The success criteria and the scaling decision are locked in upfront, so the transition is transparent.
Want to scope a pilot for your scenario?
Describe the task on the B2B page: the product format, the expected data flow, the user roles, and the result you want. We'll come back with questions and propose a clear next step.