Hexagonal architecture (ports and adapters): worth the complexity?

We're debating adopting hexagonal architecture (ports and adapters) for a new mid-size service our 5-person team is building. The idea of isolating business logic and making it framework-agnostic is appealing, especially for testability and future flexibility. However, it seems to introduce a significant amount of boilerplate with all the interfaces, DTOs, and adapters. Is the complexity truly worth it for a smaller team and a service that isn't expected to grow into an enterprise behemoth overnight? What are the practical benefits you've seen in real projects? Could anyone share examples of a lean project structure that still adheres to hexagonal principles without becoming overly verbose?