Built for the whole team.
Share the work. Set who can change it.
Monday trading report
Shared
Lisa ErikssonCan edit
Build the app your team needs by asking for it.
Describe a planner, dashboard or review queue. Dema builds it on your connected data, and you refine it in chat and share it with the team.
Net sales
€1.06M+12.4%
Ad spend
€232K+4.2%
Contribution profit
€262K+18.1%
Profit ROAS
4.6×+0.3
Net sales and contribution profit, weekly
Net sales Profit
Incremental return by channel
- Meta€182K2.4×
- Google€141K1.6×
- TikTok€64K1.9×
- Email€9K4.1×
A useful interface starts underneath
Your workflow.
Your live data.
A buying planner needs stock, demand and margin in the same place. A budget queue needs marketing performance and the evidence behind a proposed change.
Apps use Dema’s shared commercial model, so the interface can change without rebuilding the data underneath.
Explore the data platformWorking tools, built from an instruction
Make room for the way your team works.
Explore planners, review queues and workspaces. Each starts with a job the team needs to do.
You / App instruction
Build a creative review app with radar charts for CM3, CAC, CTR, returns and new customers.
Apps /Meta Creative Gallery···
Ask appMeta Creative Gallery
Facebook & Instagram creatives · ad-platform attribution · Online
Spend
€2,921,284
Blended ROAS
9.08×
Creatives shown
99
Live (total)
218
Needs attention
41
Scoring weights · ranks creatives within each objective
Profit30
35% of score
New-customer value0
0% of score
CTR40
47% of score
Scale headroom15
18% of score
Objective
All objectives
Market
All markets
Sort by
Weighted score (high→low)
Search
Theme or ad name
Sales / Purchase 80
99 of 99
25 adsCream boxy tee (UGC)
12.4× ROAS€184K
30 adsField overshirt (studio)
10.1× ROAS€142K
35 adsOat crewneck (lifestyle)
8.7× ROAS€121K
31 adsScented candle (carousel)
6.2× ROAS€98K
Pause 3 fatigued creative sets in MetaPart 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.
Keep making it useful
Made to be shared. Easy to make yours.
Shared access, company context and tools your team can refine.
Your instructions. Built in.
Company rules, with room for personal preferences.
New instruction
93/5,000
Describe it. Build it.
Describe it, refine it, share it.
From a question to a working tool
01 / Describe“Show what needs reordering.”
02 / RefineAdd cover, margin and lead time.
03 / ShareA planner the team can use.
Teach it once. Run it on repeat.
Instructions, code and references. One reusable command.
Weekly margin review
SKILL.mdmargin_review.pymargin-rules.md
Your message
weekly-margin-reviewRun this for Sweden.
One view across the team
“Finance, marketing, operations, and management can collaborate around the same insights, even if they ask different questions.”
Sandra Lindberg
CFO, Rapunzel of Sweden
Build from a real example
The next useful tool starts here.
Explore the prompts behind planning, reporting and commercial operations apps.
01 /Build
Build a weekly trading brief with a written summary, supporting market figures and a review queue linked to our Google Sheet.
Dashboard shared with the trading team
02 /Build
Build a replenishment planner with stock cover, sell-through, returns and margin. Let our team review reorders and send approved changes to the ERP.
Live planner: approved reorders push to the ERP
03 /Build
Build a budget planner with CAC and CM3. Let us adjust campaign budgets by up to 20% and review changes before syncing.
Live queue: every move waits for a named approval
04 /Build
Build a controlling workspace with a margin bridge, returns and profit by market. Reconcile ERP actuals and publish reviewed figures to our finance sheet.
Live workspace: revenue to contribution profit
05 /Build
Build a visual merchandising studio. Rank by CM3 and sell-through, filter stock and sizes, then approve changes for Shopify.
Live studio: approved rankings push to Shopify
06 /Build
Build an app that finds high-margin products with low sell-through and generates ad creative variants for them, queued to Meta as paused drafts.
Live generator: high-margin laggards get new creative
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.
GDPR compliant.
You
decide.
Scoped permissions. Approval before the actions you choose.
Keep
moving.
New reasoning models. No migration for your team.
Questions
Before you build.
Substantial applications for planning, merchandising, buying, creative review, forecasting, and commercial operations: planners with suggested actions, review queues with approvals, leaderboards, controlling workspaces, and other tools generic software does not fit.
No. Apps are described in plain language and adjusted the same way. There is no code to own, no deployment to manage, and no ticket queue between the team and the tool.
Apps use Dema’s modeled commercial data: orders, costs, returns, inventory, marketing and customer behavior, alongside measurement outputs. Views update as their connected sources refresh.
Yes, within the permissions you set. A planner can push approved reorders to the ERP, a merchandising app can publish rankings to the storefront, a budget queue can execute in ad platforms, each action waiting for a named approval.
Share the app with the team and set who can view, edit or approve. People with editing permissions can refine it in chat: add a column, change a threshold or reshape a view. Review those changes before using them in the shared workflow.
A dashboard shows numbers. An app carries the workflow: the suggested decision, the review step, and the action into the connected system. It is the difference between seeing a markdown is overdue and shipping it.