Back to resources

Effective Collaboration Between Engineering and Sales

Alignment
Sharing The Vision
Team Processes
Cross-Functional Collaboration

21 July, 2021

Sebastien Cuendet
Sebastien Cuendet

Sr. Director of Engineering at AppFolio

Sebastien Cuendet, Senior Director of Engineering at AppFolio, relieved interdepartmental tension by bringing his Engineering team together with Sales in order to see things from their point of view.

Problem

We were trying to enter a new market for which our product wasn’t a good fit yet. Sales had a hard time getting prospects to sign up for our product because of some key missing features. They wanted us to develop those features, but our product organization was reluctant to blindly develop features for prospects for fear of ending up with a string of custom solutions that would grow unmanageable.

The high-level problem between Engineering and Sales was that Sales is very short-term driven. There are quarterly quotas to hit. The feature that seems the most needed is the one that the current prospect is missing. Product development is long-term focused: you need to really understand the pain of customers and solve it in a way that will satisfy most of them.

There is a general distrust between Sales and Engineering for this reason. Usually, you have the product manager sitting in the middle as the messenger. In this example, our product managers were saying “No” to Sales a lot, and the Sales team was getting frustrated. We were having a hard time as a new company penetrating this new market.

It was a catch-22; when you’re developing a product, you need to talk to the people who need your product so that you understand their needs. This is hard to do when you don’t have any customers yet. Once you actually have a customer, you can talk to them and understand their pains. In our case, Sales people were the ones speaking to our prospects.

Actions taken

We were asked to work directly with Sales because our product was not up to par according to what they were feeling at the time. There was a general fear on the Engineering side that the partnership would result in hard deadlines, ad hoc additions, and drama. Sometimes, Sales sees Engineering only as a feature-building entity. Just do what the customer wants. This is a completely uninspiring way to work from an Engineer’s perspective. It can be limiting; you’re not really creating something new.

We decided to organize a half-day workshop early that January with the Sales team. The goal was to get to know each other (Sales and Engineering don’t interact together very often!); to create the foundation for our collaboration. I asked the Sales leader to come to the workshop with the main missing features in our product. I insisted on having them phrased as problems and not solutions. Why were we not capable of selling in this market? They came up with eight of them.

After some introduction and ice-breaking, we split up into smaller groups, one Sales person with two or three Engineers. Each Sales person explained to their group what the problem was that our product wasn’t solving and why it was important to solve it. Engineers love solving problems and started to engage with the problems and to brainstorm solutions with the Sales person.

This was eye-opening, for both the Engineers and the Sales team. The Sales team realized that Engineers were able to come up with creative solutions that were better than what they had originally imagined themselves. The Engineers were happy to see that their colleagues in Sales knew a lot about the customer and that the problems that they wanted solved made a lot of sense.

Following this workshop, we had the chance to join the Sales team as they spoke to our prospects in the market. As Engineers, we learned a lot about the business side of things and the users that we were trying to serve. It was a completely different mindset. We brought both of our worlds closer together.

Lessons learned

  • This half day that we spent together changed a lot in the perception that we had of each other. It wasn’t all rosy after that, but I think that was a turning point. We were no longer overwhelmed by too many unimportant “priorities”. The partnership became much more fruitful as a result and we had some great wins together.
  • Keep an open mind with people. This exercise helped us build trust and respect with Sales. It can be difficult to build these types of relationships with people following different codes of conduct in regard to the work. It became the foundation of a more functional relationship. I personally learned a lot about our business and sales, and have built lasting relationships with our Sales leaders.
  • When Sales wanted new features, we would hold meetings to determine what would be possible and useful, and what may be better to say no to. This gave us a chance to explain why some things were easier to add to the product than others. We were able to show them those trade-offs.
  • It is invaluable for Engineers to be involved with understanding the other parts of the business outside of the Engineering department, including the needs of the customer.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

Coaching Women Engineers: Professionally, and for Life

20 January

Yang Wang, Engineering Manager at Bond, shares how she coached several women engineers in her team to boost confidence and help them grow in their careers.

Coaching / Training / Mentorship
Team Processes
Career Path
Yang Wang

Yang Wang

Engineering Manager at Bond

How to Build and Manage the First Product Roadmap for a Startup

19 January

Angel Jamie, Chief Product Officer at Yayzy, shares how he created the first product roadmap at a startup, and a simple process to keep it alive.

Alignment
Product
Meetings
Roadmap
Prioritization
Angel Jaime

Angel Jaime

CPO at yayzy

From Big Tech to Startup: Adding Value From Day 1

19 January

Angel Jamie, Chief Product Officer at Yayzy, recalls his transition from a well-established tech company to a sustainability startup, and the major differences he experienced.

Dev Processes
Company Culture
Impact
Team Processes
Cross-Functional Collaboration
Changing Company
Career Path
Performance
Angel Jaime

Angel Jaime

CPO at yayzy

Should You Stay Up to Date with Technical Skills As a Product Manager?

19 January

Nani Nitinavakorn, the Sr Product Owner at Revolut, describes how she keeps learning hard skills to increase motivation and respect her team.

Alignment
Innovation / Experiment
Different Skillsets
Personal Growth
Ownership
Coaching / Training / Mentorship
New PM
New Manager
Nani Nitinavakorn

Nani Nitinavakorn

Sr Product Owner at Revolut

What to Do When Candidates Turn Down Your Job Offer

18 January

Rachit Lohani, Head of Engineering at Atlassian, decodes the positive changes he made to the company's recruitment process by getting into the crux of the issue.

Mission / Vision / Charter
Sharing The Vision
Strategy
Team Processes
Rachit Lohani

Rachit Lohani

Head of Engineering at Atlassian

You're a great engineer.
Become a great engineering leader.

Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.