Soluntech - Conexis VMS

One set of records, six very different users

A contingent workforce programme puts a lot of hands on the same records: buyers (including self serve buyers) raise requisitions, staffing suppliers submit candidates, MSP coordinators run the programme, workers log time and expenses, and finance approves and pays. The front end had to give each of those roles its own view of the same contracts, timesheets and invoices, with the right fields and actions for that person and nothing more, without splitting the product into separate apps.

I owned the modules where the money moves: contracts, including turning an accepted submission into a contract with its rate, location and tax details; time and expense cards with line items, cost centre splits and attachments, usable on a phone; and buyer and supplier invoicing, linked back to time and expense. I also built the reporting screen and wrote much of the role permission matrix that decides what each user can see and do before a page loads.

The decision I'd defend: a thin layer of our own over Ant Design, so feature code never imported the component library directly, plus code generation templates for new list pages, services and their tests. It added some ceremony early on, but it kept list, detail and form screens consistent when the codebase moved into a monorepo midway through the project.

• 840+Commits to the web app, May to November 2023
• 6+User roles served by one front end, each with its own view and permissions
• 3Core financial modules owned: contracts, time and expense, invoicing