Skip to content

Data platforms

One place where the numbers are right.

When each team calculates revenue its own way, nobody trusts the report. We build a data platform sized to your team, with clear definitions, tested pipelines and alerts, so people and AI tools get the same answer.

Who it's for

Companies whose numbers live in spreadsheets and app databases, where each team calculates revenue its own way. Also companies that want AI tools to answer data questions correctly, because those tools are only as good as the data models and definitions underneath.

What we deliver

The right architecture for the size of the problem

Warehouse or lakehouse, ELT or ETL, batch or streaming. On Databricks, Snowflake, BigQuery, Redshift or Fabric, or on Postgres and DuckDB for small teams.

Data models people and AI can read

  • Dimensional models built with Kimball's four steps: business process, grain, dimensions and facts.
  • A declared grain for every fact table.
  • History kept with Type 2 slowly changing dimensions where it matters.
  • Conformed dimensions shared across teams.
  • Clear table and column descriptions.

Pipelines that catch problems before users do

  • Raw, staging and mart layers (bronze, silver and gold) built with dbt.
  • Loads that pick up only new files.
  • Tests on keys, relationships and accepted values, plus freshness checks.
  • Model contracts on shared tables.
  • Documentation written into the catalog.

Orchestration

The run order, schedules, retries and an owner who gets the alert, plus a plan for bad batches: fix, filter or quarantine.

Governance

Access by role, column masks and row filters for personal data and a separate, restricted identity for each AI agent.

Cost control

Right-sized compute, incremental loads and sampling before running AI over large tables.

How we measure it

  • Tests passing and freshness targets met.
  • Totals that reconcile to the source systems.
  • Failures caught before a report goes out.
  • Monthly platform cost.

Background

These methods come from And's course plan for ETM 538, Decision Support Systems: Data Warehousing, at Portland State University (Winter 2027).

Questions

Common questions

Do we need clean data before we start?
No. Discovery looks at the data you have and says what's usable now and what needs fixing. Some projects start with that fix.
Can you work with our existing data warehouse?
Yes: Databricks, Snowflake, BigQuery, Redshift, Postgres and others. The modeling and testing methods don't depend on the vendor.
Where does our data go?
It stays in your accounts wherever possible. AI models are used through business API plans whose terms don't allow training on your data, or through your own cloud (for example, AWS Bedrock) when it must stay there. [TODO: verify current provider terms before publishing]

Have a process that eats hours every week? Let's look at it together.