How it works

A data team, with a person accountable for every number

Engineers scope, build, and test the work, and a senior lead checks it before it reaches you. Here’s the whole process, start to finish.

The request lifecycle

From question to trusted answer

Step 1
You submit a request
Pick from the catalog or describe what you need. Add the acceptance criteria that matter to you.
Step 2
We scope it
Your lead confirms what you mean, asks questions if something is unclear, and sends a fixed credit estimate.
Step 3
You approve
Credits are reserved, not spent. The service-level clock for your plan starts now.
Step 4
We build
An engineer builds the SQL, models, tests, and docs inside your warehouse and repository.
Step 5
QA and sign-off
The work passes the checklist for that request type. Your lead reviews it and delivers it.
Step 6
You accept
Credits are used when you accept, or automatically after 5 business days. Want changes? Request a revision.

Credits

If a request takes us longer than we estimated, we absorb it. Scope changes get a new estimate you approve first.

Approving an estimate reserves credits. They’re only used when you accept the delivery. Cancel before we start and they come back.

Spend the same credits on a dashboard one week and a new data source the next. No change orders.

When a connector, model, or test breaks, we fix it at no credit cost and add a test so it doesn’t recur.

Where we work

Every client gets a shared Slack channel. Each request gets its own thread.

Code lands as pull requests in your GitHub. Data stays in your BigQuery or Snowflake.

Requests, estimates, deliveries, credits, and onboarding progress in one place.