How Leading Development Teams Simplify the Creative Feedback Cycle with Punchlist and Webflow

Melissa Southern

Fast design and development and a polished end result typically don’t go hand-in-hand. But Webflow is changing that. Webflow’s full-featured website builder makes it easy to launch a beautifully designed, highly flexible and customizable website faster than ever. It does so by generating code based on visual design edits — right in the browser. This no-code solution is changing the way teams collaborate and making the website design process more accessible than ever before. 

Now, Punchlist’s no-code feedback solution makes the design, development, and launch process even easier. Punchlist takes the frustration out of the creative feedback cycle, allowing you to annotate over live websites, landing pages, images, PDFs, and slides — no downloads or installations required.

With a new, direct integration between Webflow and Punchlist you can keep the feedback process right in your browser — no need to switch to email or create PDFs of your project. With just a few clicks, you can pull in specific pages or an entire Webflow site and have a custom URL ready to share to collect feedback. 

To better understand the impact of this new integration, we sat down with three Webflow + Punchlist users to hear what they have to say.

Keeping development feedback organized proves challenging

If you’ve ever tried to collect feedback from a group on web design and development you know it’s no easy task. From different team members reporting the same bugs over and over again to QA teams having difficulty replicating issues, the process is much harder than it needs to be.

Just ask Danielle Scherr. At Edgar Allen, project teams would collect feedback on Webflow projects through a form, but that meant clients would have to log in repeatedly and the process proved frustrating for clients and the Edgar Allen team alike.

“Clients would get really frustrated that they'd have to fill out the exact same form for every issue, because we had a lot of required fields. They would end up just filling out a Google spreadsheet instead, but that would leave our team without all the information we needed to properly identify the issue,” Scherr explains.

And it didn’t stop there. Duplicate bug reports and tracking progress created challenges internally for Edgar Allen. “We would always get duplicate bugs because people couldn’t see what their teammates were logging. Even if we asked one person to consolidate feedback, that never actually happened. And then our project managers would still have to log bugs and progress in a separate system, which just caused a lot of friction around visibility.”

Matt Johnson is no stranger to these types of challenges, either. In fact, he says feedback on Webflow projects at North of Eight Design was traditionally nothing more than a back-and-forth on Slack. “People would just dump comments into Slack and then I’d have to sift through those messages to make sure I got them all. And I usually didn’t,” he admits.

Searching for a solution to the chaos

The challenges of keeping web development feedback organized and visible to everyone who needs it are real. But it doesn’t have to be that way. And the search for something different has finally turned up a better solution.

After trying three different options for Virago Webflow Development over the course of a year, Jamie Dowis had almost given up hope. One solution was too buggy and not easy to share, another didn’t offer the ability to update statuses as complete or incomplete, and yet another just wasn’t a fit for the team. 

But then she found Punchlist, which checked all the boxes she was looking for and then some:

  • Quick to get started and easy to use
  • Sharing across collaborators made simple
  • Ability to track progress and update completion status
  • Options to annotate directly on a mockup
  • Detailed page and breakpoint organization
  • Integrations with top project management tools

“When I first saw Punchlist in action, I thought ‘this solves all my problems - take my money immediately,’” Dowis shares. And her team loved it right away too, noting how big of an improvement Punchlist has been for Webflow projects, especially thanks to its integration with ClickUp. 

Scherr and Johnson experienced similar excitement when they each found Punchlist through trusted recommendations.

Making feedback an integral part of the process – not a roadblock

Webflow makes launching new web development projects faster and easier than the alternatives. But disconnected feedback processes can prove a roadblock to that speed. Fortunately, that’s not the case anymore thanks to the Webflow and Punchlist integration.

With the Webflow and Punchlist integration, you can:

  • Create projects in 30 seconds and get a unique URL to share with reviewers
  • Empower stakeholders to leave feedback (upload missing files, indicate what to remove, provide content changes, etc.) directly on top of your live site or landing page, which shows exactly how everything will look, including animations
  • Enable developers to see exactly what should be changed, organized by breakpoint, and easily replicate the bugs users see
  • Keep all feedback in one location, meaning no more digging through email chains, Slack threads, or Google Docs
  • Automate the feedback process with scheduled reminders, feedback deadlines, and more

According to Scherr, using Punchlist with Webflow is worlds better than Edgar Allen’s previous approach because it simplifies the feedback process and saves everyone time.

“What we love about using Punchlist with Webflow is that everyone can see what bugs others are logging, so there’s no concern about duplicates. Plus, our developers love being able to see exactly what our clients see. Before, they couldn’t always replicate an issue, but now users can just put a pin in the Webflow page to mark exactly what they’re seeing and our team can view that in Punchlist,” she explains. “For us, this has unlocked so much time. We previously had a lot of back and forth with clients to get more details and it became like a game of broken telephone, but now with Punchlist and Webflow, it’s all right there. It’s a lot less friction and a lot less effort.”

Meanwhile, Johnson appreciates having one place to look for a full project history of edits and feedback along with a clear, organized visual of what that feedback references. “Now, I can just go into Punchlist and have the context I need to know exactly what the client is talking about. If someone just sends a Slack message, it can get confusing because there might be multiple instances of what they’re referencing and they can’t comment directly in Webflow. But now, with Punchlist and Webflow, they can leave a comment in the exact spot. Having that all organized visually in one place makes it easier to keep track of feedback so nothing gets lost.”

As Dowis concludes: “Adding Punchlist to Webflow has been huge for our workflow. The ability to update statuses gives us a lot of flexibility. Using Punchlist and Webflow together just makes sense.”