Can the robot complete the task often enough?
The readiness scope starts with the pass bar the buyer actually needs.

Real-site robot evaluation dataset and workflow
Capture a real site. Turn it into Site, Task, Scenario, and Eval Cards. Test the task before teams spend months on-site.
The readiness scope starts with the pass bar the buyer actually needs.
Blueprint frames the task against target timing, bottlenecks, and site drift.
The report names likely assist points instead of hiding them behind a score.
Safety stays scoped to the request and does not become a blanket validation claim.
What Blueprint sells
Blueprint turns capture and pipeline evidence into an inspectable dataset and workflow: what the site is, what task matters, what scenarios can break, and what proof is still missing.
Site type, geometry, visual and dynamic conditions, safety constraints, robot metadata, provenance, rights, and review status.
Task statement, start state, success and failure definitions, required metrics, evidence source, and confidence.
Normal scenario, variation, edge case, known risk, observed-vs-inferred labels, and missing annotations.
Robot or policy tested, engine used, predicted results, failure modes, uncertainty, validation status, and blocked upgrades.
How it works
Blueprint keeps the workflow compact: real site, robot task, scenario variation, eval status, missing annotations, and the next proof step.

Start from a lawful capture, existing site package, or structured request for the facility in question.
Build the Site Card, Task Cards, Scenario Cards, Eval Cards, annotation backlog, and proof boundaries.
Name the robot profile, task suite, success rate, cycle time, intervention rate, and safety threshold.
Call out failure modes, site modifications, data needs, recapture needs, and proof that remains blocked.
Proceed to a short pilot protocol, change the site, gather more evidence, compare vendors, or hold.
Planning ranges
Pricing is intentionally simple. Public ranges help a buyer pick a path; live availability, rights, payment, and fulfillment are confirmed per request.
$2,100 - $3,400
One site, one task suite, one robot profile, one threshold set, and a pre-pilot recommendation.
Request scope$16 - $29 / session-hour
Managed browser review, reruns, observations, export framing, and a direct buyer room when available.
Request scope$50,000+ scoped
Private capture planning, vendor-neutral benchmark design, custom data package, and operator boundaries.
Request scopeProof boundary
Blueprint can look ready and polished without pretending a robot has passed deployment, safety, payment, provider, rights, or hosted-session checks that still need owner-system proof.
Sample
Stronger proof
Samples show the Site/Task/Scenario/Eval Card workflow. Request packets prove one site with provenance, rights, thresholds, and gaps attached.
Sample
Stronger proof
Generated outputs can support review, but simulator traces, action logs, robot trials, safety review, rights proof, and runtime artifacts own stronger claims.
Sample
Stronger proof
Eval cards stay advisory until the missing proof exists for that exact site, robot, task, and threshold set.
First request
Bring the facility, task, robot profile, target thresholds, timeline, and proof you already have. Blueprint routes the next step to an eval-card packet, hosted evaluation, capture ask, or proof blocker.
Request eval datasetRequests do not grant package access, rights clearance, payment, fulfillment, or hosted-session availability by themselves.
Readiness remains advisory until simulator traces, action logs, robot trials, safety review, rights proof, and runtime proof support a stronger claim.
Generated imagery on the public site is illustrative, not customer or robot-trial proof.
Public Launch Ready copy is allowed. Operational Launch Ready claims still require proof from the system that owns them.