Stitched Stack

A stitched stack is a marketing stack assembled from many discrete tools held together by integration code. It is the dominant pattern at the time of writing. Most teams are stitched. Some are slowly moving toward platforms that consolidate two or three layers into a single piece of software, but the platform-centric pattern is still the minority case.

The practical reality of operating a stitched stack is that the most consequential engineering work in the marketing organization is integration work, not category work. A small number of engineers (or, increasingly, a small number of AI marketing engineers) hold the stack together by writing the glue code that moves data between the systems, propagates changes when one system updates its schema, and absorbs the failure modes that fall between the systems' individual ownership boundaries. The work is unglamorous, load-bearing, and chronically under-resourced.

Marketleaf's standing position on stitched stacks is that they are the right answer for many teams and the wrong answer for many others, and that the buyer's question is not 'should we move off our stitched stack' but 'what is the realistic shape of the maintenance burden of the stitched stack two years from now, given our growth trajectory, our team composition, and the rate of schema change in the components.' Teams that answer this question honestly often discover that the stitched stack they have is fine; teams that avoid the question often discover, a year later, that it has become a meaningful drag on the program.