What decision should we make smarter?
Describe the business outcome you want to influence. Attach docs, databases, or a live source — I'll draft a decision flow you can tune, approve, and publish.
Weekly markdown optimizer
Decide which slow-moving SKUs to mark down each Monday, by store cluster.
Pipeline risk scoring
Surface deals likely to slip and suggest next-best actions for sellers.
Daily ad budget reallocation
Shift budget between Google, Meta, TikTok based on CAC and ROAS drift.
Store staffing recommendation
Recommend shift adjustments using footfall, weather, and event calendars.
Got it. I've drafted a Weekly Markdown Optimizer flow. Here's what I'm proposing:
It joins POS + on-hand + seasonality signals, detects SKUs that will miss sell-through by > 2 weeks, and suggests markdown tiers by store cluster. Guardrails enforce your margin floor from the Q2 memo (gross margin > 28%).
I couldn't verify your competitive pricing feed — I've left that node unconfigured. The flow still runs without it, but confidence drops ~9%.
Decision flows
Recommendations for you
3 new since FridayProjected gap to sell-through: 3.1 weeks. Recommending a 15% markdown for 2 weeks. Estimated impact: +$184k margin over do-nothing.
Engagement drop > 40% in the last 10 days on deals totalling $2.4M. Suggested next-best action per deal is attached.
ROAS drift detected; TikTok marginal return is currently 1.7× Meta. Guardrail: brand-safety tier only.
Projects
Retail Pricing
Every pricing, markdown, and promotion decision for the retail business. Flows share the Q2 pricing memo, margin guardrails, and the retail.sales + retail.inventory warehouses.
Connectors
Templates
Governance
Architecture · Build vs. wrap vs. use
Build custom
Wrap & extend
Use as-is
Standalone MVP
- Chat → flow compiler (v1)
- 3 node types: Data, Decision, Action
- 5 connectors via MCP + Snowflake + Postgres
- 1 vertical template (retail markdown)
- Slack notifications · log-and-alert actions only
- No approvals, no back-test
Team & trust
- Projects · knowledge · tags
- Approvals & Slack approve button
- 15+ connectors · first writebacks (Jira, Salesforce)
- Back-test / simulation engine
- Explanation engine v1
- Basic audit ledger
Enterprise
- SSO + SCIM (WorkOS)
- Data residency · customer VPC option
- Immutable audit ledger · SOC 2 Type II
- Row-level security propagation
- Partner / SDK API parity w/ DiwoCatalyst
- Guardrails runtime · auto-rollback
DiwoCatalyst merger
- Import shim for Catalyst KPI trees
- Unified billing + seat model
- Shared connector library
- Marketplace of flow templates
- Sub-agent runs (per-cluster fanout)