I consider my process a one way street, no matter what. I've been where you are, and its just simply not worth it at this time to be jumping back and forth between all the tools. I try to be as up front with my clients as possible - painting a really clear VISUAL picture of the process, and I make it very clear that we'll get approval from them before moving to the next steps. Doesn't mean changes can't happen - I like to say at certain points that we're working with sand, not concrete. But at some point, the concrete will harden and changes will be harder to make the further down the pipeline we go. Having this open, informal conversation is important.
When the rubber hits the road and you actually have to set your foot down...that's where things likely start to not feel fun but you have to remind yourself that you have a process for a reason. It should not be walked all over. YOU have to trust the process, and so do your clients.
That said, tactically, if a new page comes up, I just make that change right in Webflow. If I need to create a design first, I'll go into Figma, design it, get approval, then go to webflow. Rarely do I go back into Relume to add the page to the sitemap, generate a wireframe, etc. I guess this is where AI will likely never replace designers. And if you are super reliant on AI to do this kind of work, I would strongly encourage you to dive into some Figma/Webflow resources to help with this pain point.
If you wanted to have posterity across all of those tools, I suppose you could add the new page to the sitemap and generate a wireframe, make your edits and what not but syncing those changes into Figma or Webflow likely won't be a great idea. I typically just copy/paste those individual pages into Figma/Webflow.
But 99% of the time, I'm just using what I've already built within Webflow and creating that page directly in Webflow. Can grab components directly from the chrome extension so I never have to leave Webflow.
