July 5, 2026 · StartupQuickstart

Why your data stack should be boring

Dashboards that disagree are a process problem, and a bigger warehouse won't fix them. Here is the small, boring stack we deploy, what it costs to run, and when you don't need it at all.

A dashboard of charts on a laptop screen

Every early-stage team hits the same wall, usually somewhere between the seed round and the Series A board deck. Revenue in the deck doesn't match revenue in Stripe, activation is defined three different ways in three different dashboards, and the one script that held it all together was written by an engineer who left in March. Nobody is lying. The numbers are just built on sand.

The instinct at that moment is to buy something big: a warehouse, a BI platform, maybe a data hire. Most of the time that's the wrong move, or at least the wrong first move. What you need first is a small, boring pipeline that someone actually operates. Here is what that means concretely.

The trust problem is a process problem

Dashboards rot for predictable reasons, and none of them are about scale:

  • Metrics live in chart configs. When "active user" is defined inside a Metabase query, a Mixpanel report and a founder's spreadsheet, the three will drift apart. There is no single definition to be right or wrong.
  • Ingestion is a cron job someone wrote once. It doesn't alert when the source API adds a field, it silently duplicates rows on retry, and nobody notices until a chart looks weird two weeks later.
  • Nothing is tested. Application code gets a CI suite. The SQL that computes the number your board sees gets pasted into a console. Bad data doesn't throw exceptions; it just looks plausible.

A bigger warehouse or a prettier BI tool fixes none of this. Treating the pipeline like production software does: version control, tests, alerts and one place where each metric is defined.

Most startups have small data

Jordan Tigani, one of the early engineers on Google BigQuery, wrote that when he looked at BigQuery's own customer base, the vast majority had less than a terabyte of data in total, and even among heavy users the median was well under 100 GB. Startups before Series B usually sit at the small end of that curve. At that size you don't need Snowflake, Spark or a platform team. DuckDB is an in-process, columnar analytical engine released under the MIT license, and on a single machine it will scan years of a typical startup's history in seconds. In the builds we operate, the stack below runs on roughly $100-300 a month of compute, which is a rounding error next to the salary of the data engineer you were about to hire to babysit something heavier.

Our default build is deliberately unexciting, and every piece is open source or close to free at startup scale:

  • Ingestion with managed connectors (Airbyte or dlt) pulling your product database, Stripe and the handful of SaaS tools that matter. It runs on a visible schedule with retries, and dlt, for example, detects schema changes, adds new columns and can alert you when a source shifts, instead of a silent cron job that just breaks.
  • Storage and compute in DuckDB over object storage, or your existing Postgres if that's honestly enough. Columnar, fast and cheap enough that you stop thinking about it.
  • Modeling in dbt: every metric is a version-controlled SQL model with an owner, a description and a git history. When someone asks "why did activation change," the answer is a diff you can read.
  • Orchestration in Dagster, so "did last night's run succeed" is a page you can open instead of a feeling.

What "tested" actually means for data

Data tests are cheap to write and catch the failures that actually happen. dbt ships with four generic tests out of the box (unique, not_null, accepted_values and relationships), and those cover most of what follows:

  • Shape tests. Primary keys are unique and not null, and a join didn't silently fan out and double your revenue.
  • Domain tests. status is one of the values your code can produce, and currency amounts are never negative unless they're refunds.
  • Freshness SLAs. Orders landed in the last 6 hours, or someone gets paged before the CEO opens the dashboard. dbt lets you set warn_after and error_after thresholds per source so this is configuration, not a custom script.
  • Reconciliation. The pipeline's monthly revenue agrees with Stripe's own Balance summary report to within rounding. One query, run daily, ends an entire class of board-meeting surprises.

When a test fails, the run stops and the alert names the model and the assertion. That is the whole trick: bad data gets caught upstream of the chart, while it's still an engineering ticket and before it becomes a credibility problem.

When you don't need any of this

If you're pre-product-market-fit, your questions are simple and your data fits in Postgres, then a read replica and a lightweight BI tool are the correct stack, and we'll tell you so. The signals that you've outgrown it are specific:

  • Two dashboards disagree on a number that matters, and it takes days to find out why.
  • Answering "which channel produces customers who retain" requires joining product, billing and marketing data by hand in a spreadsheet.
  • Analytics queries are slowing down the production database.
  • An investor or enterprise customer asks for a metric you can't reproduce two quarters in a row.

The part nobody budgets for: operations

A pipeline is a small production system, and it keeps needing attention after the build. Source APIs change fields. A connector update breaks a sync. A backfill needs to run without double-counting. Someone has to glance at the freshness dashboard in the morning and own the fix when it's red. That ongoing operation, more than the initial build, is where most in-house data efforts quietly die, because it's nobody's job.

It's our job. We build the stack above in a few weeks, then run it on retainer: monitoring, break-fix, backfills and new models as your questions evolve. Your engineers keep shipping product and your numbers stay boring, which is the goal.

Sources

Want systems like this built for you?

We build and run data pipelines, websites, and AI automation for startups.