Services
Defined scope. Tailored proposal. Measurable outcome.
Every engagement ends with a number your CFO can read. After a discovery call, you'll get
a concise proposal with the scope, timeline, and fixed fee. If I don't think I can move it,
I'll tell you and point you at someone who can.
Warehouse & Pipeline Cost Audit
Typical engagement: 2 weeks
Teams whose Snowflake/BigQuery bill grew faster than their data did.
- Query-level cost attribution: which models, dashboards, and teams drive spend
- Top-20 optimization opportunities ranked by effort vs. savings
- Partition, clustering, and materialization recommendations per table
- Quick wins implemented in-week (not just recommended)
- Executive readout with projected annualized savings
Most requested
dbt & Semantic Layer Design
Typical engagement: 4 weeks
Teams drowning in conflicting metric definitions and spaghetti dbt projects.
- dbt project restructure into layered staging → intermediate → marts
- Semantic/metric layer (MetricFlow or Cube) with certified core metrics
- Metric treaty facilitation: written definitions ratified by stakeholders
- Testing, documentation, and PR-based metric change management
- Team training session + async Q&A for 30 days post-delivery
Pipeline Reliability Review
Typical engagement: 2–3 weeks
Teams with on-call fatigue, silent failures, or dashboards nobody trusts.
- SLI/SLO definitions for every production pipeline
- Idempotency and replay-safety audit of ingestion code paths
- Orchestration review (Airflow/Dagster): retries, backfills, dependencies
- Burn-rate alerting design — page on SLO risk, not on noise
- Incident runbooks and data-quality test coverage plan
Web App Build & Deployment
Typical engagement: 3–6 weeks
Teams that need a polished web app shipped without taking on another full-time engineer.
- Responsive web app built around your users, workflows, and existing systems
- API and data integrations with practical error handling and validation
- Production deployment to your preferred hosting platform
- CI/CD pipeline with environment configuration and repeatable releases
- Handoff documentation covering operations, future changes, and ownership
How an engagement works
-
01
Discovery call
Thirty minutes. You describe the problem, I tell you honestly whether I can move the number you care about.
-
02
Tailored proposal
Scope, deliverables, timeline, and a fixed fee in a two-page document. No hourly billing, no scope creep.
-
03
Embedded execution
I work in your repos and your Slack. Your team learns the patterns by reviewing real PRs, not slide decks.
-
04
Handoff & readout
Documented runbooks, a metrics-based readout for leadership, and 30 days of async follow-up included.
Not sure which package fits?
Book the call. Worst case, you leave with a sharper diagnosis of your problem than you had
going in — free.