Automation built for humans, not dashboards.
Companies trust us to join their apps, tame their data, and hand back one to two working days per person every month.
Our Starting Point
Elemra started with a fairly simple frustration.
There has to be a better way than this.
I spent seven years automating processes inside organisations with tens of thousands of employees. The code usually worked. The systems mostly held up. What didn’t work was everything around them — politics, approval chains, change‑request forms, and layers of abstraction that turned simple fixes into multi‑month projects.
Good ideas stalled. Obvious improvements died in committee. And the people doing the actual work were rarely the ones deciding how it should be automated.
A Different Way of Working
Elemra began as a quiet reaction to that environment.
Smaller teams. Shorter feedback loops. Decisions made in days, not quarters. No vanity slides. No roadmaps designed to impress people who never touch the process being discussed.
If we can’t explain the fix to the person who actually does the task, we start again.
That rule still shapes everything we build. If an automation doesn’t make someone’s working day easier, it isn’t finished.
How We Think About AI & Automation
Automation isn't about replacing judgement. It's about supporting it.
Machines are good at consistency, repetition, and moving information between systems. Humans are good at deciding what matters, handling edge cases, and taking responsibility when things aren't clear.
In practice, that means connecting tools and data one step at a time — app by app, decision by decision — until the system actually holds together.
Adding AI to a broken process usually just makes the breakage harder to see.
We design systems where roles are explicit. Humans decide. Machines execute. Never the other way round.
Our Team
Elemra is intentionally small.
We’re three full‑time project managers who oversee the end-to-end production of your project.
- One spent 20 years in video and content production, architecting workflows and systems for international organisations with thousands.
- The other is a former advertising exec who's built and scaled multiple companies
- And one is a seasoned product manager who's led research and development across multiple global organisations
We work directly with a pool of specialist product managers and devs hired on a case-by-case basis depending on the unique requirements of your project. But what you see is what you get. They're are no project hand‑offs.
You talk directly to the people who manage your project from initial audit and discovery, through to the build, QA, delivery, and training.
Fabio Basone
Oliver Hunt
Astrid Thorseth
How We Work
We’re selective by design.
At any given time, we work on a maximum of three client projects. Any more than that and quality slips — and we’re not interested in shipping half‑understood systems.
Everything we build lives in your accounts, using tools you already trust where possible. You keep the keys. You're never locked into us.
If the return doesn’t stack up, we’ll tell you before you commit.
Before any work starts, we do the honest maths. Cost per minute saved. Where the gains actually come from. If it doesn't make commercial sense, we don't recommend it.
What We Care About
- Honest maths — clear ROI, no hand‑waving
- Ownership — your systems, your data, your access
- Clarity — if it can’t be explained simply, it’s probably wrong
- Restraint — not everything should be automated
- Respect for people — work should feel lighter, not more complicated
If you can explain a task clearly enough for someone else to do it, you can usually automate it. If you can’t, that’s where the real work starts.