Our Top 3 Principles to Effective Sales & Engineering Alignment
Tags: engineering, strapi, sales, cms
Published: 2021-08-25 17:02:28

I was hired by Strapi in November 2020 to join as the first salesperson. And it was quite a challenge! First of all, even though I had acquired technical knowledge through past experiences, I didn't know a thing about CMSes. And a headless one, even less! ;)

One of the reasons why I accepted their offer was for the opportunity to build a Sales Team from scratch. That being said, within a company mostly made up of developers, it could have been a cause for concern:

- Are these salespeople going to oversell the product by promising features that aren't there?
- Are they going to put pressure on the engineering team for specific development work?
- Are they going to ask us to come to all their clients' meetings to cover all the technical aspects?
- ...

![https://media.giphy.com/media/t5XqW33a9VYSQ/giphy.gif](https://media.giphy.com/media/t5XqW33a9VYSQ/giphy.gif)

And that's completely normal. Software engineers traditionally do not like salespeople. The article ["How Technical BDRs Can Play A Key Role"](https://www.decibel.vc/content/selling-to-developers-why-and-how-technical-bdrs-can-play-a-key-role) from Decibel VC also gives additional insights on this topic and I personally am really aligned with their vision.

However, Sales & Engineers can be the best of buddies, and here are our top 3 principles for an effective alignment. 

## 1. **Learn, continuously**

There is one thing I always enjoyed: spending time with the tech team *(and ask countless "Why?" questions)*, spending "a day in the life" with consultants *(even if it meant traveling to Morlaix with [Thomas Laporte](https://www.linkedin.com/in/laportethomas), an ex-colleague)*, participating in technical training *(I've always asked my managers for free time to attend)*, testing my skills with practice tests (*52% is my latest score at GCP Certified Professional - Cloud Architect)...*

And, most of all, **being hands-on**: having a sandbox where I can play! *Lesson learnt: do not forget to shut down the managed Hadoop cluster, otherwise you'll receive an email from your CTO in the early morning, true story!)*

<iframe src="https://giphy.com/embed/4Zgy9QqzWU8C3ugvCa" width="256" height="480" frameBorder="0" class="giphy-embed" allowFullScreen></iframe><p><a href="https://giphy.com/gifs/wikitude-augmented-reality-penguin-linux-4Zgy9QqzWU8C3ugvCa"></a></p>

This sort of behavior is fundamental in order to legitimize your recommendations and succeed in convincing your customers to adopt your solution. Selling is not the end game. It should only be the result of your efforts to position yourself as a trusted advisor and as a product specialist rather than a "sharp knife".

## 2. **Being grateful, unrelentingly**

Gratefulness comes mostly from two things:

First of all, **Respect the product**: developers have their own way of building a product and after shadowing a few kick-off / stand-up meetings, I can assure you that their backlogs never get empty. Compromises are made according to the right value they need to deliver at a specific time, so it's also the salesperson's responsibility to understand these trade-offs, to commit to the choices made, and support the decisions in front of prospects/customers.

For the record, when we launched the Content Internationalization feature, my first reflex was to think: *"A language is only a variation of a content... So we could trick that feature to create custom/fictive languages in order to build workarounds for features such as A/B testing!"* Yeah, but no. As a salesperson, you should always have the reflex of being creative and solution-oriented, but then never forget to submit your ideas to the Product Team so they can verify them from a technical perspective. **TL/DR: it wasn't a good idea ;)**

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/3jgtdxve883ju8zkisj3.png)

another example ;)

> Hey Devs, just wanted to say that if I love doing my job every day, it's because I love the product I sell!

Secondly, **the Time**. I'd like to give a huge shoutout to all the devs who take the time to explain the product to us salespeople. Most of us aren't good at reading documentation, watching tutorials, or even looking at Stack Overflow threads. We even struggle when filling out the information in the CRM, how do you expect us to do that?! *(I'm joking, ofc).*

I often do quick sessions with my buddy, [Maxime Castres](https://www.linkedin.com/in/maxime-castres-2420a9142/), Growth Hacker, who guides me on how to get into a terminal, how to install a JSON viewer add-on, how to do simple GraphQL queries... Every time, it's a small victory. Every one of those moments is much more valuable to me than signing a deal. Every additional piece of technical knowledge I acquire thanks to developers is one more step to enhance the closing rate of my deals' pipeline. 

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/grb001d6t0wxbsuim5t2.png)

Software Engineers tend to not be the most demonstrative people *(but it's nothing compared to my bunny* 🐰 👇 *, he really doesn't care at all),* 

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/8jijtui6e87ttsr42gkf.png)

But please be aware that every person working in a Sales position has a bit of an ego. That's a positive thing! Showing gratefulness to your Sales teammates is the greatest compliment they could ever receive. It's like the ultimate approval from your *Sensei*.

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/xgoe8vupkypkanv2ocdw.png)

## 3. **Share, a lot**

My teammates spend an incalculable amount of time building an awesome product and they rarely get the chance to see how the community actually uses it to solve so many problems. And when you're an awesome person building an awesome product, you should expect awesome outcomes.

That's why salespeople should always take the time to share a few sentences, a screenshot, a comment... or whatever it is that gives Developers a real idea of the final usage of the product. We're sharing more than feedback here. It's about transmitting daily inspiration and positive vibes to other people. It's like being a route to the API config. 🤓

At Strapi, we consider feedback a gift, and the #feedback Slack channel has at least one message per day. 

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/zizpyuqp4c4ha0f6yd63.png)


![Alt Text](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/0zljuoatn6pe8snuij4v.png)

Still, field experience feedback can hardly be considered actionable since it doesn't rely on exact data, which is a requirement for product-decision making. If you ever feel that way, always remember that it's not just about giving precious insights, it's about creating as many '*Ahh, that's nice to read!*' moments.

On the other hand, a best practice all engineering teams should follow is to open a "cross-team hub". A place to **share** the goals, decisions makers, the functional scope, timeline, dependencies, and information in order to get ready for a successful release. It's even more useful when you're working on a highly technical project like the refactoring of your query engine ;) Thus, you're empowering Sales *(and not only them!)* with a vision. 

![https://media.giphy.com/media/RJafwmy54b9SLX0OaT/giphy.gif](https://media.giphy.com/media/RJafwmy54b9SLX0OaT/giphy.gif)

Thanks for reading this article! And if you feel aligned with it, Strapi has [job openings](https://strapi.io/careers) both in Sales and Developer positions ;)