Commodities · Switzerland
Automation built by people who have traded.
Eli5a helps commodity trading and analytics teams in Switzerland and beyond turn manual work and scattered data into systems that run reliably. Start with the problem.
What we do
Practical data, automation and AI for trading teams.
We work with your desk, analytics or operations team to agree the problem, the output and the limits. Then we build it with your people involved where it matters.
Trading data and analytics
Reliable data flows, quality checks and dashboards for traders and analysts, built with tools such as Python and KDB.
Workflow automation
Take repetitive reporting, reconciliation and desk tasks off people's plates with scripts, scheduled jobs and integrations.
AI adoption for commodity teams
Where AI helps, where it does not, and how to roll it out safely inside a trading business. Scoped pilots with people in the loop.
Why Eli5a
Trading-side experience
Years on a proprietary trading desk, including algorithmic energy market making.
Built inside commodity tech
Hands-on data, analytics and AI work inside a Series B, $40M+ funded commodity intelligence company.
Based in Switzerland. We know the local market and work with Swiss trading and analytics teams in person or remotely.
How we work
1. Agree the problem
One conversation to define the question, the data involved and what a good result looks like.
2. Run a small pilot
A scoped first version you can test on real work before committing further.
3. Hand over properly
Documented, reviewed by a person, and owned by your team.
Before we start
Do you give trading or investment advice?
No. We build tools and analysis. We do not give trading or investment advice, and we do not trade for clients.
Can you work with our data and vendors?
Usually. Bring the tools, data sources and approvals involved and we discuss what fits before agreeing the build.
Will you replace our team?
No. The aim is to remove repetitive work and give your people better tools, with a person making the decisions.
How do we start?
A short paragraph about the problem is enough. We reply to say whether a scoping conversation makes sense.
Start with the problem.
Discuss a project ↗