← CC-Analysis

Build brief

Codex Handoff — Capture-to-Sale Build Brief & the Positioning Wedge

Audience: Codex (and any coding agent). Author: Claude. Updated: 2026-06-17.

This is the build-ordered bridge under the now-canonical specs — and an argument for why this sequence. It is not the source of truth; these are:

  • docs/product/capture-to-sale-tracking.md — the 8-stage process contract.
  • docs/CC-Analysis/trovesnap-vision-scanning-spec.md — the AI/vision layer.
  • docs/CC-Analysis/trovesnap-competitive-learning-and-trojan-horse-strategy.md — GTM.
  • docs/product/pricing-and-tokens.md, docs/technical/data-model.md — pricing + the planned identity tables.

What changed since the first draft of this handoff: the QR identity layer, the capture-to-sale tracking spine, responsible disposal, and POS-interop are now canonical planned work (see those docs), not "off-limits below the line." Build them as canonical — while still honoring the invariants in §1.


0. The argument — why build it in this order (read first)

If you take one thing from this doc: do not lead with model-heavy AI cataloging, and do not try to be a POS. Both are traps.

  1. AI cataloging is commoditizing into table stakes. Gavelist, EstateSail, Estimint, aListEngine all do photo→listing and charge per lot. Matching them on batch-listing quality is a race to a thin-margin feature, and per-lot inference is a cost trap. (Evidence: ai-cataloging-theirs-vs-ours.md.)
  2. POS/checkout is entrenched. Square is the install base; EstateSail/PROSALE own clerking. Replacing checkout in v1 means rebuilding payments, refunds, tax, and disputes to win a battle that doesn't differentiate us.
  3. So the moat is elsewhere: a durable item identity (QR), a buyer-demand graph + local marketplace liquidity, and recovery of unsold value — plus a proprietary sold-outcome corpus that compounds. (Evidence: trojan-horse memo.)
  4. Therefore the winning shape is: a low-cost wedge (free/near-free) that crews adopt because it removes real friction, deterministic/local-first AI so the base is economically free to give away, a QR identity spine that captures floor truth and feeds demand/recovery, and interop with the tools sellers already run.
  5. And the order matters. capture-to-sale-tracking.md is explicit: operational primitives (rooms, teams, bulk ops, labels, client reports, POS imports) come before heavy AI. Those are how crews keep a big house moving; they are the actual adoption blocker — not tagging quality. Lead with them.

Net: the catalog is the commodity input; identity + demand + recovery is the product. Build the spine and the operational floor first; layer staged vision and premium intelligence on top; run the positioning wedge to acquire the crews.


1. Invariants (confirm against the repo before editing)

If any instruction below conflicts with these, stop and surface it — the invariant wins.


2. Build order (six workstreams, sequenced)

Aligned to capture-to-sale-tracking.md. Each item: what · why · acceptance.

W1 — Operational foundation (before heavy AI)

The adoption floor crews need. Why: this, not tagging quality, is why pros stay.

W2 — Identity spine (QR / bindings)

The inbound loop the pipeline was missing. Why: floor truth + demand + recovery all key off one durable id.

W3 — Deterministic / local-first capture & enrich

The free base. Why: near-zero marginal cost is what lets the base be free; voice beats photo-only.

W4 — Staged vision (token-metered, only when justified)

Implement trovesnap-vision-scanning-spec.md in its phase order.

W5 — Demand + recovery

The compounding moat. Why: this is what nobody in the cataloger cluster has.

W6 — Positioning wedge (acquisition layer)

The original freemium work — still valuable, now layered on top of the spine. Full copy/specs in freemium-ingestion-pain-analysis.md §5–§9.


3. Decisions worth defending (the argument, applied)

4. Open decisions for the human (don't guess)

5. Out of scope / deferred

6. Source documents