Enhancing Table Management: Safe Build vs Production Modes
Feedback / Feature Request: Safer “Build Mode” vs “Production Mode” for Tables Context (real workflow): I’m frequently building complex tables for client work (e.g. waterfalls, formulas, Claygents) where I need to:
- 1.
See the full dataset (TAM, row counts, distributions)
- 2.
Iterate on table structure and dependencies
- 3.
Validate logic before spending credits at scale
Today, this puts me in a tough spot between:
Sandbox mode → safe, but I can’t see the full picture (TAM, segmentation, real row behavior, reporting on yield)
Live tables → full visibility, but auto-run makes it very easy to accidentally burn credits while still “building”
Pain point: Auto-run defaulting to ON for every new table makes early-stage table construction risky — especially when adding waterfalls or dependent columns. Even when trying to be careful (“Save and don’t run”), it’s easy for something to trigger unintentionally during setup.
What I wish existed: A clearer separation between building and production, for example:
A true “Build / Draft Mode” where:
Full dataset is visible
Columns can be added/configured
Enrichments are never allowed to execute automatically
Then a deliberate “Promote to Production” action that
Enables auto-run
Starts spending credits intentionally
Is suitable for client-facing workflows
Why this matters: For consultants and teams reporting findings to clients, we need to explore the entire dataset first before committing to spend. Right now, that iteration phase is where most accidental credit burn happens. Totally understand the tradeoffs around keeping data fresh — this would just add a safer, more intentional path for advanced builds. Happy to expand or mock this out if helpful. Appreciate the team being open to feedback 🙏
