Most business processes have a step in the middle where somebody reads something, works out what it means, and decides what happens next: an order email that has to become an ERP record, for instance. A language model can do that step now, so the whole process can run without a person in it. We build those systems. The work is mostly in making them dependable enough to leave running.

A web platform is the product your customers use and everything it needs to keep working: the application, content somebody has to be able to change without a deployment, the payments, and the place it all runs. Those four usually get built at different times by different people, so most of the job is getting them to work together.

Sometimes a team is building well and needs more senior hands. Sometimes there’s nobody whose job it is to decide what gets built, because the CTO left and the replacement is months away. We do both, and they’re different jobs. Engineers who join your team work to your plan; an interim technical lead owns the plan and hands it back when the permanent hire arrives.

Identity means who’s logging in, and most companies get that from a provider like Keycloak or Auth0. Access means what they’re allowed to do once they’re in, and most companies build that themselves. Both stop fitting as a company grows: you change providers, a big customer arrives expecting to sign in with its own accounts, and a short list of roles stops describing who should see what.