Artifact · v0 (format-only stub)

Productization Candidate Inventory

Every piece of intellectual property inside SmartOne that could become a named product. Scored against build effort, market demand, and differentiation. The raw material for the platform spec.

3.1 · Platform Architect · artifact id: productization-inventory-v0.html · 2026-05-28 · v0 format stub

This artifact is a format placeholder. The Phase 3 engagement builds this inventory after Phase 1 stability is achieved and the alignment question is resolved. No outsider can catalog SmartOne's internal tooling and methodology without direct access. The structure below shows what the live inventory will look like.

The platform hypothesis from the call

"Heck, take the 10-20 open source tools, string them together with a fun little UI, I could hack something together in a week, right? And call it your platform. You have one for data annotation that 10x this is the speed or 100x the speed. And that's your competitive differentiator." Amyn · ~32:55

The hypothesis is correct. The 10-20 open-source tools referenced on the call are already in use. The platform does not need to be invented; it needs to be packaged. This inventory is the first step of that packaging: naming what exists, scoring it, and deciding what to build toward.

Inventory format (when built)

Candidate inventory table

Asset name	Description	Current form	Build effort to productize	Market demand signal	Differentiation vs. Labelbox / Snorkel
[e.g., Temporal annotation schema]	[Multi-frame labeling ontology for physical world sequences]	[Internal doc / tool / workflow]	[Small / Medium / Large]	[Buyers asking for this type of deliverable?]	[What Labelbox does not do here]
[e.g., QA dashboard]	[Real-time accuracy tracking and reprocessing trigger]	[Internal tool]	[Placeholder]	[Placeholder]	[Placeholder]
[e.g., Open-source tool N]	[Placeholder]	[Placeholder]	[Placeholder]	[Placeholder]	[Placeholder]

Scoring criteria

Criterion	What it measures
Build effort	How much engineering work to turn the internal asset into something a buyer can use without SmartOne's help
Market demand signal	Are buyers explicitly asking for this, or does SmartOne believe they will? Actual demand beats hypothesis.
Differentiation	Does Labelbox, Snorkel, or any comparable do this already? If yes, what makes SmartOne's version different?
Defense of the moat	Does productizing this strengthen SmartOne's institutional workforce differentiator, or does it commoditize it?

What you need to send us to build this

Inputs needed. To build the live inventory: (1) a list of the 10-20 open-source tools referenced on the call (names and what each one does), (2) any internal methodologies or documentation that is not off-the-shelf (the things SmartOne built itself), (3) a 30-minute call with whoever owns the internal tooling today, and (4) whether the CTO role that is currently vacant was the person maintaining this tooling or not.