If you like using page types to represent various content elements (I do), you might like the approach of defining more of your page's content as child content. This would allow you to query all the content for your page with one Hierarchical Viewer -- that is, with one database round trip. And in the case of your buttons, it would allow you to rearrange the buttons and the rest of your content by changing the node order in the content tree. If you adopt this approach, the nodes for one page might look like this:
∟Call to Action 1
∟Call to Action 2
I learned this approach from Brenden Kehren here, and Joel Dahlin here. Kentico Support guided a coworker to use the same approach, saying it "will also fall in line with our best practices."
Here's a slide deck that gives some more benefits and tips for this approach.