Episode Details

What’s up folks, today we’re joined by Bobby Tichy, he’s Co-Founder and Chief Solutions Officer at Stitch. Bobby’s a highly respected Martech veteran having spent over a decade working in technical roles for some of the biggest names in martech:

He spent a combined 6.5 years working on the Professional services teams at arguably 2 of the most well known companies in martech, Salesforce and Marketo where he was able to lead and support countless implementation projects for some of the biggest brands in the world.

At Salesforce he focused on Marketing Cloud technical and functional architecture. At Marketo he focused on project and program management.

In 2016, he left the in-house world and jumped to the agency side of martech working at Lev (a premier Salesforce consultancy) for 6+ years where he focused on Marketing and Enterprise architecture solutions. He also co-founded the In the Clouds Podcast, a show about Salesforce Marketing Cloud.

Last year, after Lev was acquired by Cognizant, he co-founded Stitch leading their solutions team. Stitch is a new martech consultancy that specializes in Segment and Braze tech stacks.

Bobby’s an expert in all things marketing technology architecture, customer data platforms, customer journeys and Dachshund dogs as the proud dog dad of 3. Bobby, welcome to the show, pumped to chat today.

In-house vs agency

I’d love to start by getting your take on agency vs in-house, pros and cons and maybe get the inside scoop on going from SF to arch-nemesis Marketo a few years ago?

I think the, the easiest way to think about agency versus in-house is when I was at Salesforce and Marketo, you’re really just focused on the specific problem as it relates to the technology. So that might be implementing, you know, Salesforce, Marketing Cloud or implementing Marketo for a particular customer. But when we’re on the consulting side or the consultancy side, you’re really more focused on that customer. 

So what problem are we trying to solve? It’s much more about business problems and outcomes than it is technology problems and outcomes.

That’s probably the best way to think about it. Or at least the the biggest delineation that I’ve seen over the years, which the consulting side is so much more fun and so much more complex. It has each has its own challenges.

On the SF to Marketo switch, I think I I was so naive at that point I had no clue that it was like moving to their arch nemesis. Now it would be like going from Braze to Iterable or you know something along those lines. And it was interesting because I even remember at the time, once I got to Marketo, there were all these kind of rumblings. You never know if they were founded or not. But you know when Exact Target got acquired by Salesforce, was it, you know, who are the other bidders? And I don’t know if you ever listened to the Acquired Podcast, but there’s an episode of Acquired on Exact Target and Scott Dorsey goes through like that whole process. Which is pretty neat. And then he mentions the SEC filings, they actually have to disclose, they don’t disclose the actual companies, but you can kind of deduce who the other bidders were. It’s kind of neat to go through.

But anyway when I got to Marketo, there was like all this conversation about Salesforce because the Salesforce and Marketo integration (at the time) was market leading as far as market automation platforms were concerned and the Exact Target and Salesforce integration was not all that great at the time. Now obviously that’s totally flipped, but at the time it was interesting because I remember my first two projects on Marketo and Salesforce, I would k