All workCase study · 2026

Qivoa

Know before you buy. A second-hand listing becomes a living dossier of facts, risks, market evidence and questions worth asking.

RoleEverything: product, design, code, ops
SurfacesWeb, Expo mobile client, Chrome extension
StackReact 19, Expo, Hono, Prisma, Postgres
Qivoa marketing page with an illustrative console listing, separate seller claims, market observations and a next action
Marketing page · the console listing and price example are illustrative.
The brief

Buying second-hand means deciding from incomplete information. I wanted a tool that shows what is known, what is still a claim, and what to check before paying.

Input
A listing and the evidence that follows
Output
A dossier that evolves with the deal
Principle
Every conclusion has an evidence trail

What I built.

01

A living Deal dossier

A listing starts the dossier. Seller replies, photos, receipts and inspection results add evidence, then update the facts, risks and recommendation.

02

Several ways in

Paste a link or text, add photos, or share a listing from the phone. A Chrome extension hands supported listing URLs to the web app.

03

Facts with provenance

Seller claims, detected details, user corrections and inspection evidence keep their sources. Conflicting information stays recorded instead of disappearing.

04

Product-specific checks

Reusable product knowledge defines what matters for a console, phone or laptop. Each applicable risk stays present, cleared or unknown as evidence changes.

05

A market-backed range

Comparable active listings inform the range. Exact and adjusted near matches carry separate weights, original prices and explanations of their adjustments.

06

The next useful action

Unresolved facts become seller questions and inspection checks. Negotiation drafts are editable and copied by the buyer; the app sends nothing to the seller.

Inside the product

Evidence in. A reasoned next move out.

The interface is a dossier, with facts, risks, valuation and inspection. The buyer can see why the recommendation changed after a seller reply or a check in person.

Web and mobile consume the same API contracts. The API persists evidence and revisions; deterministic domain code owns the decision rules.

Explore Qivoa ↗
  1. 01

    Capture the source

    Keep the listing, reply or image attached as evidence.

  2. 02

    Extract candidates

    Validate structured facts against the product's attribute definitions.

  3. 03

    Resolve the evidence

    Apply corrections and inspection results without losing prior claims.

  4. 04

    Recompute the dossier

    Derive risks, confidence, valuation and the next action in domain code.

Decisions

Trade-offs I'd make again.

  1. 01

    Give AI a narrow job.

    AI extracts and classifies information behind typed, validated contracts. It doesn't calculate the price range or clear risks. Interactive updates let the buyer review proposed facts before applying them.

  2. 02

    Put product knowledge in one place.

    The ontology defines attributes, risks and inspection bindings. Adding a product means extending those definitions, rather than scattering special cases through the API and screens.

  3. 03

    Show where the evidence stops.

    Active asking prices are not completed sales. When comparable evidence is missing, Qivoa omits the price component rather than pretending to know whether the deal is cheap. An unchecked risk remains unknown.

  4. 04

    Treat a guest's dossier as private.

    Guests receive real authenticated sessions. The Hono API checks ownership on Deal requests, so the same boundary protects saved evidence before and after account creation.

Next case studyClubSiteKitFrom my club's website to a system other clubs can use.
03 — Contact

Have a product in mind? Let’s ship it.

A role, a product to build from scratch or a club that needs a website. I reply within a day or two.

bricebraquin@live.fr