Toss or Fix Your Tech Stack? - Part 2

Taming a technology stack audit can be a nightmare. In my first post, I opened up about an internal exercise that we had based on many conversations with our prospects and customers alike.?

That question? After a year, do we tune or rebuild our technology stack?

In this post, I will be diving into the evaluation process of how we decided on the tune vs. build argument for nearly 50 applications.

Criteria 1: Map out requirements in terms of what we need now without considering what’s already been built.

This is pretty hard to do when you’re working with a group of scientists, engineers, and marketers, as those considerations and needs vary.

A good example of this first step is a blog called Six Snappy Steps to Conducting a Marketing Tech Stack Audit .?

TLDR, with regards to the CRM angle.

The requirements:

• Mechanism to capture all leads and online activity, regardless of source
• To filter or qualify them so that we were creating the right experiences based on where someone needed help
• Create an experience for every visitor based on a relationship
• Understand how and where people are engaging with us so we can make proper decisions on investment and programs as well as return on investment
• The right leads to the right people at the right time. We’ve called this no lead left behind?
• Relationships through the sales process
• Be able to measure each step of the way to see where there are gaps, affectionately called driven operations

Now we have a requirement stock to look at everything we now have and see first of all whether it meets these requirements.

What requirements do you look for in your CRM system, and what are your thoughts on starting with the requirements first? How do you juggle the requirements of various business units?

In post 3, I’ll share criteria #2 that goes beyond the technology aspect and looks at internal and external teams.