A company reported that their Snowflake compute bill became excessively high because their BI dashboards were treating the data warehouse like an OLTP database, spinning up a warehouse for every...

{
  "signal_id": "0c117a99-eebc-5d0d-a577-2dbfe4d9a869",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-09-25T10:18:36+00:00",
  "company": {
    "name": "Snowflake",
    "domain": "snowflake.com"
  },
  "data": {
    "nsfw": false,
    "stage": "none",
    "awards": 0,
    "timing": "completed",
    "topics": [
      "cost optimization",
      "data warehouse",
      "bi",
      "analytics"
    ],
    "post_id": "1wpslo8",
    "summary": "A company reported that their Snowflake compute bill became excessively high because their BI dashboards were treating the data warehouse like an OLTP database, spinning up a warehouse for every minor user interaction.",
    "category": "pricing",
    "comments": [
      {
        "url": "https://www.reddit.com/r/analytics/comments/1wpslo8/comment/pbzeo2r/",
        "depth": 0,
        "score": 6,
        "author": "CaliSummerDream",
        "excerpt": "I don’t understand the situation. What do you mean a warehouse was set up whenever a user changed a date filter? What is a warehouse in your books? How many thousands of “warehouses” did you end up with?",
        "posted_at": "2026-09-25T14:53:00.000Z",
        "author_url": "https://www.reddit.com/user/CaliSummerDream/"
      },
      {
        "url": "https://www.reddit.com/r/analytics/comments/1wpslo8/comment/pbz20gy/",
        "depth": 0,
        "score": 2,
        "author": "ketopraktanjungduren",
        "excerpt": "We put in as many relevant metrics as possible into a table to create one big table (OBT). Then extracts are scheduled to query through each OBT. This strategy has been able to cut out cost up to 50%\n\n To push down the cost even lower, we refactor the dbt models and put Snowflake cronjobs to use.",
        "posted_at": "2026-09-25T13:57:38.000Z",
        "author_url": "https://www.reddit.com/user/ketopraktanjungduren/"
      },
      {
        "url": "https://www.reddit.com/r/analytics/comments/1wpslo8/comment/pc36222/",
        "depth": 0,
        "score": 1,
        "author": "Bitter-Design-9308",
        "excerpt": "The biggest win for us was moving all BI dashboards to scheduled refreshes instead of live queries, and setting a hard warehouse timeout. That alone cut our Snowflake compute spend by about 40% because users stopped firing off ad hoc queries against huge fact tables.",
        "posted_at": "2026-09-26T01:16:27.000Z",
        "author_url": "https://www.reddit.com/user/Bitter-Design-9308/"
      }
    ],
    "evidence": [
      "[post] Our Snowflake adoption was going great until finance saw last month's compute bill.",
      "[post] We realized our BI dashboards were essentially treating Snowflake like an OLTP database. Every time a user tweaked a date filter or reloaded a morning report, a warehouse would spin up and charge us.",
      "[comment u/Bitter-Design-9308] The biggest win for us was moving all BI dashboards to scheduled refreshes instead of live queries, and setting a hard warehouse timeout. That alone cut our Snowflake compute spend by about 40% because users stopped firing off ad hoc queries against huge fact tables."
    ],
    "virality": "low",
    "post_date": "2026-09-25T10:18:36.000Z",
    "post_kind": "text",
    "post_text": "Our Snowflake adoption was going great until finance saw last month's compute bill. We realized our BI dashboards were essentially treating Snowflake like an OLTP database. Every time a user tweaked a date filter or reloaded a morning report, a warehouse would spin up and charge us.To make it worse, analysts were getting annoyed by slow dashboard load times, so they started writing their own custom SQL extracts inside individual workbooks. We were burning cash on redundant queries and suddenly had four conflicting definitions of \"Active Users\" floating around the companyInstead of aggressively tweaking auto-suspend settings (which just pisses off stakeholders) or migrating BI tools, we changed the architecture. We put a headless semantic layer (Cube) between the warehouse and our UI. Here is what actually solved the problem: Caching killed the compute costs: We moved the heavy lifting to Cube Store. Now, when 100 people open the morning dashboard, it hits the cache. The UI loads in milliseconds, and Snowflake stays asleep. Centralized logic: We ripped all the SQL out of the BI layer. Metrics are now defined once in version-controlled YAML. Everyone gets the exact same math. BI for Agents: We've been testing LLMs for self-serve. Letting an AI write raw SQL against Snowflake is a fast way to burn money and get hallucinations. Now, the LLM just hits the semantic layer API for...",
    "sentiment": "negative",
    "subreddit": "analytics",
    "event_date": "2026-08",
    "post_title": "We didn't let our BI tools drain our Snowflake account",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/analytics/comments/1wpslo8/we_didnt_let_our_bi_tools_drain_our_snowflake/",
    "entity_role": "vendor",
    "post_author": "Familiar_Season1255",
    "mention_count": 7,
    "mention_surge": true,
    "subreddit_url": "https://www.reddit.com/r/analytics/",
    "total_upvotes": 0,
    "comments_total": 14,
    "total_comments": 14,
    "event_date_text": "last month's",
    "other_companies": [
      {
        "name": "Cube",
        "role": "adopted",
        "domain": "cube.dev"
      }
    ],
    "post_author_url": "https://www.reddit.com/user/Familiar_Season1255/",
    "signal_category": "feedback",
    "comments_included": 3
  }
}

curl https://signals.autobound.ai/v1/signals/0c117a99-eebc-5d0d-a577-2dbfe4d9a869 \
  -H "X-API-KEY: $AUTOBOUND_API_KEY"

curl -X POST https://signals.autobound.ai/v1/companies/enrich \
  -H "X-API-KEY: $AUTOBOUND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"snowflake.com","limit":20}'