Relational truth first
Products, typed facts, relationships, claims and rules remain queryable and constrained. Semantic retrieval supports the model; it does not replace it.
TECHNICAL COMMERCE / OPERATING LAYER
Product truth,
turned into work done.
AI-native operating software for Technical Commerce. Helmtiq turns fragmented product sources into governed intelligence, then uses specialized workflows, evidence and human control to complete valuable merchant work.
Helmtiq is the working venture name while the parent-brand decision remains open.
SOURCE QUEUE / 04
MANUFACTURER PDFrev. 04 / 38 pages
SUPPLIER XLSX426 rows / 12 conflicts
PRODUCT PAGEchanged 18 min ago
STAFF RULEapproval required
RESOLVED CLAIM / HX-1842Needs review
Connection size
¾ in. NPT0.82 confidence
CONFLICT DETECTED
Supplier sheet states 1 in. NPT. Manufacturer manual states ¾ in. NPT.
Manufacturer manualpage 14 · authority 01¾ in.
Supplier sheetrow 218 · authority 021 in.
Publication is blocked until an operator resolves the conflict.Review required
01THE BROKEN LAYER
THE WORK EXISTS BETWEEN SYSTEMS
Your commerce stack can store product data. It cannot settle product truth.
The answer is usually split across manufacturer pages, manuals, spreadsheets, feeds, metafields, compatibility tables and the people who remember the exceptions. That fragmentation becomes slow catalog work, uncertain recommendations and repeat support questions.
01PDF / MANUALS
Authority varies by version
02SUPPLIER FEEDS
Terms, units and fields disagree
03PIM / METAFIELDS
Structured, but often incomplete
04STAFF KNOWLEDGE
Useful context, hard to govern
05COMPATIBILITY TABLES
Relationships hide in documents
02THE GOVERNED FOUNDATION
ONE TRUTH LAYER / MULTIPLE OUTCOMES
Product Intelligence is the operating substrate.
Not a folder of embeddings and not another flat catalog. Helmtiq keeps source claims separate from resolved truth, models product relationships explicitly and carries provenance into every workflow.
01Fragmented sourcesPDF · XLSX · feeds · pages · rules→
02Claims + evidenceAuthority · version · locator · confidence→
03Product IntelligenceFacts · relationships · rules · overlays→
04Specialized workflowsReason · transform · compare · escalate→
05Completed outcomesUpdate · decision · queue · answer
Evidence travels with the answer
Every consequential claim can point back to its source, version and location—so an operator can inspect why the system believes it.
Uncertainty becomes a workflow
Conflicts, weak evidence and missing identifiers produce an explicit review state instead of a confident-looking guess.
03REFERENCE APPLICATIONS
EXAMPLES, NOT A FIXED FEATURE MENU
Start with the work that repeats.
These are the clearest current applications of the same governed foundation. Discovery may surface a different bounded workflow that uses the same primitives.
01
Compatibility & Replacement
BEFORE
→Staff cross-check model numbers, manuals and inherited knowledge.
COMPLETED OUTCOME
A fit, non-fit or replacement decision with the evidence attached.
02
Supplier-to-Commerce
BEFORE
→Supplier files and pages arrive in different shapes, terms and versions.
COMPLETED OUTCOME
Normalized product truth, commerce-ready outputs and an exception queue.
03
Technical Buying
BEFORE
→Buyers and staff translate requirements into specs across scattered sources.
COMPLETED OUTCOME
A structured, evidence-backed decision—or a clear request for missing facts.
04WORKING PROOF
WATER FILTRATION / REFERENCE INTERFACE
A visible test bench for Technical Buying and Compatibility.
The current reference route turns a buyer request into structured requirements, then demonstrates the review behavior used when identifiers or authoritative evidence are missing. It is an honest interface proof—not a production catalog or claimed customer result.
- Natural language → structured requirements
- Fit / Not fit / Needs review states
- Evidence and missing-information handling
TECHNICAL BUYING
“Will this replacement fit my current system?”
STRUCTURED REQUIREMENTS03 / 05
Current modelNot identified
Candidate modelNot identified
Evidence thresholdAuthoritative source
Needs review
No fit decision without both model identifiers.
Ask for the current housing label and candidate part number before checking compatibility.
05HUMAN CONTROL
AUTOMATION WITH A STOP CONDITION
The system should know when not to answer.
Technical outputs can affect purchases, installation and published product truth. Helmtiq keeps the evidence, exception and approval state in the product—not in an invisible prompt.
Fit
Rules and authoritative evidence support the decision.
PASSNot fit
A known constraint rules the option out.
BLOCKNeeds review
Sources conflict, evidence is weak or required facts are missing.
ESCALATERUN / HTQ-001423 sources2 rulesoperator pending
06BUILD STATE
SCOPE, MADE EXPLICIT
What exists. What can be piloted. What is direction.
The website separates a shipped reference surface from bounded implementation capability and longer-term architecture.
Public reference layer
- Company/platform website
- Interactive review-state proof
- Shared design system and evidence UI language
Uses public/sample behavior. No customer or production-performance claim.
One bounded workflow
- Real source and workflow mapping
- Product Intelligence slice
- Concierge / AI-assisted operation
- Approval-gated outputs
Requires design-partner discovery, data access and a measured finish line.
Broader operating system
- Merchant workspace
- Supplier source connections
- External-agent/API surfaces
- Discovery and distribution network
Not presented as shipped software. Expansion must be earned by repeated value.
DESIGN-PARTNER PATH
One workflow.
One measurable finish line.
Do not buy a platform. Start with one recurring technical-product job that has visible inputs, decisions, exceptions and an outcome worth measuring.
- 01Observe the real workflow
Map the trigger, inputs, rules, exceptions, approvals and current consequence.
- 02Scope a bounded paid pilot
Choose one data slice, one outcome, one responsible operator and one measurement.
- 03Operate with evidence
Use software, agent capacity and human review in the proportion the job requires.
- 04Productize only what repeats
Keep, narrow, expand or stop based on cash, capability and distribution return.
DESIGN PARTNER / WORKFLOW 01
What product work should stop living between tabs, files and memory?
The public contact destination is not yet approved; the workflow CTA opens a prefilled email draft without inventing a recipient.