Internal platformInternal tool
An internal platform, from an empty repo
No code and no team on arrival. Today the whole firm signs in once and works in tools I designed, built and now maintain with a team I hired.
- Role
- Lead developer
- Client
- Accounting firm, Paris
- Year
- 2026
- people on the platform
- 100+
- sign-in for every app
- 1
- team built: hired and onboarded
- 0 → 5
Context
The firm ran on spreadsheets and a handful of SaaS tools that did not talk to each other. Every new need meant another subscription and another login.
What I built
- 01A hub with single Microsoft sign-in and a shared staff directory
- 02Apps for time tracking, evaluations, skills assessment, client-relationship quality and staff onboarding
- 03A monorepo where each app ships on its own, with shared UI and auth
Key decisions
One database per app
We tried a shared schema first. Apps now own their data and share only through the hub's API, so one app can change without breaking another.
Decisions written down
Architecture decision records for every structural choice, so the team I hired can read why, not just what.
Outcome
Used across the firm every day, maintained by a team I recruited and onboarded.