Revenue is up. Why is margin down?
−€1,450,000 gross profit, mostly costs and discounts. Reconcile periods and trace the change to orders, prices and costs.
Cost and discount evidence; recorded agent drafts
See the margin demoAI workflows for finance and operations teams
Find the issue.
Check the evidence.
Decide what’s next.
Catch invoice overcharges, explain margin changes, reconcile CRM and billing — with every number traced to its source.
Pilot from €2,500 excl. VAT · fixed price · 2–3 weeks. Scope and exact price agreed in your proposal.
Invoice INV-01
100 individual units · ITEM-A
€120.00
Contract CON-OLD
€10.00 per 10 units
€100.00
Price difference to investigate
€120.00 minus €100.00 equals €20.00.
Pending human review
A finding is useful
when you can check it.
The full example compares 16 invoices with contracts and credits. 4 findings need investigation; 8 cases remain unresolved.
Follow the investigationFrom alerts to an exclusive total
Two kinds of candidate, counted once.
Synthetic invoices, dated contracts and credits. Unknown amounts stay outside the total.
Pending review€35 + €120 = €155
- Price deviations €35
- Possible duplicate €120
Excluded
Overlapping alerts: €20 · Not counted twice
Hatched: drawn to the same scale as the bar above, but not added to it.
8 unknown cases kept for human review; amounts stay outside the total.
Source: procurement-demo/result.json
View data table
| Evidence | Amount | Treatment |
|---|---|---|
| Invoices checked | 16 | Dated contracts and credits |
| Findings | 4 | Candidates for investigation |
| Unknown cases | 8 | Kept for human review; amounts unknown |
| Price deviations | €35 | Candidate for review |
| Possible duplicate | €120 | Candidate for review |
| Exclusive total | €155 | Sum of candidates |
| Overlapping alerts | €20 | Excluded; counted once |
What this example establishes
€20 of overlapping alerts is excluded from the total, as are unknown amounts. Calculations are checked against independent fixture labels. No live ERP integration. Findings are candidates, not confirmed loss or savings; production accuracy and time saved have not been measured.
Start with a business question.
Working demos, each a possible pilot scope. All run on synthetic data; findings are candidates for your team to review, not confirmed results.
A new inquiry. What should you know before replying?
7 supplied facts, 3 unknowns and 3 questions. Prepare company context and a response draft for review.
Recorded briefs, pending review
See the lead demoMonday’s numbers. Can you trust them?
3 source snapshots; simulated missing support holds the draft for human review. Stop when billing, CRM or support is missing or stale, and hold the draft for human review.
Stops on missing data; deterministic, no live integration or model call
See the reporting demoDo CRM and billing agree?
240 differ; 30 need a person. Compare CRM and billing records and inspect exact cent differences.
Cent-level differences, 30 for review; deterministic calculation
See the reconciliation demoDiscuss your workflow See all demos
How the reporting workflow handles missing data Engineering walkthrough
One workflow.
A clear first engagement.
Agree the question and sources first. Build a read-only pilot, review its findings, then decide whether to extend it.
Discuss your workflowSources
Records and agreed context
6,000 CRM + billing rows3,000 subscription pairsChecks
Calculations and missing data
Match key + amount, currency, statusExact IDs and integer-cent rulesFindings
Evidence you can trace back
2,730 agree · 240 differTrace each difference to both recordsHuman decision
Review before taking action
30 need a personResolve unknowns before any action
Workflow outline. Scoped permissions and human approval before actions.
- 01 / Question and data
Define what needs checking
Agree the business question, representative data, access and how a useful result will be evaluated.
- 02 / Reviewable result
Build and test a bounded pilot
Trace findings to sources, check calculations and surface missing data. Define permissions, review points and a fallback before any actions.
- 03 / Decision on further work
Review before extending
Assess the result against agreed criteria, then discuss implementation and support. The proposal confirms the pilot’s exact price, timing and subsequent terms.
A pilot first, then implementation and support.
Step 1 · Pilot
from €2,500
One-time fixed price, excluding VAT. One read-only workflow in 2–3 weeks; your proposal confirms the scope and exact price.
Step 2 · After a successful pilot
Indicative monthly budgets in EUR, excluding VAT, for implementation and support. They are not part of the pilot price.
Focused
Recommended startOne scoped workflow, read-only first
€2,500 / month
+ €5,000 one-time setup
- Source-linked findings your team reviews and approves
- Agreed permissions and approval points
- Monitoring and fixes for that workflow
Custom
Connected investigations across your tools
€5,000 / month
+ €12,000 one-time setup
- Everything in Focused, across linked workflows
- Findings that combine data from several tools
- Checks updated from reviewer corrections
Enterprise
Multiple workflows across teams and systems
€10,000 / month
+ €25,000 one-time setup
- Everything in Custom, for several teams
- Separate review queues and permissions per team
- Support responsibilities agreed in writing
Not sure where to start? I’ll help you identify a focused first project.
Clarity before commitment.
Can we start with our existing tools?
I check data quality, API access and permissions during scoping. A read-only pilot can analyze exports and prepare findings without changing your records. Later integrations and actions are scoped and approved separately.
How much control will our team have?
We agree what the workflow may do, what needs approval and how exceptions reach your team. These boundaries become part of implementation and handoff.
What data do we need for a first pilot?
Start with a business question, representative data or sample exports, and an example of a useful result. For metric-based work, we also agree on definitions. Feasibility is established during scoping.
What does a pilot cost?
A pilot starts from €2,500 excluding VAT at a fixed price and takes 2–3 weeks. Your proposal confirms its scope and exact price. The implementation and support budgets apply to later work and are not included in the pilot.
How are timing and ongoing support agreed?
Milestones depend on the workflow, integrations and data access. The proposal defines timing, support responsibilities, response arrangements and commercial terms before the corresponding work begins.
What needs
a closer look?
Describe a recurring task, a number you can’t explain, or a decision that requires checking several systems. I reply personally.
[email protected]Send an inquiry
Inquiry received. Thank you for telling me about your workflow. I’ll review your message and reply by email with follow-up questions. If the workflow fits, we’ll arrange a discovery call.
We couldn’t send this. Your details are still here. Please try again later or email [email protected].
What happens next
- You describe the question or workflow, where the data lives and who reviews the result.
- I reply with follow-up questions.
- We arrange a discovery call to check fit, data access and review boundaries.
- If it fits, I propose a scoped, read-only pilot with agreed acceptance checks: from €2,500 excluding VAT, fixed price, 2–3 weeks.How a pilot works
Your inquiry goes to Danil Galeev, founder of MadeBy.Expert.About the engineer
Latest articles
Engineering notes on how the demos are built and what holds up when agents run for real.
· 5 min read
The reconciliation step where we use no model at all
Reconciling 3,000 CRM and billing subscriptions with deterministic code, an independent expected-result manifest and a review queue for the rest.
· 4 min read
The agent finished. Who turns off the VM?
A coding agent finishes at 6 p.m. Which limits stop the command, the agent session and the workspace, and what evidence to keep before cleanup.
· 2 min read
Agent memory’s real failure is currency, not retrieval
Agent memory often retrieves the right record after it stopped being true. Why staleness is a state-management problem and what validity windows change.