Mario AnghelIndependent software builder

I build the softwareyour businessactually needs.

Websites, internal tools, automations, dashboards and connected systems — designed around the way your business really works. Then kept running after launch.

Currently building
Business platformsConnected automationsUseful internal tools
LIVE ARCHITECTURESYSTEM ONLINE
MARIOBUILDS ITWEBSITEAUTHCRMEMAIL / SMSDATABASEDASHBOARD
Scroll to inspect

01 / Selected work

A few things I can actually show you.

Six public projects. Different industries, different problems, one pair of hands from idea to deployment.

PUBLIC WORK / 06

This is the visible part. Much of the more complex work lives behind logins, private networks and company doors.

02 / Capabilities

Built around the problem.
Not a fixed menu of services.

I combine product thinking, interface design and engineering to make the whole thing work — not just the part visible in a browser.

01

Business systems

The tools a team actually works inside every day.

  • CRM platforms
  • Internal tools
  • Admin portals
  • Role-based workflows
02

Websites & platforms

Public-facing products with the machinery behind them.

  • Business websites
  • Content platforms
  • Custom CMS
  • SEO foundations
03

Automation & APIs

Make the repetitive parts happen without the repetition.

  • Custom APIs
  • Third-party integrations
  • Webhooks
  • Email & SMS flows
04

Data & finance

Turn operational noise into information people can use.

  • Dashboards
  • Reporting systems
  • Data visualisation
  • Financial tools
05

Security & access

The right people, in the right place, with the right permissions.

  • Authentication
  • OAuth & 2FA
  • Permissions
  • Signing workflows
06

Useful oddities

The ideas that sound slightly unreasonable until they work.

  • Gaming tools
  • Minecraft projects
  • Smart-home systems
  • Experiments

03 / Beyond the page

I don't only build websites.

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.

SYSTEM / FULL VIEWALL LAYERS CONNECTED
FRONTENDAPIAUTHDATABASEAUTOMATIONEMAIL / SMSADMINANALYTICS
Public interface Business logic Infrastructure
PRIVATE / CONFIDENTIAL / INTERNAL

04 / The work behind the work

The interesting stuff isn't always public.

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.

Portrait of Mario AnghelBUCHAREST / RO
Builder, not a middleman.Direct from first conversation to production.

05 / About Mario

I like building things that solve real problems.

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.

Mario builds it. Mario maintains it. You talk directly to Mario.

06 / End-to-end ownership

Built. Deployed. Maintained.

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.

01Understand
02Design
03Build
04Launch
05Maintain

I can keep it running, too.

  • +Hosting & deployments
  • +Domains & infrastructure
  • +Databases & backups
  • +Monitoring & updates
  • +Bug fixes & improvements
  • +New features & integrations
01

Understand

Find the real business problem before deciding what to build.

02

Design

Shape the simplest system that solves it properly.

03

Build

Frontend, backend, data and integrations — whatever the job needs.

04

Launch

Deploy it, test the actual workflow and remove the sharp edges.

05

Maintain

Keep it healthy and improve it when the business moves.

07 / Start somewhere useful

Have something in mind?
Tell me what it needs to do.

You do not need to know the stack, architecture or technical terminology. Explain the problem. I'll help figure out the rest.

No technical vocabulary required.