Minsait (Indra)
Enterprise web apps, owned end-to-end — from the client to production.
Built web applications for contract management, progress control and billing — from requirements gathering with the client through design, development and final validation.
Clients and internal product names are anonymized.
-
Contract management & billing platform
Web applications for enterprise clients covering the contract lifecycle, progress control and billing — a domain with intricate, frequently-changing business rules.
-
Document automation & e-signature
Generated contractual documents and wired up digital-signature flows so paperwork moved through the system without leaving it.
- .NET
- Document generation
- e-signature APIs
-
Delivery pipelines
Designed and maintained CI/CD pipelines so releases were repeatable and low-drama, under a SCRUM cadence.
The kind of stories an interviewer asks for.
- Complex domain · clean architecture Challenge
Contract and billing rules were complex and kept evolving — the kind of domain where naive code rots fast.
ApproachModeled it with DDD and a CQRS + MediatR structure, keeping the domain explicit and the read/write paths separable.
ImpactA codebase that stayed maintainable as requirements shifted, and that new rules could land in without fear.
- Ambiguous requirements · client communication Challenge
Requirements often arrived fuzzy, and a gap between what the client meant and what got built meant costly rework.
ApproachWorked directly with the client through requirements gathering, functional analysis and final validation, closing the loop before code shipped.
ImpactFewer reworks and a tighter fit between delivered software and what the client actually needed.
Minsait is where I grew from doing coding tasks to owning the technical side — design, client conversations, process. The architecture patterns I picked up here (DDD, CQRS, MediatR) still shape how I reason about non-trivial domains today.