Define the task
Document the object, process, environment, throughput, people nearby, operating hours and failure tolerance. A clear task statement prevents impressive but unsuitable demonstrations from setting the specification.
Compare the right parameters
Use category-specific fields. A humanoid needs locomotion, manipulation, runtime and developer access; an industrial arm needs payload, reach, repeatability, mounting, controller and safety data. Keep model names and source descriptions in English where translation changes meaning.
Qualify the seller and support path
Confirm whether the seller is the manufacturer, an authorised distributor, a dealer or an individual. Verify warranty authority, local service, spare parts, escalation contacts, training and software support.
Calculate total deployment cost
Add freight, duties, tax, site work, tooling, integration, guarding, charging, commissioning, training, licences, connectivity, maintenance and downtime—not only the robot price.
Agree evidence and acceptance
Request test context for performance claims. Define a site acceptance test, safety responsibilities, data access, cybersecurity requirements, source-code or SDK rights, handover documents and the remedy if acceptance fails.