Why Bombayworks replaced
Bugherd with Marker.io and Trello




Digital agency



Key Integration

The context

Jonas is the co-founder of Bombayworks, a digital agency with over 70 employees and offices in four cities worldwide - Mumbai, Malmö, Gothenburg, Stockholm. They became a Marker.io customer in 2015.

As a co-founder, Jonas started as Bombayworks’ first project manager but eventually moved into his new role as Head of Operations, where his job has been to make sure other project managers have the right tools and processes to be successful doing their jobs.

The challenge

As someone obsessed with his team's success, Jonas spends a fair amount of time looking around for new tools to improve his team collaboration. When he finds a solution that can make his team more productive, he signs up for it.

But as new clients and new team members got added all the time, it became a real hassle for project managers to stay on top of things. And for Jonas, who is responsible for employee and client onboarding, he had to create new users, new projects and new clients in all these different tools.

Information was all over the place! Tasks, issues, projects and users were all living in different tools, creating a ton of overhead and confusion for everybody

For example, designers and developers were told to look for new issues only in Bugherd, but then they would see contradicting tasks in Trello, or an urgent email from a client and they wouldn’t know what was more important.

After a developer missed an important client email, Jonas said enough! He knew that they needed a single source of truth where they could manage all projects, users, time logs, and issues in one single place. They settled on Trello.

Trello is now our source of truth.
I tell the team that if a task doesn’t exist in Trello, there is no need to do it! If you want to get something done, you must create a card in Trello.”
hull process before
hull process after

Switching from Bugherd

Before centralizing everything around Trello, Bugherd was the tool Bombayworks' team used to report and track issues. It was the first visual bug tracking tool they had adopted and it was a breakthrough for them. They were finally able to stop reporting bugs through forms!

But working with Bugherd and Trello in parallel turned out to be a real challenge.

We tried to work with Bugherd and Trello together but it was terrible.
For example, when we closed a card in Trello, a duplicate issue remained open in Bugherd and vice versa. I wasn't happy with that.”

Jonas started searching on Google for a bug tracker that worked with Trello and came across a blog post about how to turn Trello into a powerful bug tracker.

When he discovered Marker.io, Jonas realized they could ditch Bugherd all together.

“I was so happy when I found Marker.io because I realized that we didn't need an issue tracker after all.

We could use Marker.io with Trello, and stop paying for Bugherd.”

Jonas Rendahl, Partner and Project Management at Bombayworks

How does Bombayworks use Marker.io?

The team’s favorite thing about Marker.io is how deeply it integrates with Trello by allowing reporters to assign labels, team members and due dates without leaving the website. They also love how easy it is for new employees and clients to understand how it works!

QA testers

Testers: Once developers are done with a website, they hand the project over to the QA team who use Marker.io to report the first batch of visual bugs and issues. They also use Marker.io on Browserstack to test for cross-browser compatibility and responsive testing. The QA team loves that Marker.io grabs all the metadata from the Browserstack device and attaches it to the Trello card. Learn more about how Marker.io integrates with Browserstack.

Product managers

Project managers: After the QA team has gone through the testing phase, PMs use Marker.io to request changes that they know are important for the success of the client.


Designers: Then the design team jumps in to give their visual feedback before showing it to clients. They go over the website or webapp with trained eyes and make sure all modules, forms and visual effects behave like they want.


Developers: Developers tend to use Marker.io very little, yet they are the ones most positively impacted by having the other teams report issues through Marker.io. They especially love that all incoming Trello cards come with a clear screenshot, the source URL and metadata about the browser, operating system and screen specifications.


Clients: An increasing amount of clients have Trello accounts on their own which makes adoption of Marker.io even easier. When clients need to share feedback or request changes on their website, they use Marker.io to create a new detailed Trello card. Another positive effect of collaborating with clients via Trello is that it helps to create a transparent process with clients - avoiding the need to send project updates and reports. Clients can log into Trello and see how the project is moving along.

Final thought

When Bombayworks initially signed up for Marker.io, they were looking for an alternative to Bugherd that worked well with Trello. But as they started using Marker.io, it became clear that it was much more than an issue reporting tool. Today, Marker.io is their default tool to report issues, but also to create user manuals, onboarding guides or simply to explain something to colleagues and clients.

Marker.io is a Bugherd alternative that is easy to use for everyone on your software team or your clients and integrate with your current bug tracking tools.

Marker.io Bugherd
Is a bug reporting tool on its own

With Bugherd, you work and report issues in Bugherd.
With Marker.io, you work in Trello, Jira, etc. and report issues with Marker.io directly into your tools.

close check_circle
Create issues in your bug reporting tool (Trello, Jira, GitHub, etc.) check_circle close
Single source of truth

When you work with Bugherd and Trello (can also be all the bug reporting tool we integrate with), your developers always have to synchronize the tasks between Bugherd and your tool. By integrating deeply with your bug reporting tools, Marker.io allows your team to only check a single place to work.

check_circle close
Uncluttered UI check_circle close
Intuitive & easy to use check_circle close
Also integrates with Slack, etc… check_circle close
Can be used without asking an admin check_circle close
No file storage limits check_circle close
Easy to configure bug report template check_circle close
Save your screenshot for later use check_circle close
Report mobile app bugs check_circle close
Responsive customer support (avg. answer time: 5mins.) check_circle close

No script to install. Get started in seconds.


2. Connect your tool

Grant access to your existing tracking tool

first medal

3. Start reporting bugs & feedback

Capture, annotate and report issues in one click