For most of us in B2B, the marketing automation platform - aka "MAP" - is the anchoring piece of technology in the martech stack. When I was first buying a MAP, there were way more options than today, but generally they all bundled a few core features together - sending emails, segmenting audiences, and creating workflows. But is there a reason why you need to do your lifecycle processing in the same tool that you send emails with? What does a Martech stack look like where these roles are distributed differently? Today's guest has answered that question and built an elegant and high-performing composable stack. Thanks to Our Sponsor Many thanks to the sponsor of this episode - Knak. If you don't know them (you should), Knak is an amazing email and landing page builder that integrates directly with your marketing automation platform. You set the brand guidelines and then give your users a building experience that’s slick, modern and beautiful. When they’re done, everything goes to your MAP at the push of a button. What's more, it supports global teams, approval workflows, and it’s got your integrations. Click the link below to get a special offer just for my listeners. Try Knak About Today's Guest Niels Fogt is Sr. Director, Automation Solutions at tray.io. He's led and participated in a wide variety of initiatives within growth and marketing. Strong technical acumen. UX roots. https://www.linkedin.com/in/uxstrategist/ Key Topics [00:00] - Introduction [02:31] - Niels’ journey as a martech architect [06:06] - Challenges with the traditional martech stack [09:13] - Developer mindsets and service-oriented architecture [12:10] - Applying automation capabilities across the organization [14:09] - Components of Tray’s martech stack [15:02] - The role of a customer journey tool [16:07] - Centralized lead processing in Tray [17:23] - Event collection [19:09] - Streaming events into automation tool vs. data warehouse [22:21] - Native vs. custom integrations [29:15] - Benefits of having a workflow layer in Tray vs. in a MAP [32:02] - Economics of using an iPaaS as a workflow layer [34:50] - Composable martech stacks [39:03] - Skillsets needed to operate a composable stack [40:01] - Future capabilities [41:25] - Relationship to business stakeholders Resource Links Why low code is the future of lead management (and RevOps) Introduction to the lead processing pipeline on Tray.io Open source RevOps: Taking a closer look at the first few steps of the lead processing pipeline Learn More Visit the RevOps FM Substack for our weekly newsletter: Newsletter
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
Justin: For most of us in B2B, the marketing automation platform, AKA map is the anchoring piece of technology in the Martech stack. When I was first buying a map, there were way more options than today, but generally they all bundled a few core features together. They provided a database for your lead and activity data. They provided a way to segment audiences. They send emails, they give you forms and landing pages. And they provide workflow functionality, the ability to execute if this, then that style logic for various things like your scoring, your data management,
your pipeline management, and so on. So whether you're using Marketo or Pardot or Eloqua or HubSpot, you're kind of used to thinking of all those functions bundled together, but does it have to be that way? Is there a reason why you need to do your lifecycle processing in the same tool that you send? And of course there isn't, but what does a Martek stack look like where these rules are distributed differently? Today's guest has answered that question and put it to the test. Neils Fogt is senior director of automation solutions at tray.
io, where he's been for almost five years and he's built a composable stack and documented exactly how it works in a really interesting series of blog posts on the And one thing I'll say Niels is I've been thinking about these problems for a lot of years, and you really have put something together. That I've thought of a few times, but hadn't yet seen or done, which is a pure workflow layer that's abstracted from the map. And you've done it in a really thoughtful and well architected way. So I'm really excited to dive into the details with you. Welcome to the show. niels-fogt_1_02-20-2024_140545: Awesome. Thanks for having me, Justin.
And just want to say a big thank you for having me on the podcast. did have a chance to listen to your episode on the humans of Martech this morning and just really appreciated the level of depth and of insight that you had as you were talking through how we're all thinking about AI. these are all really interesting technical challenges and speak to me and my technical itch when it comes to working on these kinds of problems and understanding I think that affinity towards looking at these sorts of technical problems innovating on technology is kind of what drove me to
rethink how we approach the Martech stack and Anyway, I'm happy to go wherever we want to go and talk through that journey. But this is definitely a privilege to be here. So thank you. Track 1: Oh, thank you so much. I really appreciate that. And why don't we start with just like a quick replay of your journey as a martech architect, because I think all of us make decisions. In large part, based on our past experiences, what we've seen that's worked and didn't work. So, before you came to Trey, were the sort of tools that you had worked with? niels-fogt_1_02-20-2024_140545: Good question. . I actually didn't start super heavily on.
Ops and rev ops until I got to Trey. was always in and around it and always working closely with ops people, but it was not my primary profession. So I actually came up in the tech space through a user experience agency. So what we would do is we would, this was in the lean startup days. If you're familiar with. When the Eric Ries craze was going on, we were working with a lot of high growth startups who needed help with user experience design on their either through their product or through their marketing website.
Going crazy and their needs are constantly evolving. That's the type of work I came up doing and what I always gravitated towards that. Is the technical side of it. And so for example, I would basically be like a product or project manager for a UX engagement. And we would have inevitably some kind of technical piece that needed to be delivered with that. Let's say front end code or website CMS or something like that. And on the background, what I would be doing is actually can I help with Devin, some of that WordPress side, or can I like, figure out
how to hack in tag manager here? I would, always just find ways to insert myself into the technical side and self taught myself a lot of that stuff. So, ended up doing was I went in house to a company called New Relic, basically doing exactly what I was doing in an agency. Setting and inside new relic, which was a high growth dev tool startup. And I got exposed to a lot of interesting technology. So at the time segment came along and we were using analytics dot JS as our data layer, so to speak for collecting all this clickstream data. And we're like, okay, well now we've got to put it in a data warehouse, right?
So we got red shift, right. And we started putting all that data into Redshift and they're like, Oh, crap. Now what do we do? We've got to get it back out. So we were doing like reverse ETL before reverse ETL is cool. I like to say and so, Redshift, analytics. js, tag manager. Those were like where I came up on the data side and just kind of like, how do I pull this all together and use it? And then as I. Come into more of a operations role here at Trey. I've gotten exposed to the classic MarTech stack, which when I first got here was Marketo and Salesforce and outreach and, all the sales enablement side, sales
navigator and sales OS and all this kind of enrichment vendors, all of it. , I'm also, I'm familiar with a lot of the traditional sort of Martech stack and have a really close familiarity with, I would say like the whole data stack that's been evolving over the last, , six or seven years. Track 1: I could really relate to what you were describing on those projects, like gravitating towards the technical, because I felt very much the same when I first started getting into MarTech more broadly. And I don't know what it is, but there's just something about the. Oh, this is cool.
Like I could, stitch these things together and build something cool, almost like playing with toys, but not to trivialize it and describing it that way. But there's something very fun about making something work and stitching it together and having an elegant architecture. So there's a certain scrappiness to your approach that you described. And even though you dent inherited a conventional stack at Trey, you were starting out, it seems like at new relic with a lot of different. So it wasn't like this scary undiscovered territory, you were already exposed to, you know, what these alternative paradigms would look like. So you came to Trey, you've got, your standard Marketo Salesforce outreach,
which a lot of us can relate to. What were the pain points and what were the challenges that you were experiencing with that design? niels-fogt_1_02-20-2024_140545: Yeah. So when I first came in, my job was actually nothing to do with this, right? So what they actually wanted me to do was a lot of what I was doing in Heroic, which was like, hey, help us stand up a PLG motion, right? We've never had a trial. How do we do that? And help us get our web presence up to snuff and like that sort of stuff. But again, inevitably I found myself gravitating towards
those technical challenges. And so I was talking to our. CMO one day. And he's look, like we are having all kinds of data reliability problems, right? Whether it's with not understanding what stage our leads are at in the funnel or not being able to attribute all these programs that we're working on, right? We're spending all this money. And doing ungodly amounts of paid advertising events, all the things right. And I just don't feel like I can trust what this data is telling me.
And yeah, we've got all this great tooling but you still have to be able to orchestrate that tooling and make everything work and make it work consistently in a reliable fashion. And so I think it was like a lot of the classic problems that young marketing teams have and young evolving organizations have, and they just needed help perfecting that. Now the interesting part was I didn't come into it with a preordained mindset, right? Like I didn't come into it with. Okay. Well, this is how you solve that problem on Marketo. I just came at it from a more, I don't want to be snobbish about it, but
I a first principles like mindset. It was like, okay, well, what are the jobs to be done here? What do we actually need to do? And with that different perspective, I started trying chipping away at it. And I worked pretty closely with a, died in the world marketo champion who we had employed there who was also struggling with these problems. Like she too was. Going I don't know what's happening when and where, and things are overwriting, and I can't seem to quite choreograph things in the way I need it to choreograph. And so we paired together and slowly, but surely we started building capabilities.
And so a simple first version was email validation. Like it's really simple and silly, but every time we get a new lead, we need to conduct some email validation post processing, right? And so I built her a little service that called clear bit risk and never bounce. He did some basic syntactical validation and a workflow. And I'm like, here, just call this through your Marketo program. It'll tell you if it's good or not. And we started just standing up these little capabilities. And that's how it started. Track 1: What I was thinking in some ways as you were talking was like, Oh, this is really interesting.
Cause like you can solve a lot of those problems with call it Martech, or map native approaches or architectures. Maybe the way that you're doing it is probably better for various reasons. Like actually have come around to that conclusion, or at least as a hypothesis, probably too early to say it's a conclusion. But you, Gravitated naturally. I think it helps that you're working at a, at an iPass company. So you had those tools available to you and there's a lot of confidence in the tools, but is a less conventional approach.
And was there anyone or any company out there that you were inspired by, or you really were just well, like we need to put this nail into this wood and this looks like a hammer. And I think, you know, it looks like a good way of doing it. Let's do it that way. niels-fogt_1_02-20-2024_140545: I would say it was probably more the latter. If anything, what I've been, was inspired by was actually New Relic. It mostly, I was really exposed to developer mindsets. And how you architect systems. At the time we were real big into service oriented architectures and that was right.
Break down the monoliths and to more narrowly scoped services, which have a very narrow function and purpose. And then by doing that, you can use them more interchangeably. So just that idea was sitting there in my head of okay, services, right? Narrowly scoped. I could build services on tray so I can build a validation service. I can build a MQL service. I can build a routing service. And so all these again, jobs to be done. I was like, well, yeah, all you need is some inputs.
Right. And if you don't bloat it up it'll be real easy to use. . And then now they're like little pieces that I can then choreograph. And so that was really a big. influence for how I just thought about solving the problem. We just kept chipping away at it, chipping away a little bit more, a little bit more, and to the point where it's wait a minute, we just look back and we're doing all this work that was previously done elsewhere here and man does it scream like it's like fast, like really fast. Like from the time I see a lead until the time that person's coming out of
outreach, it's like 45 seconds sometimes. No more than 90 seconds and that's pretty cool. And not only is it screaming fast, but like I can, if anybody ever has any complaint anywhere, like I just go straight to the service. And I can see exactly what happened when and where and how many times it's happened then go back to the process from there. It just really felt elegant and easy to manage. Track 1: I love what you said about the developer mindset. And this is coming from, an English major who fell into marketing and
then somehow fell into technology. But I picked up a lot of that from folks like Sanford Whiteman or Jep, you also know who have kind of just modeled a lot of those ways of thinking and things like You know, don't repeat yourself or having like loosely coupled services, exactly what you said. So it's kind of used to building those within Marketo, which you can do in a way like you can modularize things, but it's not built to have the same level of, let's call it like ability to orchestrate in a defined way, or probably
the level of logging that you get. Certainly you don't get to see like a full JSON input and output for everything the way you can. I think in a lot of I pass tools. So where you went with it seems really logical to me and I've kind of had the thought. You know, you're used to doing it one way. And you don't go there. niels-fogt_1_02-20-2024_140545: I'm sure there are a lot of fantastic Marketo power users out there, right? You just have to know how to use the tool. But one of the things I would maybe argue is that, While things like use cases around the bicycle are important and probably, a first class challenge for
ops teams to solve, they're not the only challenge where automation and a service oriented architecture can be applied. And as you look across there are use cases in which this core, fundamental skillset. Is applicable meaning relational systems, data models, service oriented design, understanding business logic, all that kind of stuff. There are many processes which you can apply that to that once you have that core foundational skill set, make you a much.
Different player in the ops space, right? You can impact many more parts of the business that where they're just not getting the love of those kinds of capabilities. Like a simple example is your community experience, right? So everybody's using a Slack based. Community experience now where you have this ability to have this very interactive experience for your customers. And the capabilities to, connect that experience to your rev ops systems or your product systems can create some really cool things, right? So like we have. A very interactive slack community where we built these various slash commands and
things that allow our customers to like, check your user score progress, check your education progress, apply a badge so that all your best power users have a special little annotation on their name, right? And everybody knows they're the best one at your tool, right? Or , people have a lot of workflows on trade. So look up a workflow by keyword through slash command, right? Like use AI, it doesn't really matter. What I'm trying to say is there are many places in which this capability can manifest. And when you house it within this really rigid frame of marketing automation, then I think it limits your worldview.
can do a lot more. Track 1: I want to zoom out for a second and look at your stack as a whole tray obviously being a critical part of it. But what are the other main components of your martech stack today? niels-fogt_1_02-20-2024_140545: Like traditional demand gen stuff, right? So we have pay all the paid social lead sources, right? You have those we have all your traditional enrichment, like vendors, right? So zoom info, clear bit. We have event platforms. We use zoom for our webinars. We use a little bit of event here and there for some bigger events.
We have, of course, Trey, right? Acting as this orchestration layer. We use iterable. We use them for journey orchestration and all the email campaigns and all that kind of stuff. We use iterable for that. And then we have sales OS, sales navigator, right. For all the contact sourcing, that kind of stuff and outreach for sales engagement. Salesforce. Track 1: I'm broadly familiar with like kind of the iterable embraces and in my mind, in this like customer journey.
engagement type of platforms, but in terms of what parts of what we might think of as Marketo functionality that iterable is taking over and what parts are in tray, how would you divide up those kind of duties between the two platforms? niels-fogt_1_02-20-2024_140545: centric. Iterable is essentially what I call journey orchestration, which is. Most of your customer facing communications, ? Usually there's a variety of use cases for that, right? So you might have a nurture journey that you take somebody through once they hit a certain status within your CRM, or at least for us CRM you'd have
like fulfillment type stuff, right? So you had some piece of content that you need to fulfill. Right. And then you need to deliver that. You might have just basic database marketing stuff, right? You have an event coming up. You need to segment your database by a certain, through a certain group of people, right. And get those communications out and webinar operations, follow up, all of the traditional customer facing journeys is happening through iterable and then all of the lead processing data management is happening through Trey, meaning, okay, from the moment you capture that lead from any given source could be your
website, could be your chat platform, could be your, ad vendor, whatever it is. We ingest that through a Trey workflow. We normalize the data. So we need to then normalize it so that it fits a common data model. Apply things like lead source, all that kind of stuff. And then we run it through what we call our lead pipeline. And our lead pipeline is this sort of amalgamation of lead processing jobs. So the first thing we always do is run it through email validation. Then we run it through a lookup process to see if we have that record in our CRM already.
If we don't, we enrich it, create it, lead to account match it. Run our attribution process, which is basically just stamping the dates and stuff on the life cycle objects and putting campaign memberships in place. And we run it through an MQL process. And the MQL process is like, Hey, are you an MQL? Yes, you are. Okay, then route it. Right? All that sort of end to end journey is happening on Trey. And then there's always the ongoing stuff of are we constantly making sure we understand where somebody is at in the funnel and progressing them through automation so that we all, run our reports and intelligence on, how
everything's working and where people are standing, that's always up to date. Track 1: I'm thinking of MQL and I'm thinking as you're talking, all right, there's that initial processing flow and then potentially somebody comes in. They're not an MQL yet. Maybe you have a concept of an MQL threshold, which is based on points or an accumulation of activity, and it made me think about where's that activity layer like the piece that's tracking you visited these web pages and then maybe Me. You know, assigning some points to that. Is Iterable responsible for that, or do you have a separate event collecting system?
niels-fogt_1_02-20-2024_140545: Yeah, so we use analytics. js. You can think of it like munchkin. So, Segment provides analytic. js. So we collect all of our sort of clickstream behavioral data through segment, and that includes the page view data, the form submit events, all those sorts of things. And so we can essentially listen for those events through Trey, and then we can action upon those events, whether that be for changing data values or trigger orchestrating some kind of like internal action or external action,
we can just listen to those events. Track 1: Are you streaming those events also into a warehouse or something, and simultaneously into Trey? And niels-fogt_1_02-20-2024_140545: So segment has a native Redshift, Track 1: get niels-fogt_1_02-20-2024_140545: pipeline. So they're constantly keeping up our different segment sources that are collecting all this behavioral data and pushing it into Redshift and then. They're all the data team will have like jobs that sit on top of that to basically amalgamated, you know, data and it's for all form isn't always the most useful. Sometimes you need to aggregate it and create views on top of it to make it more
consumable for some system or process. Track 1: Independent event collection and storage, and then making those events accessible to other tools. There's a lot of debate around what's that order of operations look like and potential latency and, so you've made the decision obviously to stream it to, both places, which is the one that makes the most sense to my mind. Presumably you considered at least the option perhaps of sending it to
Redshift and then pulling from Redshift. What made you not go in that direction? I guess, what were the disadvantages if you did consider that? niels-fogt_1_02-20-2024_140545: Well, for the most part most of our needs are met through this event driven architecture. And we don't have like crazy complex scoring and point systems and those sorts of things. Actually, we tried it and we basically decided it was this sort of like subjective. Assignment of value that like, drinking a lot of Chris Walker Kool Aid these days
where like he has this point of view on your declared intent or high intent, like leads being your most valuable leads and this idea that like we have this, weird subjective view of Oh, well, if you viewed two pages and you like downloaded an ebook, like that makes you qualify. That's the ticket. Right. Maybe we're over complicating this idea of this whole MQL in sort of a stick your finger in the air kind of methodology.
And what we really need to do is like optimize for a great experience on your high intent leads, which can be basically done through an event driven system. Right. In my opinion. And then there are better ways in which to surface the right people to talk to sales and the experience that you should give them. So, in that regard, we're okay with more latency essentially is what I'm saying. Like you don't need this real time scoring routing kind of thing for the people who are not declaring their intent. And so that's why we're okay with essentially pushing
things to the warehouse. And by the way, we're not perfect here. Like we're still in this process of how do you basically take this first party data set that you have and provide sales with a good subset of people in which to prioritize and use the correct motion with those people, because they're not saying to you, I want to talk to you right now, right here, right now. And so as long as we can get the high value leads through real quick. We're okay with a little bit of latency on the backside.
Track 1: So those events, it sounds like are mainly like form fills of specific, like what I would call hand raised forms. And then for iterable, does it sit on top of the warehouse or does it sit on top of CRM from an integration point of view or a combo of the two? niels-fogt_1_02-20-2024_140545: It mostly CRM, right? So most of the data that we need for segmentation purposes is written to CRM. And then I built a custom sync between, cause they don't offer an out of the box Salesforce integration. So I built a custom sync on tray to basically push that data between them.
And then we have a handful of custom events that basically act like program member triggers So like anytime we apply a person a campaign membership to a person in salesforce we listen for that through tray and then we emit an iterable event which gives you program membership triggers Like that's the campaign membership triggering process. Track 1: Let's talk about integrations a little bit. Cause one of the. And I think one of the pieces that you focused on a lot in your blog post series was moving away from native integrations and using Trey
as this primary integration hub. And I was curious what the benefits of this are from your point of view. We all have seen some limitations to native integrations on the plus side, like they are a lot more out of box and presumably there are a lot of things like error handling and that sort of logic kind of built in to some of these integrations, at least ostensibly. That, , otherwise, you have to rule your own, which can be daunting for some people. What influenced that decision, as you were building this out? niels-fogt_1_02-20-2024_140545: It mostly came from Necessity, right?
So we had a belief that best in breed tooling is how we want to go. We have a belief that we can own our own process in a way and make it work in a way that we want to work by taking this approach, but the truth is do have a connectivity issue at that challenge, right? Just like we were saying with Bitterable a minute ago. Like they don't offer a native Salesforce integration.
So that's a problem that we have to solve. So I'm not against native integration by any means, right? if it's going to do the job that it needs to do and save me the cost of ownership, please, I will take it. Because we have the capacity to look at these problems a little bit differently. I don't have to put up with the shortcomings of those integrations. And so that's what generally drives it. It's sure. We could use that, but then we compromise that last 10 to 15
percent where it's falling short. Right. And so rather than build around those problems and, you know, try to explain those problems to somebody who just doesn't get it, right. Like we just simply have decided that we don't have to do that. And nine times out of 10, it's not this crazy complex integration problem. It's usually just a few small things that are. Causing it to be non ideal, right? When you have those hard skills around, well, okay, I understand webhooks. I understand the APIs. I understand basic data mapping and transformations.
You could actually close those gaps really easy. You just have to have those hard skills to be able to do it. So it's just come out of, okay, we have those hard skills. We know what the gaps we need to close. Let's just close them and move on. Track 1: One of the experiences I've had building Kind of a native integration equivalent process. And I pass was with Trey. It was a different one, but similar sort of logic and workflows. It's definitely achievable was my observation. You're a lot more experienced than me in this domain, but you quickly realize
like some of the things that you take for granted, for example, like preventing infinity loops, where you have something like this recipe or this workflow triggers off an update in this system and makes it up and that makes an update, but then this workflow triggers off an update in this system and then they start ping ponging. And so then now I have to solve that problem. And you're like, oh, but what if something is updated in both places at the same time? Now I have to do like field level comparison and resolve conflicts and just things that you don't really realize are happening under the hood in a normal integration, when you actually have to go and build it out, you kind of appreciate
that, oh, it's doing a lot for me. How have you thought about solving those things within your architecture or have you built it out in such a way that you could sidestep some of those problems? niels-fogt_1_02-20-2024_140545: Yeah, there's not an easy answer. So first of all, I would argue that those problems you're articulating are actually probably happening already in your native integrations, and you probably don't realize it, or at least you only hear about it episodically. And a lot of things are black boxy, so to speak.
So, just because a native integration does solve some of those problems, doesn't mean they've solved all the problems and it's perfect, right? These are all highly relational systems and the more things that are interfacing with those systems, be it native integrations or custom integrations or whatever it is, there is this ping pong effect happening. Toe one extent or another. So almost certainly everybody's dealing with this problem, it's just more that you're less aware of it when you're not on the front lines dealing with it.
Track 1: We're all just sitting with our head in the sand, blissfully unaware niels-fogt_1_02-20-2024_140545: yes, Track 1: of all these issues. niels-fogt_1_02-20-2024_140545: or aware, not having much bliss at all. Track 1: Yeah, or the opposite of blissfully. Painfully unaware, niels-fogt_1_02-20-2024_140545: What I would argue is like when you own some of this and you literally have the process level visibility when somebody goes, Hey, I see this problem why did I get this link? You go specifically to the metal where you see exactly where it happened, exactly when it happened. And you can to that specific situation, then you can solve it.
Otherwise you're beholden to the level of observability that you have on that system. So I'd rather at least know where my problems lie and that I can fix them. Then not know, Track 1: Do you believe in keeping a kind of intermediary source of truth between two integrated systems so that like you kind of dump changes from one system in here and dump the other ones and then you kind of have this neutral place where you can sort them out? Or have you found that just like two point to point integrations, you're able
to build the logic in such a way that works an acceptable amount of the time? I'm going to use the marketo integration as an example, but my understanding of how it works is it's taking all the changes from the marketo side during any particular sync interval, and then taking all the changes from. The Salesforce side and then it's comparing them. Cause if you just think from point to point, it's kind of like blind. It's I have this, I go over there and you have this and you go over here. And there's other systems out there that I've seen that less pure I pass systems, but maybe like Synchry, for example, that maintains this sort of independent, neutral data store in the middle for integration
purposes, which I think makes sense. Like it does answer a lot of those challenges, or you could just use a Snowflake database or a Redshift database of your own in the middle. niels-fogt_1_02-20-2024_140545: I'm sure there are circumstances where the level of complexity between two systems like MAP and CRM and the sort of throughput. Let's say going through those two systems is sufficient that you need a much more sophisticated layer of triaging conflict and resolving some of the issues that you've articulated, but in our particular case, it hasn't become a
big enough of a problem and that we've needed to resolve those conflicts. And that's not to say that means It's not a perfectly valid challenge that people have, right? I think is given that we are able to kind of standard on Salesforce as our source of truth and move out from there. We've not hit some of those traditional snags. Track 1: That makes perfect sense. I want to dive back into your lead processing workflow, and you've given a high level overview of how it works so far. Most people as we've talked about, handle those functions in the map and in like
my Mariketo instance right now, I have. A lot of those services that you described built out, but they're just like little brown program icons, like enrichment, MQL, scoring, works pretty well. I can orchestrate them. Our needs are not like hugely complex at this stage. But you've moved all those functions into Trey. You don't need to convince me of the benefit of doing that because I've seen the power that having a dedicated workflow layer brings, but From your point of view, what are you gaining from going there that you couldn't have just built into Marketo perhaps? niels-fogt_1_02-20-2024_140545: Probably a few things like I gained confidence.
I feel very confident using Trey, right? And I can like. I can absolutely tell you two decimal places, how often any one of those processes ever go awry. I get notified if anything's going wrong, instantly, basically. So, to me, having that level of comfort and confidence to know exactly what happens when and where. And where to go to fix it is huge for me just from pure nuts and bolts, ops perspective. I'd say the other thing, if I just kind of take a step back and think about
us as an organization we have a lot of leverage in our marketing stack, right? = Because. I have such an ability to evolve my process quite easily. I don't have to have as much technology in our stack, I have a lot of leverage and vendor conversations, right? Because it's a job to be done, which is the process orchestrates. And if I find that one vendor happens to be better than the other, I'm not constrained by all of these more rigid. connections between those systems.
So that ability to have leverage and flexibility and how we approach our technology stack is quite nice. And the other thing that we gain is speed, right? I mean, this thing is just fast, right? And I love. Knowing exactly how long something takes and if I need to deal with a huge amount of throughput, suddenly I can do that and it's not a problem. We can do it really fast. So let's say those are some of the main things. Track 1: Make me jealous while you're talking because I don't have, what I would consider a really robust workflow tool right now.
We have Zap here, but, it's certainly not as powerful, let's say, as some of the other options that I've used in the past or for Trey. And the freedom that it brings to know when this thing happens over here, that I can go over here and update this data value, and there's this power and control, as you're saying, that you have. It's so liberating. It's one of the reasons why I really fell in love with that category, for what it can do. People that don't have that, I think, don't know what they're missing, number one. But it also made me curious, as you were describing what you can do, You, I'm assuming, have a fairly unmetered version of Tray.
And you mentioned at one point, I remember when you first brought this up in conversation, this design of your stack. There's cost savings involved. From a real world economic perspective, if I was to become a Tray customer and how did the economics shake out? Because different vendors price in different ways. Some price per task, some price per workflow. Am I saving money at the end of the day, do you think, or am I going to be forced to constrain myself in a different way? . niels-fogt_1_02-20-2024_140545: So we're a consumption model, meaning we build off of tasks. We don't believe that a workflow based model is the right mentality
because it doesn't fit with our philosophy that you want this service oriented architecture, right? Like you want to be able to build a process, whether or not that process runs a couple of times a day or a million times an hour, should build. A smart architecture that handles your processes in the most efficient and manageable way possible. And we think that when you put like billable constraints on things like workflows, essentially people don't solve problems, so we want to tie the consumption of the platform to the cost.
I do think that there's true savings that you can have, cause I don't own a lean data. I don't own a marketo. I don't own a lot of tools that you may have to pay a lot of money for. So, what that exact number is I don't want to pretend that I can give everybody a really clean answer on it. And you do have a cost of ownership with this model, to your point, right? Where you're building certain things. So to me, do think there are cost savings in there, but probably the better mindset to have about it is the level of flexibility and capabilities
that you're able to bring to your organization and solve problems in a much faster and efficient way, so you don't have to have this straight jacket around you where you're trying to operate within the constraints of that straight jacket. Like I can build my stack in the way I need to build it and make it work the way I need it to work, which allows me to help our organization facilitate, rapid change faster, we're all talking about AI now, how are we going to get AI into our process? And we're worried about governance and we're worried about security
and we're worried about, how do we use our first party data and these models and all this kind of stuff. Right. Well, I would argue that when you have a capability like this to build your processes in a way, then you can take new capabilities like AI and you can bring them into your process much more easily. And so to me, indexing on that agility and the ability to do what have your stack, do what you need to do for your organization is just as important as saving, you know, five figures on your vendors this quarter.
Track 1: You mentioned the humans of Martek podcast and my friends, Phil and John over there, they've talked a lot in some of their episodes about, composability and creating a composable CDP. And it's one of those words that's very much. In Vogue right now. Were you thinking about composability when you were designing this? Or do you see your stack as falling under this label? Or so happened that you've approached it in that way? niels-fogt_1_02-20-2024_140545: It's absolutely a composable stack. If it doesn't meet the definition, then I'm not sure what does . The whole idea.
Is that you can take these core services or jobs to be done and orchestrate and use them in the way that you need to this idea of abstractions. It's nothing new per se, we were talking at the start of the call about. Analytics. js or segment, right? Like they came in with an abstraction layer to instrumentation so that we can move event data to either point solutions or your data warehouse quite easily and not have to go through that process for every new tool we bring into the stack, This idea of abstraction has been.
Going on for quite a while. To me, what we're now getting into is kind of had this initial sort of data layer abstraction happening. And you have in the sort of cloud data warehouse, right? Consuming that and acting like its own abstraction layer your workflow. Version of this is just another version of abstraction and composability right where we're now you're creating these capabilities that can be just like those other tools they can be used in a fashion that gives you The flexibility to decide when and how they're used.
Track 1: It seems that there is an increasing trend towards companies designing these sorts of point tools microservices and they all kind of come up in that way. And at the same time, though, there is an increasing economic pressure in the marketplace for companies to consolidate functionality. And I think we see this in lot of the sales engagement space where we have the gong and the. Sales loft and, you know, various tools like that starting to try to eat each other's lunch from various angles and acquiring tools and bringing them together.
And, , there's reasons that it's easier for budgetary purposes for companies to do that. Or you have the HubSpot is maybe the perfect example where they're like, we'll just build one of everything, we're just going to build it and it's all going to be one. Huge monolithic stack. Do you see both of these models coexisting? you see the future as one in where there's just like this endless diversity of point services and then orchestration tools that bring them all in these wonderful ways? What does the future look like from your point of view? niels-fogt_1_02-20-2024_140545: I don't think it's a endless sort of amalgamation of point services. At some point, there is going to be some benefits to taking certain more,
let's call it more broad platforms and Leveraging whatever capabilities those platforms have if it makes a lot of sense for your business and it does what it needs to do, and there's less overhead for you, right. And running that model, then run that model that is okay. There's nothing wrong with using a really smart set of tools to do the core jobs to be done that need to be done, like we don't need to just. For the sake of composability, right? To develop a composable stack.
That's definitely not the mindset I would take. I think it's just more so that having the ability within your four walls of your organization to cross that line when you need to. Is a capability that we should be prioritizing for our ops functions . Meaning this is a critical skill set for operations teams to have within house, so that when that platform doesn't do what you need it to do.
You can make the changes that you need to make and are not beholden to the constraints of that system. And, That is where you use it, right? And that's a always evolving thing. Our stacks are constantly evolving. The vendors of today are going to get beat by the vendors of tomorrow, right? And we want the ability to be able to move with that change. And so in order to do that, you have to have these competencies in house, because otherwise don't control your destiny. Track 1: So speaking of the ever evolving state of things, . What are
the, to do list that you're like, yeah, I got to fix that someday. Are there still some rough edges here and there? niels-fogt_1_02-20-2024_140545: One of the harder things is what we've been talking about is like, do we Make sure that we can continue to run this practice. So one of the harder things is just teaching people the hard skills, right? Like I've learned that there's a certain profile of operator. I need to have underneath our roof who has the right sort of skill sets to be able to run this sort of practice. So early on. For example I was probably not looking at the right types of individuals
when the right types of skill sets because is a more technical challenge. Whereas maybe you may have brought in more junior practitioners, for example, as part of an ops function, you can't execute this model with a junior practitioner who doesn't have a good systems architecture mindset. So that's been a challenge that I've learned just like, how do you find the right skill sets to run the approach. And then as far as areas for evolving the system I don't have this major thing that stands out where it's just Oh, we absolutely have to fix.
I don't know, our lead scoring approach or something like that. I've been running it for probably three and a half years now . And so it's pretty mature. So what we're actually more so thinking about is, what is next in our Inside of our house of capabilities. And so we're doing the trendy stuff right now. Like, how do we actually understand where we can apply AI in, inside of our organization to do like the things you guys were talking about on humans and MarTech, like how do we take less structured data and what are the
technical underpinnings that we need to have in place to be able to consume that and make it operationally useful. For our organization, kind of skill sets in services do we need to have in place to do that in a way that security is also going to be like, that's cool. You're allowed to do that. And it's also useful and functional for the business. So one thing we've been doing right now is building a service around our all of our sort of knowledge content of how we consume that Put it into a vector database, create a service that, we can then use with our knowledge content and
then use that for both internal enablement use cases and customer facing use cases. Track 1: Chat GPT that's trained on your own docs or your own data kind of scenario. Maybe last question I'll ask is in terms of the evolution of this and how you evolve it day to day, what's your relationship to your business stakeholders? Is it you coming up with ideas or presenting them? Are they coming to you with requests? Is it more of a product management style? How do you triage and roadmap these things?
niels-fogt_1_02-20-2024_140545: Pretty much like any classic ops team, right? So like I am a business partner to other parts of the organization. I report to our CMO. And so, a lot of what we're doing right now is just ensuring that we're facilitating the go to market strategy that he's laid out for the organization. And we were in a as an organization, a bit of a transformational period, where we're shifting our go to market strategy a fair amount, which requires that you got to reevaluate all the things that were tied to the old go to market strategy. And so just like any other ops team, like we'll hear the challenges that
he is putting forth for us to change, and then we create a roadmap and we prioritize that we work with our same thing with our sales leaders, right. When I go to market strategy evolves, the sales organization evolves, you get things like new territories and new segmentations your customer base and all that sort of stuff, I don't think we're doing anything all that revolutionary there. We just have to be, tied to what the business is trying to do and creating a set of priorities, determining what we can do easy and as impactful and making those changes as quickly as we can.
Track 1: Well, they're lucky to have you. And I love how you think about this stuff it sounds like in many ways you've built something really awesome. So I'm glad. That we could just talk about it and expose more people to the way that you've thought about your stack I will include links to your blog post series and the show notes because you go into Really high level of detail on what you've done You have videos if you're listening to all this To those of you out there and thinking like oh, I just really should really see and understand more What Niels is talking about you can because he's gone over it with screen share.
So we'll share all that But yeah, thank you so much for coming on the show. It's been a ton of fun learning about niels-fogt_1_02-20-2024_140545: Awesome. Yeah. Thanks for having me.
Every time you explain your business to an AI from scratch, you’re repeating work. The opportunity with context engineering is to make your company’s expertise, processes, and past learning available whenever an agent...
Justin and Lily reflect on their parallel journeys diving deep into AI throughout 2025. They discuss why most AI content misses the mark for operators and system builders working within corporate constraints, share...
SEO used to be the ultimate growth lever - offering massive “free” traffic to marketers who could outsmart the algorithm. But in 2025, it's a different game. In this episode, I’m joined by Gaetano DiNardi - an SEO...
AI agents are everywhere in conversation right now - but what actually makes them work? It’s not just slapping a large language model into a workflow and calling it a day. Under the hood, real agentic systems operate...
Not many people make it to VP of Marketing Operations - Kimi Corrigan has done it twice. In this episode, she shares her journey from marketing coordinator to leading marketing ops at companies like Duo Security, Cisco,...