Delivery, migration & support
Pre-project analysis for DWH implementation
Before development starts, I examine the data sources, metrics and requirements, design the warehouse architecture, and give a transparent estimate of timeline and cost.
What is pre-project analysis
Pre-project analysis is a survey of data sources, metrics and reporting requirements, followed by the design of the target architecture of the future warehouse and its data model. On this basis I prepare a well-grounded estimate of the project's timeline, cost and risks — before DWH development even begins. The analysis reduces uncertainty and provides a clear plan: what we build, in what order and why. As a result, the decision to implement is made on facts rather than on gut feeling.
When you need pre-project analysis
What the service includes
Survey of sources and integrations
I examine the source systems — CRM, advertising accounts, the website, the app and the databases — and record the export methods, formats and existing integrations.
Gathering and prioritizing requirements and metrics
I collect reporting requirements, formulate the key metrics and set priorities, so it's clear which data the warehouse actually needs.
Data profiling and quality assessment
I profile the data in the sources, assess its completeness, integrity and real volumes, and find gaps and discrepancies that will affect the project.
Designing the target architecture and data model
I design the warehouse architecture with layers (staging, ODS, detailed layer, data marts) and a data model that fits the agreed metrics and dashboards.
Choosing the stack and infrastructure
I select the database, orchestration and transformation tools, BI and infrastructure that fit the volumes, budget and speed requirements — with a rationale for each choice.
Estimate of timeline, cost, risks and a roadmap
I prepare a well-grounded estimate of timeline and cost, describe the risks, and put together an implementation roadmap with clear stages.
How the analysis works
- 01
Kickoff meeting and goals
We discuss the business objectives, expectations of the warehouse and the project's success criteria, and fix the scope of the analysis.
- 02
Inventory of sources and access
I compile a list of source systems, find out how data is exported, and arrange the necessary access.
- 03
Interviews with data owners and requirements gathering
I interview the data owners and reporting stakeholders, collect requirements and prioritize the metrics.
- 04
Data profiling and quality assessment
I profile the data in the sources, assess its quality, integrity and volumes, and record the issues found.
- 05
Architecture and model design and stack selection
I design the layered architecture with data marts, the data model, and select the stack that fits the task.
- 06
Report with estimate, risks and a plan
I prepare the final report with the architecture, an estimate of timeline and cost, risks and a roadmap, and present the results.
Projects
Analytics platform for the digital agency YA AGENCY
Analytical data warehouse and dashboards for Ash
End-to-end analytics and infrastructure migration for WiseAdvice-IT
Dashboards for the SaaS platform Entera
Analytical data warehouse for a chain of bars and restaurants
Analytical data warehouse for the Neolombard pawnshop chain
Unified data warehouse and dashboards for the delivery service Edostav
Data warehouse for the financial analytics project VISUALSECTORS
Tech stack
dbt 
OpenMetadata Clients
Testimonials
Pre-project analysis pays off before the first line of code: instead of building a DWH blind, you get a clear architecture, a data model and a well-grounded estimate of timeline and cost. I examine the sources, profile the data and design a solution that fits your tasks — so the project starts with lower risk and a transparent implementation plan.
Shall we discuss your task?
FAQ
How is pre-project analysis different from a BI audit? +
A BI audit is an assessment of an existing system: dashboards, the warehouse and the pipelines, finding problems and points for improvement. Pre-project analysis is preparation for a new DWH: a survey of sources, architecture design and an estimate before development starts.
What do I get as the result? +
The target architecture of the future warehouse, the data model, a list of sources and integrations, a well-grounded estimate of timeline and cost, a description of the risks, and an implementation roadmap.
Do I then have to build the DWH with you? +
No. The report is self-contained: you can use it to make a decision, for a tender, or hand it over to another contractor for delivery.
How long does the analysis take? +
There are no fixed timelines — the duration depends on the number of sources, their complexity and the quality of the data. We fix the scope of work at the kickoff meeting.
Is access to the systems required? +
Yes — profiling the data and assessing the sources requires access to the key systems. We agree on the minimum necessary set; where access isn't possible, we rely on exports and descriptions from the data owners.