
BPM Auto
A full automotive presence built to turn vehicle discovery into real conversations — with tailored workflows behind the polished storefront.
- Web platform
- Automotive
- CMS
- Integrations
Mario AnghelIndependent software builder
Websites, internal tools, automations, dashboards and connected systems — designed around the way your business really works. Then kept running after launch.
01 / Selected work
Six public projects. Different industries, different problems, one pair of hands from idea to deployment.

A full automotive presence built to turn vehicle discovery into real conversations — with tailored workflows behind the polished storefront.

A product website, documentation hub and community home for a Minecraft mod that turns storage into a system of its own.

A warm multilingual travel platform that brings personal itineraries, stories and group experiences under one distinctive identity.

The operational layer for a roleplay community, connecting member accounts, Discord roles and administration workflows.

A control and automation layer for Tesla owners, built around voice commands, custom flows, OAuth and a practical REST API.

A focused financial workspace that helps Romanian independent professionals understand projections, obligations and what comes next.
This is the visible part. Much of the more complex work lives behind logins, private networks and company doors.
02 / Capabilities
I combine product thinking, interface design and engineering to make the whole thing work — not just the part visible in a browser.
The tools a team actually works inside every day.
Public-facing products with the machinery behind them.
Make the repetitive parts happen without the repetition.
Turn operational noise into information people can use.
The right people, in the right place, with the right permissions.
The ideas that sound slightly unreasonable until they work.
03 / Beyond the page
A website might be the part people see. The valuable bit is often the system underneath — moving data, enforcing access, triggering work and keeping the business informed.
One person understanding the whole system means fewer hand-offs, fewer translation gaps and a product that behaves like one product.
04 / The work behind the work
Some of the most complex systems never become portfolio links. They hold customer data, proprietary workflows, reporting logic and private integrations — exactly the things a business cannot casually put on display.
The six projects above show the range. They are not the ceiling.
BUCHAREST / RO05 / About Mario
My work sits somewhere between business, product thinking, software, automation and user experience.
Before deciding what to build, I want to understand how the business actually operates: who does what, where time gets lost, what keeps breaking, and what a good day should look like.
Sometimes the answer is a sharp, fast website. Sometimes it is a custom platform because forcing the work into generic software would create more problems than it solves. I'm comfortable with both.
06 / End-to-end ownership
You should not need to assemble a technical team just to keep your product alive. Tell me what needs to happen; I handle the machinery.
Find the real business problem before deciding what to build.
Shape the simplest system that solves it properly.
Frontend, backend, data and integrations — whatever the job needs.
Deploy it, test the actual workflow and remove the sharp edges.
Keep it healthy and improve it when the business moves.
07 / Start somewhere useful
You do not need to know the stack, architecture or technical terminology. Explain the problem. I'll help figure out the rest.