> There's a variant of going full stack where you eat your way gradually through the customer by doing all their hardest work for them.
One of my clients provisions front office applications for banks and the conversation has come up more than once regarding the client evolving into a bank themselves and building up operations around the capabilities of the product stack.
One good multi-regional partner and it could be a radically different animal. Providing software to one very big customer tends to be a lot simpler than providing it to 20+ smaller customers.
In my experience it depends on the nature of that client. A drawback to having a dominant client is that they have a lot more leverage in roadmap, prioritisation, and product fit. That can seriously impact the internal coherence and maintainability of the product. Too many bits of business logic lodges in weird places because the client didn't want to write custom behaviours, and no time to tidy it up because they're always demanding their next wishlist feature to be deployed yesterday.
The arrogance of this comment detracts from the kernel of good, which is that banks are very complicated and lots of the complication is regulatory and finance, not just software.
One of my clients provisions front office applications for banks and the conversation has come up more than once regarding the client evolving into a bank themselves and building up operations around the capabilities of the product stack.
One good multi-regional partner and it could be a radically different animal. Providing software to one very big customer tends to be a lot simpler than providing it to 20+ smaller customers.