Tsito

Loading0%

Back to home
Internal platformInternal tool

One portal, one sign-in, the whole firm

One Microsoft sign-in, a shared staff directory and the firm's internal apps, each one shipped and deployed on its own.

Role
Lead developer
Client
Accounting firm, Paris
Year
2026
Illustration redrawn for this site
people across the firm
100+
months from first commit to launch
4
code reviews on the team's pull requests
52

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 portal with single Microsoft sign-in and a directory synced from Microsoft 365
  • 02Apps for time tracking, evaluations, skills tests and client email follow-up
  • 03A monorepo where each app ships on its own, with shared UI and auth

Key decisions

One database per app

The first decision on record was a shared database. The next day a second one replaced it: each app owns its data and shares only through the portal's API. The price is written down too: if the portal is down, the apps refuse entry.

The portal stays off the critical path

The portal is not an identity provider: sign-in goes straight to Microsoft. Share the foundation, not the runtime.

Outcome

Launched to the whole firm in October 2026. The code lives in the firm's own GitHub organisation, with an onboarding guide and the written decisions for whoever takes over.