Your data. One foundation.
Connect commerce, ad spend and ERP actuals.
Your financial close.
Built into your own app.
Describe the finance view you need. Dema builds an app on your connected commerce and ERP data, from returns and costs to profit down to CM3.
Finance reviewExample
From revenue to what you keep.
Contribution after marketing · CM3€20,000
- Net revenue
- €100,000
- Product costs
- −€40,000
- Operations
- −€15,000
- Ad spend
- −€25,000
Reviewed figures → Finance sheetUsed by the teams at
“With unified and enriched data from Dema's AI models, our strategic discussions are sharper, and our time spent on analysis is greatly reduced.”
Jonas Angelöv
Mini Rodini
Your finance view. Built around your definitions.
Ask for a margin bridge, market comparisons or an exception queue. Add your close rules in the same conversation.
app.dema.ai/controlling-workspaceDemo workspace
Workspace / Controlling workspaceShared with your team
Commercial overview · This week
Financial close
Net revenue€357kAll markets
Contribution€108.3kAfter costs & returns
Contribution margin30.3%After costs & returns
Return costs€11.4kAll markets
From revenue to contribution
ERP actuals + commerce data€357k
Net revenue−€11.4k
Return costs−€156.7k
Product & fulfilment−€80.6k
Acquisition€108.3k
ContributionGoogle SheetsFinance close / reviewed actuals
0 items selected for Google Sheets.
All your data. Ready for AI.
All your commerce data, connected and ready for AI. Dema joins the records, defines your metrics and keeps your apps and agents current.
Reconcile commerce with ERP actuals, including returns, fulfilment costs and profit down to CM3.
- Commercial activity
- Orders, refunds, customers, product views & sessions
- Cost & inventory
- ERP actuals, product costs, fulfilment, inventory value & returns
- Contribution
- Product-level marketing spend, market allocations & shared CM3 definitions
Have the close ready for review.
Ask an agent to reconcile the week, flag variances and update the finance sheet before the team reviews it.
Your agent deliversInteractive example
The close is reconciled. Two costs need a look.
Finance / Weekly closeGoogle Sheets
Delivered- variance lines explained
- 2
- variance threshold
- 10%
| A | B | C | |
|---|---|---|---|
| 1 | Cost line | Actual | vs plan |
| 2 | Returns · DE | €22.8k | +14% |
| 3 | Freight · UK | €16.8k | +12% |
| 4 | Cost of goods | €142k | −2% |
Actual vs planChange logDefinitions
ERP actuals matched to the finance sheet. Returns and freight exceed plan.
One definition of profit. Down to CM3.
See what remains after product, fulfilment and marketing costs, with returns accounted for. Your app, agent and finance team work from the same definitions.
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
Your first finance workflow.
Ready for your team.
Connect your data, describe the work and put a reviewed workflow in your team’s hands.
Your workflow. Built by asking.
Describe your close, cost allocations and exception rules.
Your team. Ready to act.
Review reconciled figures and share the finance sheet with your team.
Questions about the controlling workflow
Yes. These are examples of what you can create. Describe your own app or recurring job in chat, using your connected data and available tools. Review the result and refine it in the same conversation.
Start by describing the job as you would to a colleague. Ask for the views, metrics and rules you need, review the result, and ask for changes. Your team can create and adjust apps and agents in plain language.
Yes, because they are built from the same definitions. Contribution margin is reconciled once from orders, COGS, freight, fees, and returns, and every answer, close, and report reuses that definition. There is no second version of the number to argue about.
Yes. The 10%-from-plan rule is a starting point. Thresholds can differ per cost line and market, and each flag can route to a named owner, so the close reflects how your team actually reviews the numbers.
No. It sits on Dema's modeled data, connected to the systems you already run. The difference is that the weekly close builds itself and arrives explained, instead of being assembled from exports every Friday afternoon.
Yes. The close remains an active Dema session. Ask why freight moved, split a variance by market or product, or turn a recurring concern into its own monitor, without rebuilding anything.
You do. Finance workflows typically run read-only: the close reports and explains, and anything that acts (an adjustment, an escalation) waits for a named approval first.
See how much of it runs itself.
Bring your workflow. See how to create the app or agent your team needs in a live walkthrough.
Build with Dema.