Compare beyond price
Similar names do not always mean the same product. I worked on organizing product information so buyers can compare it against their own needs and conditions.
Case 03 · Two-person team project
Buy new,
or buy used?
An AI service for purchases that cannot be decided on price alone. I owned the data and AI-reasoning work that makes new and used products comparable. My partner owned the interface and deployment.1
Actual service screens
A decision based on the buyer’s needs.
Separate facts from inference
I treated the distinction between observed information and AI reasoning as a product requirement. Missing information should remain uncertain rather than turn into plausible confidence.
Make ownership clear
I owned data, AI reasoning, and service integration, connecting that work to the interface built by my partner. We validated the result together; I do not claim the entire UI as my design.
Validate the implementation and its judgments separately.
The integration checks covered the code, build, and model judgments. No fabricated price, inventory, or exact-product judgments were detected in the controlled sample. This does not establish accuracy across all products or real listings.2
Detailed production methods and operational design are not disclosed.
Sources and scope
- Project role records and public service screens. Responsibilities are separated between data/AI work and interface/deployment work.
- Integration verification and real-model evaluation records. Tests and the five synthetic inputs are separate validation scopes; the sample does not represent the entire market.