You are used to a different paradigm. The age of designing in photoshop is coming to an end, simply because of the responsive era and how clients want to see how their site works responsively before signing off. If you want to be able to just draw shapes and drag them around, you will likely have to hire a developer at some point.
I think one of the strength’s of Webflow is that it uses the same paradigm as you would for coding something. If you ever need to hand off your project to a developer, they will thank you for using Webflow.
I tired both Muse and Macaw. I actually built a site in muse for a paying client before being introduced to Webflow. It was a terrible mistake. It’s not responsive like Webflow, and I still had to go into the code to change some things and make some tweaks for custom forms and other php apps they had in the older site. After looking at Muse’s code and then looking at Webflow’s code, I realised why Webflow is so beloved.
I’ve also tried Macaw. It’s great for quickly drawing shapes and resizing them and moving them around with your mouse but it’s still nowhere close to Webflow with it’s functionality. If you want the same widgets Webflow has, or want to do transitions or interactions like webflow, you would need to code them in. So as a non-coder, it would be perhaps fine for making a mock-up, but then I might as well be mocking up in Photoshop.
The truth is photoshop had that trick back in the 90’s even, where you could draw a layout, slice it up and out put functioning HTML (table-based). Webflow, to me, is the closest you can get to making a real, modern, functional responsive website with a WYSIWYG. But you still have to learn the paradigm of how the web is constructed. Why people would use container’s and divs and what is margin and padding and the difference between positions: fixed/absolute/relative/auto, what is overflow, display options: block/inline, why you would need columns and a responsive grid, etc…
Understanding these concepts is fundamental to how a page is made. Any program that hides them from you is potentially going to have some serious flaws at some point in the workflow (eg. Muse).
Lastly, I realise you said you don’t have the time or inclination to learn to code. But if you are going to be building websites on a regular basis, it would benefit you greatly to know a little about it. I just started learning last week and it’s much easier to learn HTML/CSS than you would guess. I took the free trial on Treehouse and did the ‘How to Make a Website’ course and it took me like two days and now I understand more about the basics of how a website is coded and look at my webflow code and actually understand what is happening and why. Actually I found with the course, I was already familiar with a lot of coding concepts because I had been using webflow and learned the proper paradigm in the first place.
Sorry for the long reply. In the end you have to do your own research and make your own choices. I just think I had to speak up along with all the other people who have found they love Webflow for a reason.