Gross Margin by Channel

Try the Agent

Select a preset query to run the agent. Responses use the KWF-generated configuration and sample data — no live database connection required for this demo.

Agent Configuration & Data

Every agent configuration generated by the Knowledge Work Foundry includes the query logic, data schema, and sample output. What you see below is the actual KWF output for this workflow candidate.

• Agent Query
• Table Schema
• Sample Output

-- KWF Agent Query: Last-Month Gross Margin % by Sales Channel
-- Parameters: {sales_channel}, {start_date}, {end_date}
-- Runtime resolves relative phrases like "last month" to explicit dates
-- Table: pura_vida_foods_dev.sales_dw.fact_sales

SELECT
  '{sales_channel}' AS sales_channel,
  SUM(revenue)                               AS total_revenue,
  SUM(profit)                                AS total_profit,
  CASE
    WHEN SUM(revenue) = 0 THEN NULL
    ELSE ROUND(SUM(profit) / SUM(revenue), 4)
  END                                         AS gross_margin_pct
FROM  pura_vida_foods_dev.sales_dw.fact_sales
WHERE sale_date BETWEEN '{start_date}' AND '{end_date}'
  AND   sales_channel = '{sales_channel}';

-- Business logic:
-- If gross_margin_pct IS NULL → "No sales for {channel} in this period."
-- Otherwise → format as percentage (× 100, one decimal): "47.6%"
-- Use this value verbatim across Sales, Finance, and Ops to prevent recomputation

-- Source table: pura_vida_foods_dev.sales_dw.fact_sales
-- Delta table on Databricks — precomputed revenue and profit columns
-- Agent reads only: revenue, profit, sale_date, sales_channel

CREATE OR REPLACE TABLE pura_vida_foods_dev.sales_dw.fact_sales (
  sale_id          STRING           NOT NULL,
  sale_date        DATE             NOT NULL,
  customer_id      STRING           NOT NULL,
  product_id       STRING           NOT NULL,
  order_id         STRING           NOT NULL,
  quantity         DECIMAL(10,2)    NOT NULL,
  unit_price       DECIMAL(10,2)    NOT NULL,
  unit_cost        DECIMAL(10,2)    NOT NULL,
  revenue          DECIMAL(15,2)    NOT NULL,  -- precomputed
  cost             DECIMAL(15,2)    NOT NULL,  -- precomputed
  profit           DECIMAL(15,2)    NOT NULL,  -- precomputed
  profit_margin    DECIMAL(8,4),
  discount_amount  DECIMAL(10,2)    DEFAULT 0.00,
  discount_percent DECIMAL(5,2)     DEFAULT 0.00,
  sales_channel    STRING,                     -- Retail | Wholesale | Online
  order_priority   STRING,
  shipping_cost    DECIMAL(10,2)    DEFAULT 0.00,
  created_at       TIMESTAMP,
  updated_at       TIMESTAMP
)
USING DELTA;

Cognitive Labor Breakdown

The KWF analyzes every workflow candidate across three layers of cognitive labor. The split below is the actual output of the KWF analysis for the Last-Month Gross Margin % by Sales Channel workflow for a Sales Manager role.

The execution layer is rule-following: retrieve from one table, apply one formula, format to one decimal. The logic is defined and has been for years — it just hasn't been encoded anywhere. So the Sales Manager encodes it manually, from memory, every month.

The judgment layer is where the Sales Manager's time actually belongs. Deciding whether a margin compression in the Retail channel reflects a product mix shift or a pricing concession that needs to be unwound is a Sales Manager call. Building the spreadsheet that produces the number is not.

Business Value Translation

Redirecting the execution layer of this workflow to the agent does not "save 45 minutes per month." It changes what a Sales Manager does before every performance summary and QBR. Instead of arriving having built the margin view, they arrive having read it — and the conversation starts at the judgment layer: what to do about the channel movements, not what the numbers are.

At the three-layer value model, execution work generates roughly 1× value per dollar of labor cost. Judgment work generates 2–5×. Strategic work generates 5–15×. A team of Sales Managers whose execution allocation for this workflow drops from 50% to ~40% is not saving time — they are redirecting high-cost resources to the work that actually leverages their expertise. For a team that runs monthly channel reviews, this is the difference between a meeting that starts at the numbers and one that starts with the decisions.