How Checkbox Saved a Week on Their Website Rebrand with Marker.io

Sara Wickström leads marketing at Checkbox, a survey software company based in Amsterdam. She spearheaded a complete website rebrand (new identity, new content, restructured pages).

When the new site hit staging and hundreds of bugs surfaced, she needed a fast, reliable way to get feedback to a remote developer without drowning in spreadsheets and Slack threads.

"We definitely wouldn't have made the deadline we had set out to do, and it would have been a much more complicated process."

‍

The challenge: hundreds of bugs, no system to track them

Checkbox was planning a full rebrand of their marketing website — new logos, colors, restructured pages, new content, images, CTA buttons, and forms. The project involved a marketer, a designer, a remote developer, and several other team members.

After three months of development, the new site was uploaded to staging. And that's when the real work began: hundreds of bugs and visual issues needed to be identified, described, and fixed before launch.

"When we came to the point that we were uploading the new version of the website to our staging environment, we realized that there are quite a few fixes that we need to do and bugs that we identified."

The team's first instinct was a spreadsheet: take screenshots, describe the problems, share the file. But they abandoned that idea before even starting.

"We were thinking about maybe just simply creating a spreadsheet where we would take screenshots and maybe describe the situation. But we didn't even start because we realized it would be just a bunch of back and forth communication and simply too time-consuming."

With a remote developer who wasn't in the same location as the rest of the team, clear and self-contained bug reports were essential. There was no option to just walk over and point at a screen.

The solution: annotate directly on the page, sync to Notion

The team skipped the spreadsheet entirely and went straight to Marker.io. They already had an account from a previous project, and getting started again took minutes.

"It was very simple and super fast. We downloaded the extension and then we also had it connected to Notion. So everything that we marked as bugs or any feedback — it was tracked in Notion."

Screenshots that speak for themselves

Instead of writing long descriptions of what was wrong and where, the team took annotated screenshots directly on the staging site. The visual context meant the developer could understand each issue immediately — no follow-up questions needed.

"Just being able to take a screenshot and then have it connected to the description of the problem: we had an extremely minimal back and forth communication because of this. You could really get a clear picture of what was needed."

AI rewrite for faster reporting

With hundreds of bugs to log, even writing descriptions became a bottleneck. The team used Marker.io's AI rewrite feature to quickly turn rough notes into clear, actionable descriptions.

"If you identify this many bugs, just writing down everything in a clear, cohesive way can take quite a lot of time. So it's nice to just brain dump what you want to say and then have the AI rewrite it."

Seamless Notion integration

Every issue captured in Marker.io automatically appeared in the team's shared Notion board. The developer working remotely could track which tasks were started, in progress, or finished, without anyone needing to send a message.

"In our Notion list, which was shared with our developer and the other team members, he could track which tasks he had started, which was in progress, and which was already finished."

Bug bash with zero training

Right before launch, the team ran a larger bug bash and brought in additional team members who had never used Marker.io before. Onboarding took minutes — just a short note on how to install the extension.

"Before the bug bash, I just sent out a minor description on what to do, to download the extension. And that process was also very easy."

The results

By replacing spreadsheets and Slack threads with Marker.io and Notion, Checkbox kept their rebrand on schedule:

• Saved at least a week on the overall project timeline
• Extremely minimal back-and-forth between the team and the remote developer
• Five core team members used Marker.io daily, with additional members onboarded for the bug bash in minutes
• Virtually eliminated Slack and email for bug communication
• Still using Marker.io weekly for ongoing site improvements after launch

"Probably we saved at least a week by using Marker.io. We definitely wouldn't have made the deadline, and it would have been a much more complicated process."

Even after the rebrand shipped, the team continues to use Marker.io for the small fixes and tweaks that come up every week — proof that a tool adopted for one project can become part of the permanent workflow.

"Ever since weekly we find some small minor detail that we want to change. So we do keep on using it even after the project is kind of finalized already."

‍