To your main question: Any successful “dual license” OSS project I can use as template?
I would argue: There are successful examples, but you shouldn't use them as a template.
The right license(s) and strategy for your project are very specific to your project and community. I strongly encourage you to choose your licenses based on what seems appropriate in your case, rather than which ones have seen success with other projects.
(The SFOSC project I'm involved with for example decided the entire model doesn't align with it's principles)
Take for example MongoDB, which is arguably successful by several metrics.
Currently they dual license with their new SSPL as a copyleft license for which they offer commercial license alternatives as one aspect of their business model. (They also offer MongoDB as-a-service for example)
They created and switched to this license as a direct response to cloud providers making presumably large profits with their software and it sparked heated discussions whether given the new restrictions the license can even be considered a free and open source software license. However it has been part of the apparently required pressure for Google to negotiate a deal but also for Amazon to make another hard fork.
Even if your project is in the exact same boat of this cloud providers vs database vendors clash of the titans, you'll have to ask yourself if you really want to take the same approach as MongoDB or your community has different values and concerns.
Is there a standardised license that fits my use case?
Again, whether it fits your case is something you will need to decide with your community, but...
By definition, for dual-licensing you will want to select at least 2 software licenses. One for the OSS aspect, one as the commercial license you can buy.
Additionally you will need some type of Contributor Agreement and have all contributors sign it. Specifically to make sure all copyrights are held by a single legal entity, which is necessary to be able to change the license without infringing on the copyrights of your contributors.
For the OSS license, there may be fitting candidates among the copyleft or source available licenses.
For CAs you might look at Harmony agreements though I'm convinced there are more options out there.
And as talked about in the previous answer I'm not aware of any templates you can 'just use'.