Eliminating setbacks and surprises at Netguru

How the Poland-based agency uses Slack to keep customers coming back

Author: Lima Al-AzzehFebruary 2nd, 2017

Hiring an agency often leads to a steady stream of back and forth communication. There are initial meetings to define project needs and, from there, a litany of calls and meetings to discuss ongoing project developments. The most minor of misunderstandings between customers and their agency partners could set a project back significantly, costing both sides a lot.

Netguru, a software development consultancy based in Poland, pride themselves on being masters of efficiency. It’s especially important when developing up to 60 concurrent projects with an international customer base and, behind the scenes, coordinating this work across a 200-person team of developers, project managers, designers, and account managers working from homes and offices all over the country.

In their ongoing quest for a tool that would streamline their workflows and communications, last year they decided to give Slack a try.

Marek Talarczyk

“We’ve been able to wrap pretty much all of our processes, including our customer communications, into Slack,”

Marek TalarczykHead of delivery, Netguru

Organizing principles: A channel for every process

Being rigorous about processes helps Netguru deliver high quality projects on time and on budget. To make everything run smoothly, head of delivery Marek Talarczyk and his team have organized their Slack workspace to reflect all major aspects of their business operations.

With team and customer communications organized into clearly labeled channels, all team members can easily find the information they need to do their work — whether that comes in the form of notifications from apps and services used to build projects or channels set up to quickly receive direct responses from customers.

Their Slack workspace tends to be organized around three central workflows:

  • Project channels (#projectteam-projectname): These are public channels containing a given project’s team of developers, designers, and project managers working together to iron out technical details and communicating on a daily basis to make sure everyone has a mutual understanding of what needs to be done.
  • Customer channels (#clientname-projectname): Customers are invited to channels as single-channel guests, to protect their privacy and as a single point of contact with their project’s team. If team members had any doubts or questions about particular features, they just consult the customer directly in this shared channel.
  • Business development channels (#bizteam-projectname): One thing Talarczyk has found especially helpful is creating a second customer-related channel in Slack that gathers the development team with account managers so they can discuss strategies for customer success and overall customer satisfaction.

To top it all off, there’s a mix of channels to discuss day-to-day business operations, including private channels for conversations around recruitment and even channels spun up to brainstorm and discuss new processes with stakeholders before they’re rolled out to the rest of the team.

Uniting technical teams and their tools

Direct communications with customers is one way Netguru team members speed up feedback cycles. For Jakub Niechciał, a senior developer and team leader, the technical teams under his purview frequently rely on updates from another source: Slack integrations.

Integrations pull notifications from Netguru’s various applications (like Jira, Confluence, and Pager Duty, to name a few) and act aserror assessment feeds,” as Niechcial describes it. These notifications alert the whole team of server issues that could affect a project’s, or several projects’, development.

“What’s even more useful is that we can basically resolve or accept technical issues right within Slack, just by clicking a button,” explains Niechcial. “And because these integrations are in public channels where all team members are, it’s an immediate indication that someone is taking ownership of the issue.”

The combined effect of these measures is not lost on Talarczyk: “Integrations probably save us each at least five minutes a day per person. When you add that all up, it means we’re saving weeks, and even months, of time spent on projects across the whole organization.”

Jakub Niechcial

“What’s even more useful is that we can basically resolve or accept technical issues right within Slack, just by clicking a button.”

Jakub NiechciałSenior developer, Netguru

On the road to repeat and referral customers

As Head of Delivery, Talarczyk is in the unique position of overseeing quality at Netguru from two perspectives—delivering high caliber products and providing a seamless experience for customers.

“We’ve found that using Slack with customers early on in the process helps tighten our bond and build a better relationship with them,” he explains. “Now a lot of our business comes from existing customers and we’re finding this leads to an increase in new referral customers, too.”


Was this post useful?



Thanks so much for your feedback!

Got it!

Thanks for your feedback.

Oops! We're having trouble. Please try again later!