Ekkinox

Custom business tool for construction-site financial tracking, started as an internal Patriarche product then turned into a white-label version with a SaaS path ahead. Senior front-end and front lead for 18 months — team of 2 front, 2 back, 1 PM, 1 designer.

We started out wanting a modular setup, but the domain is too interconnected for that: we went with a domain-oriented organization structured around interfaces — a split that follows the UX designer's mental model and real user flows. Business workshops for every feature, fast iterations, regular client demos: we adjusted often, sometimes heavily, but without losing the overall coherence.

• Domain-oriented front-end architecture built to last 18 months of delivery — split by interfaces aligned with UX flows, not by file type (no components/utils/views folder that grows without holding).
• Tailor-made business views: financial tables, custom behaviors per module, in-house design system built alongside the product to stay coherent as features piled up.
• Recurring user workshops and client demos at every milestone — learning construction-site finance on the job became part of the role, not a side concern.

Vue + TypeScript and Pinia on the front, in-house design system built in parallel with the product. NestJS on the back — full-TS end to end. Front-end architecture was the structuring topic: a strict domain split wouldn't have held (everything is linked), so we went for an interface-based split that maps to the business and actual usage.

18 months on the project, from day one through the move to a white-label version, with a front-end architecture that never had to be rewritten along the way. On a personal level, this is my first real front-lead role over the long haul — a chance to lay foundations that hold, challenge the PM when it mattered, and learn a domain (construction-site finance) deep enough to discuss with users without hand-waving.