Built for the whole team.
Share the work. Set who can change it.
Monday trading report
Shared
Lisa ErikssonCan edit
Agents
Your best work.
On repeat.
Describe a recurring job. Set when it runs and what it can do. An agent works with your live commerce data and delivers the result to your team.
Your instruction
“Have the trading report ready before the Monday meeting.”
Monday tradingRunning
- Read orders, costs and returns
- Apply the team's reporting skill
- Explain the changes in profit
This week, explained.Week 24
12movements explained
MarginReturns
Stock risk
Stock risk
Preparing the report for #tradingEvery Monday. Already taken care of.
Trusted by commercial teams at leading brands
From instruction to outcome
One instruction. A complete run.
Follow the work from your request to the evidence, the result and the connected system where it lands.
Your instruction
Prepare next week's budget moves where profit is incremental, and send them for approval.
Profit Pilot
Runs Fridays 16:00- Queried modeled data
Spend, contribution margin, and returns by channel and market · last 28 days
- Asked the MMM
Diminishing-returns curves per channel · profit-optimal split for next week
- Used skill: budget-move-guardrails
Max ±20% per move, never against low stock cover
Control stays with you
Give it a job.
Give it boundaries.
A report can run read-only. A proposed budget change can wait for review. Each workflow gets the access and approval rules the work calls for.
Keep useful automation close to the people responsible for the outcome.
Lower the daily budget
PMax · Germany
Daily budget
- Current
- €120
- Proposed
- €100
Budget changes above 10% need approval.
Lisa ErikssonGrowth lead
ReviewerWaiting for approval
Skills
Teach it once.
Run it on repeat.
Package the instructions, code and reference files behind a repeatable job into a skill.
Reuse the method across agent runs, without explaining every step again.
Filesscriptsreferences
Weekly margin review
Find what changed in profit, and what needs attention.
Procedure
- Compare CM3 with the previous week.
- Break down the change by market and product.
- Explain the three biggest losses in euros.
Part of the platform
Measurement included.
Marketing mix modeling, incrementality testing and causal attribution are built into Dema. Bring that evidence into your questions, budget reviews and recurring workflows, alongside the rest of your commerce data.
Built for the work after the first run
A routine the whole team can rely on.
Shared data, clear ownership and routines that grow with your team.
Your metrics. Precisely defined.
Define once. Use across every answer and workflow.
Contribution
After costs. After advertising.
Net revenue€100,000
- Product costs
- − €40,000
- Operations
- − €15,000
- Ad spend
- − €25,000
Contribution margin20%
Defined once. Used by both.
ReportsAgents
All your data. One live model.
Commerce and marketing, connected in one model.
Tatti Lashes
20workflows built
in three weeks
in three weeks
Built by the team, without writing code.
Your instructions. Built in.
Company rules, with room for personal preferences.
New instruction
93/5,000
Built by the commercial team
“What took two people three to four months now runs in a single command. We built 20 workflows in three weeks without writing a line of code.”
Tom Everson
Digital Director, Tatti Lashes
Put a real routine to work
Start with the work that repeats.
Reports, checks, product sets and follow-ups. Explore the instruction behind each workflow.
01 /Automate
Prepare next week's budget moves where profit is incremental, and send them for approval.
Budget moves with evidence, waiting for sign-off
02 /Automate
Every Monday at 07:00, deliver the trading report to #trading with the largest movements explained.
Delivered to #trading and email
03 /Automate
Scan every channel and market weekly. Flag what hurts profit and prepare the fix.
Flags with the prepared fix attached
04 /Automate
Review search terms weekly. Draft negative keywords in Google Ads for terms that spend without converting, and send them for approval.
Negative keywords drafted, waiting for approval
05 /Automate
Rebuild our RFM segments every Sunday on contribution margin — not revenue — and sync them to Klaviyo.
Segments rebuilt on margin, synced overnight
06 /Automate
Rebuild the “Most popular” collection in Shopify every Monday from actual sales — excluding sale items and anything with broken sizes.
Collection rebuilt on sales, eligibility enforced
07 /Automate
Every morning at 07:30, email leadership a short brief: revenue, spend, and contribution profit vs plan, with anything unusual explained.
One-page brief vs plan, unusual moves explained
08 /Automate
Forecast 35 days of outbound volume and inbound returns per warehouse, and deliver it to the 3PL in Google Sheets every Monday.
Capacity forecast in the 3PL's own sheet
09 /Automate
Segment the product feed by contribution margin and refresh the segments daily, so campaigns bid by profitability — not just revenue.
Margin segments synced to every feed
10 /Automate
Pause any campaign whose cost per new customer runs 25% above its 30-day average for 3 days.
Campaigns paused when CAC breaks the guardrail
11 /Automate
When a promoted style drops below three weeks of stock cover, lower its budgets in Meta and Google Ads and tell me why.
Budgets lowered on low-cover styles, with the why
12 /Automate
Watch coupon sites for our voucher codes. When one leaks, quantify the weekly margin exposure and alert #commercial.
Leaked codes caught with the margin exposure sized
Connected to all your data.
Orders, inventory, returns, marketing and omnichannel data connect once and stay maintained. Nobody on your team owns the pipeline.
Built on the same foundation
One model. More ways to work.
The work moves.
The control stays.
Give your team the capabilities to move faster, with the controls to make them part of everyday operations.
EU / US
Inference and pipelines in the region you choose.
Always
yours.
Your data is never used to train models.
You
decide.
Scoped permissions. Approval before the actions you choose.
Keep
moving.
New reasoning models. No migration for your team.
Questions
Before you put it in motion.
They can remain read-only, draft actions, or execute through connected systems. You decide which tools each agent can use, which actions need approval, and who can approve them.
Recurring commercial work with a clear trigger, decision, and destination: weekly reports, keyword exclusions, budget guardrails, feed segments, sheet syncs, anomaly response, inventory monitoring, CRM activation, and more.
A schedule (every Monday at 07:00, daily at 06:00) or a condition in the data (refund rate breaks its range, a product drops below three weeks of cover). Both run against live modeled data.
Reports and alerts deliver to Slack, email, and Google Sheets. Executed changes go to connected systems — Meta, Google Ads, product feeds, the ERP, and other integrations — always within the permissions you set.
The agent flags it instead of quietly publishing. Missing sources, broken definitions, and failed runs surface to a named owner — the opposite of a zap that fails silently.
Teams connect their core commerce systems first, then begin with one recurring workflow — most start with a weekly report or a spend guardrail and expand from there.
Bring one commercial job
Give the recurring work a new owner.
Build with Dema.