The platform

One platform, seven layers of intelligence.

Preckon isn't a single model bolted onto a viewer. It's a chain of specialized intelligence layers — each reading one kind of document, each handing structured output to the next — sitting on a shared foundation and orchestrated by the Construction Copilot.

Documents Requirements Elements BOQ Estimate Procurement
Architecture

How Preckon is built.

Click any layer to see what it reads, what it does, and what it hands to the next.

Construction CopilotOrchestration · conversational access to any layer · human-in-the-loop on every output
ORCHESTRATION
▸ Documents in Procurement out ▸
Platform FoundationMulti-tenant data · encryption & audit spine · provider-independent AI orchestrator · construction knowledge graph
FOUNDATION
TenderLogix Tender Intelligence LAYER 01 / 06
Reads
What it does
Hands off
The foundation

What every layer stands on.

The modules are only as trustworthy as what's beneath them. Preckon's foundation is built for sensitive documents, enterprise scale, and outputs a reviewer can defend.

Multi-tenant isolation

Row-level security separates every client's data. One tenant's documents never touch another's.

Immutable audit spine

Every action and change is recorded — who, what, when — so any number can be traced to its origin.

Provider-independent AI

An orchestrator routes each task to the right model. No lock-in, and no single vendor sees everything.

Construction knowledge graph

Reasoning grounded in real construction logic — elements, assemblies, trades — not generic text.

Human-in-the-loop

Review and correction is built into every layer. Nothing is costed or issued without a person confirming it.

White-labeling

Per-tenant logo and brand color are first-class — run Preckon under your own identity.

How it reasons

The orchestrator and the graph.

Every layer draws on the same construction knowledge graph and the same provider-independent orchestrator — so the platform reasons about buildings, routes work to the best model for each task, and shows how it got there.

Task routing

Each step goes to the model best suited to it.

Knowledge graph

Grounded in construction, not generic language.

Provider independence

No lock-in; data never pools with one vendor.

Explainable

Every output traces back to its source.

See the whole chain on your project.

Bring one drawing set. Watch it move through every layer — documents to a procurement package — in your first call.

Book a demo