Skip to content
VISKOURABetter Data. Brighter Decisions.

DISCOVERY + THREE DELIVERY PATHS

Your starting point.
One governed outcome.

Discovery defines the agreed analytical middle layer: build a new warehouse/mart and semantic layer, extend existing approved analytical assets, or deliver only bounded Gold, mart or semantic models from accepted curated data. Client reporting remains downstream.

Client-owned source/CDC and landing → contracted Viskoura engineering → client-owned reporting and consumption.

Build, adaptation and reuse are explicit. Discovery precedes commitment.

01 - Discovery & scope definition

Understand first. Commit with clarity.

Start with
One workflow, recurring incident, disputed KPI or named AI use. Identify the owner and permitted evidence.
What we do
Profile representative periods, investigate existing logic and source authority, map dependencies and define expected outcomes.
What you receive
A source/object inventory, semantic-design direction, baseline measures, prerequisites, risks and acceptance cases.
Before build
Agree deliverables, exclusions, effort assumptions, client contributions and the target environment.

Discovery is an agreed engagement, not an automatically free assessment or a guaranteed saving.

02 - New middle-layer build

Engineer the agreed analytical middle layer.

Starting condition
Approved landing datasets or existing accepted assets are available. Agree schema, keys, grain, freshness, security and source authority.
Viskoura delivery
Contracted canonical Bronze (if needed), Silver transformations, Gold models, marts, semantic definitions, rules, history, quality and lineage evidence.
Client contribution
Client-owned extraction, CDC and landing delivery; runtime platform, credentials, scheduling and independent acceptance owners.
Acceptance evidence
Inbound population checks, reconciliations, transformations, business-metric validation, SIT/UAT support and accepted handover.

Plug-and-play through agreed integration contracts still requires target-specific configuration, integration testing and client acceptance.

03 - Existing platform extension

Keep what works. Strengthen what is missing.

EXISTING

Usable ingestion and models

Retain suitable source routes, infrastructure and accepted components.

ENHANCED

Governed outputs

Adapt or build agreed Gold, data mart and semantic objects; the client retains downstream reporting.

Viskoura delivery
Explicit adaptations and new objects, quality controls, reconciliation, mappings and implementation evidence.
Client contribution
Existing architecture and code, authorized access, responsible owners and representative discrepancies.
What you can verify
A reuse/build register, lineage boundaries, independently expected outputs and non-regression in the affected flow.
Completion
Agreed business behaviour, required technical tests, accepted limitations and operating ownership.

04 - Bounded Gold / semantic development

Accepted landing. Governed analytical handoff.

CLIENT-OWNED

Approved landing

Source connectivity, capture/CDC and the agreed delivery contract.

Validated handoff
VISKOURA SCOPE

Governed models to consumption handoff

Agreed Bronze/Silver/Gold, marts, semantic definitions and validation evidence; not report or dashboard development.

At the boundary
Confirm accepted Silver/curated data, schema, grain, keys, freshness, access and source authority before bounded development.
Viskoura delivery
Only the agreed Gold, mart and semantic structures, documented metrics, quality controls, lineage, tests and handover.
Where migration applies
Compare equivalent populations and definitions. Disclose approved semantic changes and unresolved differences.
Acceptance
Validate governed datasets and semantic meaning; the client retains release, runtime and downstream consumption acceptance.

Existing accepted Bronze or Silver can be reused; no rebuild is assumed. Snowflake-first methods need validated target-specific adaptation.

1 / 4