DAM/IDM, entry thresholds, volume, fees, imbalance risk, and the decision before gate closure.
Bespoke pilot · 30 calendar days
Test one real decision workflow before you scale anything.
Together we freeze one market or zone, one priority workflow, and a measurable baseline. Alvo connects its already-live market layer, configures your thresholds, and produces inspectable decision packages; an accountable person approves every action.
30 days from kickoff1 workflow · 1 market/zoneNo automated order submission
Who it is for
The pilot works when your team already makes a recurring decision.
The best fit is a professional team that can appoint a workflow owner, provide the operating assumptions, and compare its process before and after the pilot.
One reviewable view of sources, freshness, forecast band, assumptions, and rationale.
One agreed charge/discharge case over live prices; reserve-market demo assumptions stay labelled.
Test the fit of available read-only data and exports in your analytics process, without auto-execution.
Frozen scope
One workflow, narrow enough for an honest decision in 30 days.
We freeze the scope in a kickoff note. New markets, execution automation, or separate integrations are not added silently; they receive a separate estimate after the closing review.
Included in the base pilot
- One 45-minute kickoff and a written scope note
- One market or bidding zone and one priority workflow
- Configuration of agreed volumes, fees, thresholds, and gate time
- A weekly 30-minute evidence review with the workflow owner
- A closing readout, evidence export, and scale / iterate / stop decision
What we need from you
- A workflow owner and an accountable person who approves decisions
- Market/zone, gate times, current workflow, and the current baseline
- Volumes, fees, risk limits, and success formula — never secrets in the browser
- Private data or API access only when the agreed scope requires it
- Access, retention, DPA, and allowed-user requirements before private data is loaded
Exact deliverables
Five outputs you can accept or reject.
Every deliverable has an owner, date, and evidence — not a presentation-only label.
Agreed market/date/gate context, volume, fees, thresholds, and the human approval role.
Available prices, sources, timestamps, freshness, regional context, and forecast status for the chosen scope.
Trade date, market/zone, assumptions, formula, forecast band/status, human approval, and methodology link.
A sample of pilot decisions and a review export; missing or demo fields remain explicitly labelled.
Baseline comparison, open data gaps, security/ops notes, and a written scale / iterate / stop verdict.
Illustrative package · not live data
Where UAH 137,125 comes from — down to the formula.
A fixed synthetic fixture shows the shape of an Alvo package. It is not an OREE publication, customer result, or trade instruction.
Inspect inputs, timestamps, formula, and approval stateIllustrative result: UAH +137,125Recomputable
- Trade date
- 15 Jan 2025
- Market / zone
- DAM · UA-IPS
- Volume
- 5 MWh per position · 20 MWh total
- Fees / threshold
- UAH 12/MWh per leg · minimum net UAH 250/MWh
- Source timestamp
- Synthetic OREE-shaped fixture · 14 Jan 2025, 19:00 UTC
- Forecast status / band
- Illustrative P10–P90 UAH 4,200/MWh–UAH 13,100/MWh · issued 14 Jan 2025, 18:30 UTC
- Human approval
- Pending human review · automatic submission off
- Average net spread
- UAH 6,856.25/MWh
Formula
For each position: ((sell − buy) − 2 × fee) × volume
Σ result = UAH 137,125
| Position | Buy | Sell | Gross spread | 2 × fee | Net spread | Result |
|---|---|---|---|---|---|---|
| 1 | 14:00 · UAH 4,478/MWh | 21:00 · UAH 13,300/MWh | UAH 8,822/MWh | −UAH 24/MWh | UAH 8,798/MWh | UAH 43,990 |
| 2 | 03:00 · UAH 5,200/MWh | 19:00 · UAH 11,824/MWh | UAH 6,624/MWh | −UAH 24/MWh | UAH 6,600/MWh | UAH 33,000 |
| 3 | 04:00 · UAH 5,600/MWh | 20:00 · UAH 11,924/MWh | UAH 6,324/MWh | −UAH 24/MWh | UAH 6,300/MWh | UAH 31,500 |
| 4 | 05:00 · UAH 6,000/MWh | 22:00 · UAH 11,751/MWh | UAH 5,751/MWh | −UAH 24/MWh | UAH 5,727/MWh | UAH 28,635 |
The result shown is only the arithmetic output of illustrative inputs. It does not guarantee P&L, forecast accuracy, or price availability.
Timeline
30 days from kickoff to a decision.
The clock starts once the scope is written and the agreed inputs are ready.
- Day 1Kickoff · 45 min
Freeze the workflow, roles, baseline, inputs, success metrics, and data boundary.
- Days 2–5Configuration
Configure available sources, thresholds, fees, volume assumptions, and package template.
- Days 6–21Shadow operation
Use Alvo alongside the current process; a person still approves every decision.
- Days 22–27Measurement
Compare completeness, decision time, usage, and data gaps with the frozen baseline.
- Days 28–30Readout
Deliver the evidence export and agree a scale, iterate, or stop verdict.
Success criteria
Measure process quality, not a promised trading outcome.
The numeric baseline is frozen in the kickoff note before the first pilot decision. If a metric lacks enough data, that is a data gap — not a positive result.
Trade date, source/freshness, assumptions, status, and human approval are present.
Or another written minimum for a lower-frequency workflow.
Compare median current and pilot process time with no pre-set uplift.
Every absence, fallback, or demo assumption is visible before the decision.
P&L, forecast accuracy, and savings are not guaranteed criteria. They can be added only as a separately pre-registered metric with an adequate sample.
Security and data boundary
Define the boundary before private inputs enter it.
The public demo needs no customer data. For a private pilot, access, retention, deletion, and allowed users are written down before the first upload.
No external model egress
The deterministic Alvo core computes authoritative numbers; market and customer data is not sent to an external LLM.
Human approval
Alvo provides decision support. It does not submit market orders or replace the accountable trader.
Least-data scope
We take only fields needed for the one agreed workflow; never put secrets or credentials in the request form.
Written controls
Before private-data start, agree the access list, retention/deletion, DPA need, and incident/support channel.
What is live — and what is not
The pilot never presents demo data as live.
Exact availability is checked again for the selected market/date during kickoff.
Live today
- — Official OREE DAM/IDM and ENTSO-E flows for the supported workflow
- — Supported regional day-ahead zones with source attribution
- — Forecast band, decision brief, audit context, and exports — with status/freshness
Demo or conditional
- — Imbalance risk: Live only on observed inputs; a fixture remains Demo
- — BESS reserve economics: demo assumptions until a licensed market feed exists
- — Private inputs/API integration: only after scope, access, and retention agreement
Not included
- — Automated market-order submission or execution
- — Guaranteed P&L, forecast accuracy, or trading uplift
- — Self-serve checkout, unscoped markets, and unlicensed raw feeds
Next step
Describe the one workflow you want to test.
Do not send credentials, API keys, or sensitive trading data. A market/zone, team role, and the decision you make today are enough.
We respond within 1 business day (Mon–Fri, 09:00–18:00 EET) and propose a short discovery call.
Leave a contact — we'll walk Alvo through your tasks (DAM/IDM, risk, BESS, or API) and answer your questions. The demo workspace is already open, but the live walkthrough we'll do together.