One system for a whole park
Worxspace is software for managing technology parks. A park is run by a team and seen by the outside world through its website, and those two sides usually live in separate tools that know nothing about each other.
Worxspace puts them in one system: a CRM for the people who run the park, the public websites, and a control module that manages both. We built it as a team of three, and I was responsible for the front end.
Companies, spaces, requests, money
The CRM holds the companies in the park, the commercial spaces they occupy, the service requests they raise and the accounting behind all of it.
Bank accounts connect through Salt Edge and invoices go out through Romania's national e-Factura system, so the books follow the park without anyone re-typing them. My job was to make that much data easy to work with on screen.
Many roles, one interface
No single screen was hard. The size was: many roles, many processes, and pages that all have to agree with each other. A request touches a company, a space and an invoice, and each role sees a different slice of it.
I kept the CRM on one typed codebase shared with the API, so the screens use the same types as the server and break at build time instead of in front of a user. Role-based access runs through every page, and each role gets only the sections and actions it needs.
Websites run from the same place
The public websites aren't a separate project. They're managed from the same control module as the CRM, so the team changes what the outside world sees in the same place they run the park.