Platforms · Snowflake
Snowflake consultants for the loads, the models and the credit bill.
Snowflake is rarely the hard part. The hard part is what lands in it, what the columns are agreed to mean, and why the spend moved last month. We handle all three, whether that takes an hour or a quarter.
What we connect it to
- + your stack
If it has an API, we can connect it.
What we do
The three services, on Snowflake.
-
Get source data in, on schedule and without duplicates
A single feed or the full landing pattern: Salesforce, NetSuite and the operational databases arriving in Snowflake on schedule, no duplicates even when a load is repeated, and a record of what every run touched.
-
Model it so two teams reach the same number
That can mean the full model built properly, or an afternoon untangling why two dashboards disagree. Every change is proven in a safe copy of production before it ships, and the definitions live in source control rather than inside a saved query nobody owns.
-
Keep credits, roles and the daily loads under control
Warehouses sized for the worst query anyone ever ran, auto-suspend switched off, privileges granted to individuals until nobody can say who sees what. We attribute the credits to the workloads causing them, size and suspend the warehouses to match, and take the quick calls: the role that broke a dashboard, the load that doubled overnight.
The everyday work
Not everything is a project.
Problems like these come up in every system, and not all of them are even problems. Some are an hour of advice, or writing down how something works before the person who built it leaves. Most take us minutes or hours, and you do not need a project with us, just send them over.
Fixes
- A task that silently stopped running
- A warehouse that never suspends
- A role change that broke one dashboard and nothing else
- A load that quietly doubled its runtime
Documentation
- The account and role hierarchy written down
- Runbooks for loads, tasks and the daily checks
- A map of what feeds each schema and dashboard
Advice
- A second opinion on warehouse sizing and spend
- Whether Snowflake, Fabric or Databricks fits your team
- An hour on modelling approach before the build
Proof
Patterns we have already delivered.
Anonymised accounts of work our principals delivered in previous roles. These are the patterns that come up on Snowflake in nearly every scoping call.
Governed by design
One governed data platform for CRM and ERP data
How does data from every system land somewhere the whole business can trust?
The result
One governed home for every data feed
Read the case study
One version of the truth
One customer record across CRM and ERP
Why does every system hold its own version of the customer?
The result
One customer record read by every system
Read the case study
Never duplicates
Sync CRM and ERP records without duplicates
How do you keep two systems in step without creating duplicates?
The result
Zero duplicate records created on a rerun
Read the case study
Common questions
What buyers ask before they call us.
How does a Snowflake engagement usually start?
If the build is already defined, we start straight away. If something needs attention today, failing loads or credit spend nobody can explain, we can step in within days. And if you are not sure what the fix should be, we can run a two to three week discovery that maps your sources and account layout, and the blueprint is yours to keep.
Our Snowflake bill keeps climbing. Can you help with that?
Usually. Most of it traces back to warehouse sizing, auto-suspend left off, queries scanning far more than they need, and loads running more often than anyone reads the result. We attribute the credits to workloads first, so the changes are argued from evidence rather than instinct.
How is the work priced?
Per engagement rather than from a rate card. A discovery is a fixed fee for a time-boxed piece of work. A scoped delivery carries a fixed shape and a fixed price agreed up front, so the number does not move as we go.
Are you a Snowflake partner?
No. We hold no Snowflake certification and no vendor sponsorship, so nothing we recommend earns us anything beyond the engagement itself. What we bring is delivery history on Snowflake ingestion, modelling and cost work, alongside the Azure and Databricks certifications the team does hold.
Do you only take on project work?
No. A steady share of the week is small: a broken automation, a question that needs an experienced answer, documentation nobody ever wrote, or plain advice before you commit to something bigger. Most of those are minutes or hours, not days, and they get the same care whether you run a two-person business or an enterprise team. When one turns out to be bigger than it looked, you already know who is holding it.
Get started for free.
One call to understand the problem, and a written price if we can help.