Data architecture services that give running platforms one design before anyone rebuilds

Our data architecture services start from what you run today and end in a target design and a roadmap, ready for your engineers or ours to build.

Illustration of scattered data sources joined into one data platform that feeds analytics dashboards and AIIllustration of scattered data sources joined into one data platform that feeds analytics dashboards and AI

WHERE IT STARTS

Was your data platform designed, or did it grow?

A data architecture is the written design of where your data lives, how it moves between systems, who owns each part and which platform holds it. We deliver it as four documents: a current-state assessment, target-state diagrams, a platform recommendation and a phased roadmap. The arguments then happen on paper, before the next build.

Finance and sales bring two revenue figures to the same meeting. A dashboard number can't be traced back to any source. A new source takes weeks to join, because each data pipeline was built for one report, and the cloud bill grows faster than anyone can explain. Those are design problems, and another round of engineering on top rarely fixes them.

You may not need this at all. If your reports agree and a new source slots in without a rebuild, the architecture is doing its job, and the money is better spent on the next pipeline. If the real goal is a model, preparing data for AI is the narrower job to start with.

Illustration of a data platform that grew piece by piece, with tangled pipelines running between sources and reportsIllustration of a data platform that grew piece by piece, with tangled pipelines running between sources and reports

DELIVERABLES

What do you receive at handover?

Current-state assessment

A data architecture assessment of what you run today: every source, pipeline, store and report, and who owns which data. It records where numbers drift apart, where loads fail or slow down, and which parts of the bill no workload accounts for. A roadmap needs this first, since nobody can order fixes for problems nobody has found.

Target-state diagrams

Diagrams of the platform you are moving toward: which systems feed it, where each kind of data is stored, how it flows from raw to reporting-ready and where access is controlled. They are drawn for two readers, the engineers who build it and the people who approve its budget. They also show where each shared metric, such as revenue, is defined and calculated, and who owns the definition. A new source can be placed on them before anyone writes code for it.

Written platform recommendation

A single platform recommendation with the reasons written down, so your engineers can challenge it and whoever signs the budget can follow the argument. Of everything in the design, the platform is the hardest choice to reverse, which is why it gets a document of its own.

Phased roadmap

Every change in priority order, grouped into phases with the dependencies between them. Each phase can be estimated and built on its own, and the plan still makes sense if you stop after phase one. Where a phase moves data, the roadmap includes a way back at cutover.

Illustration of four handover documents: an assessment, target-state diagrams, a platform recommendation and a roadmapIllustration of four handover documents: an assessment, target-state diagrams, a platform recommendation and a roadmap

SCOPE

What does the design cover?

The design covers the whole platform, on AWS, Azure or Google Cloud, or as a hybrid that keeps some systems on-premises. It decides four things that are expensive to change later: where the target state runs, how storage is layered, how data gets in, and who may touch it.

Architecture is the drawing. Building the data warehouse and its pipelines is engineering, and data model design settles the tables inside it. Both are separate jobs, and we take on either as part of the wider data practice.

Target state, cloud or hybrid

Which platform holds which data, and which systems stay where they are. A hybrid that leaves some systems on-premises is often the right answer when moving them costs more than it returns.

Warehouse and lake layers

How storage is split into layers, from raw data to tables a report can trust, on Snowflake, Databricks, Redshift or BigQuery.

Integration and pipelines

How each source reaches the platform and who owns each data pipeline once it runs. Streams cost more to run, so they go only where a decision needs data within minutes.

Our engineers work with Airflow, dbt, Fivetran, Kafka and Spark.

Governance and access

Data governance drawn into the first version of the design: who owns each dataset, who can reach what, and where lineage and metadata are recorded.

Quality checks sit where data enters, because a bad record is cheapest to stop before it reaches a report that someone has already forwarded to the board.

PATTERNS

Which pattern and platform fit your situation?

Warehouse, when reporting is the job

