The Pull Request Nobody Wants to Write You know the one. It sits in the backlog for three sprints. The ticket title is something like "Kentico version compatibility investigation" and every time it surfaces in standup, someone says "we'll get to it this sprint" and then you don't. Because getting to it means opening a conversation about the $80,000 renewal invoice, the custom C# modules that only one person on the team understands, and the fact that your marketing team has filed fourteen Jira tickets this quarter asking for content changes that should take twenty minutes but take three days because everything in Kentico requires a developer to touch it. This is the state of Kentico in 2026 for a large number of engineering teams. Not broken. Not catastrophic. Just quietly expensive, quietly slow, and quietly eating capacity that your roadmap cannot afford to lose. Kentico Xperience 13 reaches end-of-support in 2026. The upgrade path to Xperience by Kentico is not a version bump. It is a reimplementation.…