01 · DEFINE THE DECISION
What must the sample help the buyer decide?
Before opening the box, state the target customer and the commercial decision. A mobile-accessory distributor, a premium reception project and a corporate gift program do not evaluate the same workflow.
Use one primary decision statement, such as: “Can this format support a mobile multilingual workflow for our corporate channel?” The sample record should answer that question and list anything it does not prove.
If the intended user, environment and workflow are undefined, a successful demo is not yet channel evidence.
02 · SIX CHECKPOINTS
Move from identity to written scope.
Define the channel decision
Write down the target customer, intended selling channel and priority use case. A sample cannot be judged meaningfully against a generic idea of ‘translation’.
Confirm the exact sample identity
Record the model, physical configuration, included accessories and the software package used during the evaluation.
Test representative workflows
Use phrases and environments that reflect the intended business scenario. Record the input, output, conditions and any failed attempt—not only the best result.
Separate device and software scope
Document phone, app, account, connectivity and downloaded-resource requirements so the complete workflow is understood.
Review destination requirements
Request documentation for the exact model and destination market. Do not assume that one model’s documents apply to another configuration.
Close with written terms
Confirm quantity, branding, packaging, warranty, lead time, delivery and service scope in the final written proposal.
03 · MATCH THE FORMAT
Do not compare unlike workflows as if only the hardware changed.
Start with the format that matches the intended job. When two options use different apps, phones, network states or interaction patterns, record them as complete workflow alternatives—not a controlled hardware benchmark.
Evaluate shared viewing across a table or counter.
Check physical handling, screen visibility and the proposed face-to-face workflow with the exact market configuration.
View T90 evidence →
Evaluate the complete device-and-app workflow.
Record phone, app, connection, installed resources and service scope alongside the physical sample.
View T5 evidence →04 · EVIDENCE SCORECARD
Record the test so another buyer can review it.
Use this structure for each candidate. A blank or unresolved cell is an open item, not a reason to infer a favourable result.
| Decision area | What to inspect | Evidence to retain |
|---|---|---|
| Physical sample | Model identity, controls, displays, accessories and finish | Photos, checklist notes and exceptions |
| Priority workflow | Representative phrases in the intended environment | Inputs, outputs, conditions and failed attempts |
| Software setup | Phone, app, account, connection and resource requirements | Setup steps and proposal-specific service scope |
| Operational fit | Charging, storage, handover, cleaning and staff responsibility | Pilot owner and operating procedure |
| Destination review | Model-specific documents and buyer import requirements | Open items confirmed by responsible parties |
| Commercial proposal | Quantity, customization, warranty, delivery and service terms | One approved written scope |