A warehouse fits when most questions are structured reporting on data you can model: revenue, orders, stock. It is the simplest of these patterns to run well. Kimball dimensional models deliver one business process at a time, an Inmon-style normalized core suits one enterprise-wide model, and Data Vault fits many sources that change often and need full history. It fits badly when data scientists need the raw files a warehouse is not built to keep.

Lake, for raw data that can wait

A data lake goes wrong when people report straight off it. With no owners and no catalog, it turns into a folder of files nobody trusts. Used for what it does well, it holds raw and semi-structured files cheaply until someone needs them, such as event logs, documents and data science work. Most teams that need a lake also need a warehouse beside it.

Lakehouse, when two groups share one copy

A lakehouse keeps raw and modeled data on one storage layer and promotes it through medallion-style stages, from raw to reporting-ready, so analysts and data scientists read the same tables. It pays off when both groups are real and growing. For a team that only runs reports, it is more platform than the problem needs. Databricks is the usual candidate, and lakehouse architecture on Databricks is a service of its own.

Hybrid, when some systems should stay put

The hard part of a hybrid is the boundary. Some systems stay on-premises because they are costly to move, tied to hardware or held in place by a contract, and the rest move to the cloud. If nobody draws the line between the two halves, every report needs data from both and no one owns the join. The design draws that line first.

Data mesh and data fabric, for many owners

A data mesh gives each dataset to the business domain that produces it, under standards shared across the company. A data fabric lays one metadata and integration layer over sources that stay where they are. Both pay off with several teams that can each run their own data, and with a single data team the overhead usually outweighs the gain.

How we pick the platform

We weigh four things: the workload and data volume, the cloud you already run and what your team can operate, the cost at your expected volumes, and which sources must connect. The written platform recommendation shows how each candidate compares on all four.

Illustration of a data platform blueprint with storage, pipeline, governance and analytics layersIllustration of a data platform blueprint with storage, pipeline, governance and analytics layers

PROCESS

From assessment to roadmap

We start from what you already run, and draw nothing until we have read it. An architect, a business analyst and a delivery manager run discovery and design, reading pipelines, schemas and reports with the people who maintain them.

  1. STEP 1

    Discovery and current-state assessment

    We map your sources, pipelines, storage and reports, and the decisions each one feeds.

  2. STEP 2

    Platform recommendation

    We shortlist platforms only after reading your sources and reporting needs, then test each against your criteria.

  3. STEP 3

    Target-state design and phased roadmap

    We draw the target state, then break the route there into phases with their dependencies.

  4. STEP 4

    Optional build with our engineers

    Our data engineers can build to the design alongside your team, or take the whole build on as a project.

CASE STUDIES

Design decisions from our data cases

Faster queries for a mobile software developer

For a global mobile software developer, we moved the heaviest sources of its Redshift warehouse to Redshift Spectrum and gave an ML model's calculations a separate pipeline on AWS Batch and Docker. ETL moved from Python scripts to Airflow. The client got 6x faster queries, 12x faster raw data collection and 98.8% savings in computing resources. The case reports these figures for the project as a whole.

Fivetran and dbt pipelines for an education company

A professional education company had a warehouse on Amazon Redshift, while its Salesforce, Shopify and SAP data sat outside it. After analyzing its sources, reporting needs and existing architecture, we chose Fivetran for ingestion and dbt for modeling, then built the pipelines that brought that data in, with validation and monitoring.

A Python wrapper library over a fixed API

A trading platform for crypto and tokenized assets took its analysis data from one API. Retrieval was inconvenient, and changing the API wasn't an option. We left the API as it was and built a Python wrapper library over it, which streamlined retrieval without compromising data integrity. The same data pull now runs 3x faster through the library.

Illustration of a data warehouse and pipelines feeding analytics charts that load fasterIllustration of a data warehouse and pipelines feeding analytics charts that load faster

