Your Snowflake program, from first idea to governed growth

A program has a life. There is a block for each stage

An idea, a number, a plan, a build, a run, and then growth that has to stay governed. Most teams are somewhere in the middle. Start at the stage you are in.

1. 1 · Know where you stand

   Assess

   The bill keeps growing and nobody can explain why.

   Findings on architecture, security, workloads and cost, in order of priority.

   Private preview

2. 2 · Decide what it takes

   Estimate

   The committee wants a number by the end of the month. We have three quotes that don't compare.

   Scope, estimate, scenarios and a proposal, from your own documents.

   Early access

3. 3 · Agree on how and when

   Plan

   The budget is approved. Nobody agrees on what ships first, or who signs it off.

   The estimate you approved, turned into epics, sprints and tasks with hours and due dates, with burndown, velocity and a completion forecast to follow them.

   Early access

4. 4 · Build it and prove it

   Deliver

   The backlog is six months long, and nobody can prove that what we shipped is right.

   Governed agents, and accelerators for migration, dbt conversion, DataOps, account foundation, data quality and FinOps.

   Early access

5. 5 · Run it in the open

   Observe

   The dashboards were slow again on Monday. We found the query on Wednesday.

   What runs, waits and changes on each warehouse, down to the exact query.

   Early access

6. 6 · Grow under control

   Optimize

   Finance wants the bill split by team. We have one number for the whole account.

   Spend, owners and savings you can check.

   In development

Every stage has a tool. Nobody owns the hand-offs

• Sizing the program took ten days of workshops. The number still came with a shrug.

  A plan with a price on it

  A finding, an RFP or a migration inventory becomes stories, each with an estimate and scenarios you can put in front of a committee.

  On a real bid: 3 hours apart from a package of 10 workshop days.

• The migration job said finished. Nobody could say the data was right.

  Delivery you can let in

  The assistant works on your engineer's machine, read-only by default, and pushes nothing before a person approves the list of changed files. Migrations end with a comparison of source and target.

  12 engines, compared row by row.

• We shipped the fix. Nobody checked whether the bill moved.

  A result you can measure

  Observe shows the same window before and after a change. If nothing moved, you see it.

  Refreshed every 5 minutes by default.

Where this comes from

Every block was built on CRITHINK's own engagements before it was offered to anyone else.

enterprise migrations

100+

countries

7

engines in the migration accelerator

12

between our estimate and a 10-day workshop package, on one bid

3 h

Questions we get first

• Where does our data go?

  Observe runs inside your Snowflake account. In Deliver, the agents run on your engineer's machine, where their conversations stay, and the migration accelerator runs on your machines, on your network. Estimate and Plan are a web application that works from the documents you give it. The security page says what each block reads.

• Can the assistant touch production?

  No. It is read-only by default. In a delivery it writes in the dev target only, it never pushes to the integration or production branch, and nothing is published before a person approves the list of changed files.

• Are you certified?

  We do not claim SOC 2 or ISO 27001 today, and we will not show a badge before an audit is valid. The security page lists what each block reads and where it runs.

• Do we have to buy the whole platform?

  No. Each block works alone. A second one makes sense when one block's output is the next one's input: findings that need a price, a plan that needs delivering, a change that needs checking.

• Do the blocks talk to each other?

  Each block works alone today, and you carry the output of one into the next: findings go into Estimate as documents. Direct links between blocks are what we are building now.

• What if we need people, not software?

  The same engineers run migrations and platform work at CRITHINK consulting. You never have to buy it to use the software.