Principals & family offices
Multi-entity holdings, personal exposure on signed documents, and offices that need a named practice — not a vendor seat model.
Request private scoping reviewPrivate document intelligence for files that carry liability.
For operators, principals and compliance-heavy teams — explainable, auditable outputs with human sign-off before anything becomes final.
- Messy documents → structured review
- Recommendations → source-backed explanations
- Human sign-off → audit trail
File № SCN-2026-01 · Restricted circulation
A private practice · By introduction and qualification
Cross-border trade · Marketplace operations · Multi-entity group ops
What it does
A proprietary engine ingests operational documents inside your boundary and returns structured, explainable outputs — each row traceable to sources, each release gated by a named signatory. Vertical deployments (trade, marketplaces) are proof on the same architecture, not separate products.
Illustrative output
Illustrative output — review-ready classification
Input
“LED desk lamp, 10W, USB-C, touch dimmer”
HS / TN VED
9405 42 390 0
Confidence
0.86
GRI trace
- Rule 1 → Heading 9405 (lamps and lighting fittings)
- Rule 6 → Subheading 9405.42 (LED, electric)
Sources
- · EAEU TN VED, Chapter 94
- · TR CU 004/2011, Annex 1
§ 01
Position of the practice
Whom the practice serves — and what it refuses.
- 1.1
- The practice serves principals and their offices — where a document, once signed, becomes someone’s personal exposure.
- 1.2
- It does not sell software seats. The proprietary engine is deployed privately, under NDA, inside the client’s boundary.
- 1.3
- Engagements are few and scoped. Access is by introduction or written request.
§ 01a
Who should enter
Four corridors. One practice — pick the file that matches your office.
Trade · customs · import
Supplier files, explainable HS / TN VED, certification flags, and declaration workflows where someone must defend the output.
Exhibit A · full fileMarketplace operators
SKU-level unit economics as a live proof surface — briefing and qualification on EN; not self-serve checkout on this layer.
Exhibit B · briefing gateLegal · contract · compliance
Clause extraction, obligation mapping, and review packs where counsel or compliance must trace every recommendation to a source.
Scope a redacted sample§ 02
The asset
One loop from ingest to human gate.
Ingest → extract and normalize → retrieve precedent → explainable structured output → human sign-off → optional private deploy. Vertical products are wedges and proof on the same architecture — not separate experiments.
Ingestmessy inputs
Normalizeextract · schema
Classifyexplainable codes
Explainsources · trace
Sign-offhuman gate
Proprietary asset of the practice — annex to the file.
§ 03
Terms of engagement
From private briefing to production in your boundary.
- 3.1
Private briefing + scoping review
Async brief plus process and data-sensitivity review — fit confirmed before any call.
- 3.2
Scoped paid pilot
Thin slice on redacted samples under NDA; before/after metrics, an agreed review window, and a written commercial frame — scoping review → paid pilot → private deployment, not public SaaS tiers on EN.
- 3.3
Private production deployment
Licensed system in your boundary — explainable, auditable, operator-in-the-loop.
Optional call only after fit is confirmed.
Trade operators: full deployment dossier at scanovich.ai/customs/
§ 04
Deployment map
One engine. Honest labels on every surface.
- Live
Cross-border trade · HS / TN VED
Explainable classification under NDA — import ops, brokers, compliance.
- Live
Marketplace unit economics
Proof surface (Yandex.Market); additional fee models under contract.
- Scoped pilot
Declaration archive search
Precedent layer on redacted DT archives — meaning, not filenames.
- By introduction
General counsel · contract corpus
Source-attributed retrieval on indexed material — not generative counsel. Scoped pilot.
- By introduction
Permitting · subsurface dossiers
Structured extraction and gap review on technical annexes.
- By introduction
Multi-entity group operations
Consolidated review-ready structures and audit trail across entities.
Vertical modules share one governed engine — not separate experiments.
Exhibit A
Cross-border trade
Where liability is highest, the engine is live.
Cross-border trade document intelligence: supplier normalization, explainable HS / TN VED classification, and certification requirement detection — deployed under NDA for import ops, brokers, and compliance teams.
Wrong classification and inconsistent supplier data create regulatory and margin exposure — someone has to defend the file.
Illustrative classification output sits in the preview above — the trade dossier carries the full annotated sample with GRI trace and certification flags.
Full trade dossierExhibit B
Marketplace economics
Marketplace economics as a second surface.
SKU-level profit after fees, logistics, and ad spend — live for Yandex.Market; the same engine extends to additional fee models under contract. Proof surface, not the primary engagement path.
Marketplace proof surfaceProprietary IP — available under license and NDA after qualification.
From the principal of the practice
Every output this engine produces was designed to survive one test: a person with authority signs it, and stands behind it. That standard is mine before it is the system’s. If your office runs documents that carry that weight, request access — I review every brief myself.
Aleksandr Mordvinov
Principal of the practice