IN YOUR SYSTEMS

How we work in your systems

Illustration of a data warehouse with individual access keys for each engineer and a design document beside itIllustration of a data warehouse with individual access keys for each engineer and a design document beside it

Accounts you issue, removed at the end

In your warehouse, cloud account and source systems, we work through named accounts you issue, each limited to what that person's part of the work needs, and removed when they leave.

EU hosting for what we control

Systems we control are hosted in the EU. Your warehouse and cloud account stay wherever you keep them, and the design works around your rules for where data may live.

A platform pick you can defend

We hold no partner status with AWS, Microsoft, Snowflake or Databricks, so the pick follows your criteria. Our team includes certified AWS, Azure, Snowflake and Databricks engineers.

Build with us or without us

The design is written for whoever builds it. Your team can build from it alone, or we can add engineers to implement the architecture beside them.

TERMS

Engagement models and terms

Project delivery

We deliver an agreed scope end to end: plan, team, milestones, QA and release. You make the product decisions and accept each milestone.

Fixed price per milestone after discovery, or time and materials against an estimate.

  • Scope changes go through change requests.
  • On fixed-price projects, a warranty period agreed in the contract, usually 30–60 days.

Discovery phase

A short phase before a build: requirements and backlog, architecture, an estimate and a delivery plan.

Fixed price, usually 2–4 weeks.

  • The outputs stay with you whether or not the build continues with us.

Staff augmentation

Our engineers join your team and work in your process and tools. You manage them; we source, vet and contract them.

Hourly rate per engineer by role and seniority, invoiced monthly.

  • If an engineer isn't the right fit, we replace them within 14 days at no extra cost.
  • Knowledge transfer to the replacement engineer isn't billed.
  • There is no free trial period.
  • 30 days' notice to take an engineer off or end the engagement, with no minimum term beyond it.
  • Out-of-hours on-call only if agreed with you; we set its hours and billing together.
  • After two years, moving an engineer onto your own staff is something we can discuss.

Whichever model you choose

  • We reply to an inquiry from the contact form within 24 hours.
  • We sign an NDA before work starts, and IP passes to you on payment.

MORE CASE STUDIES

Designs that kept the next change cheap

Most architecture decisions are made before anyone knows the real load, the next platform or the next question the business will ask. A design that ages well doesn't bet on one answer. It keeps the part most likely to change cheap to move.

A fintech warehouse we built keeps its transformation logic in Python and Airflow, outside Vertica, so a later move means repointing pipelines, not rewriting them. A health app's pipeline had to scale with a load nobody could forecast, and a load test found its cost problems before launch.

Do your reports disagree with each other?

Tell us which sources feed your reports and where the numbers lag. We will suggest where the assessment should start.

FAQ

Data architecture services: common questions

How long does the work take, and what decides it?

Our discovery phase, which usually takes 2–4 weeks, comes first. The architecture work around it has no standard length: it depends mostly on how many sources you have and how well they are documented. Ten well-described sources go faster than four that only one person understands.

What does it cost, and what sets the price?

The discovery phase has a fixed price, set by the size of what is being designed and who joins it, such as a lead engineer. If you go on to a build, project delivery runs at a fixed price per milestone, or as time and materials against an estimate. The Engagement models and terms section compares the models we offer.

Who owns the design and the documents you produce?

You do. All four documents are yours to keep, even if another team does the build.

Who gets access to our data and systems?

Each engineer signs in through your own identity system, so you can see and revoke their access yourself. An assessment rarely needs more than read access. We sign a data processing agreement wherever we handle your data.

Do you push a particular cloud or platform?

No. The platform is picked on criteria you agree with us, and every reason is on paper for your team to check. It can also be the platform you already run.

We have our own data team. How do we work together?

Your architect or data lead keeps the final say. Our written recommendation is there to be argued with, and it is usually better for it. When the build starts, our data engineers can join your team and work in your process and tools.