Deals Service
By late 2024, the Enty platform comprised distinct functional modules: Contracts, Invoicing, and Counterparties operated as isolated silos. Users were forced to constantly switch contexts to manage a single business transaction.
The business objective was to launch Deals β a unified hub where all artifacts (documents, bills, counterparty data, and external files) are aggregated within the context of a single deal.
π¨βπ» Role: Hands-on Tech Lead
I acted as a "playing coach," combining leadership with core engineering. My goal was to architect the system in a way that allowed junior developers to contribute safely and in parallel, without compromising code quality.
𧩠Architecture & Process
To mitigate the risks of a tight deadline and team inexperience, I implemented a "Skeleton & Slots" strategy:
- Core Implementation: I personally built the API layer and the frontend scaffolding. I defined the data contracts and the UI structural layout.
- Modular Development: I carved the application into isolated "blocks" (slots). Developers were assigned specific components to fill into these slots, ensuring separation of concerns.
- Epic Branching: We worked in a dedicated integration branch where I performed daily code reviews and merged the blocks.
In the final phase, I performed a unification sprint, refactoring and polishing the integrated components to ensure a consistent codebase before the release.
π Results
- Delivery: Thanks to the architectural scaffolding and process isolation, we delivered the project ahead of schedule.
- Product: Users gained a "Single Pane of Glass" dashboard for deal management, featuring a new Dropbox-like file storage capability.
- Quality: The "Skeleton" approach allowed juniors to be productive immediately while maintaining senior-level architectural integrity.
