Multi-role Professional Platform

I led the project team while contributing hands-on to the design of the business workflows, the UX/UI and the full-stack development of the platform, including role-based experiences, confidential document handling, real-time updates and scheduling.

The platform brings together consultations, appointments, written deliverables, documents, fees and payments. These activities are closely connected, but they are not viewed or handled in the same way by everyone involved.

I used the case file as the central organising unit. Conversations, dates, documents, financial actions and professional work all connect back to it, while permissions determine what each person can see and do.

I like to start from the people rather than the screens: understanding how each role works day to day, in their own words, and turning that into clear workflows before drawing any interface.

I took part in the design of those workflows and of the UX/UI, then built the product end to end: interface, API, database, real-time layer, e-mail notifications and generated PDF documents.

The platform is bilingual, so every label, message and notification had to work for different audiences from day one.

One case file, several views: I structured the product around a shared case file, then adapted its information and actions to each role and permission level.

Plain language first: The intake starts with an everyday situation or a description in the user’s own words, rather than requiring specialist terminology.

Visible next steps: Statuses, deadlines and pending actions make long processes easier to scan without flattening their complexity.

Scoped collaboration: Delegation is attached to a specific task, preserving both confidentiality and traceability.

A product like this holds sensitive documents and money, so a large part of the work happens where users never look: who can open what, what happens when two people act at the same moment, and how the system recovers when something fails.

After the first version, I ran a systematic hardening campaign: dozens of written audit rounds covering access rules, data integrity, concurrency, input validation, file handling and monitoring. Each round ended with documented findings, fixes and automated tests, so the next person can see not only how things work but why.

Product interface: Vue 3, TypeScript, Pinia, PrimeVue, Vue I18n, FullCalendar and Socket.IO.

Application architecture: Node.js, Express, TypeScript, PostgreSQL, Drizzle, Firebase Auth & Storage and shared domain rules used by the frontend and backend.

Security & reliability: Case-level access control, runtime validation, MFA flows, file validation, antivirus scanning, monitoring and automated tests.

Business workflows: Structured states, scheduling rules, real-time updates and generated documents support case files as they progress over time.

I did not know my client’s profession. I had to learn its concepts, its vocabulary and the way its professionals really work, and I found it fascinating: diving into a new world is one of the things I enjoy most about my job.

I am convinced that observing and understanding come before designing. Interfaces and business workflows only bring real value when they rest on a genuine grasp of the field, so I ask questions, listen and keep learning until the logic of the work is clear to me.

I explain my technical choices in plain words, write decisions down, and leave a project documented (set-up, deployment, maintenance) so a team can pick it up without me.

If you are building a platform for a field with its own rules, several kinds of users or a lot of invisible complexity, I would love to hear about it.