Writing
I write rarely and with a clear thesis. Each piece makes a technical decision and its operating cost visible.
Long-form articles
-
Architecture analysis · LinkedIn
Suite, composable or warehouse-native
An analysis of nine MarTech stack patterns, from the integrated suite through composable and warehouse-native.
- 01Integrated Suite
- 02Collection & Orchestration Hub (Tealium)
- 03Data Platform Ecosystem (Microsoft)
- 04All-in-One CRM (HubSpot)
- 05Enterprise Application Ecosystem (Oracle)
- 06Commerce & ERP Ecosystem (SAP)
- 07Warehouse-Native
- 08Composable / Best-of-Breed
- 09Engagement-Centric Architecture
MarTech architecture glossary
Short definitions that separate products, capabilities, and architecture decisions. Each entry also explains where the usual confusion sits.
Architecture notes
Recurring problems in identity, customer state, Decisioning, and operations, always examined through the same lens.
-
Identity
Identity is a source contract
A graph resolves evidence. It cannot invent relationships that sources never emit.
-
Customer state
Separate operational state from customer state
Immediate orchestration and queryable facts do not need the same representation.
-
Profile governance
Profile writes are shared-state engineering
Multiple writers turn the profile into shared operational state.
Articles are published on LinkedIn and linked from here. I do not copy the text onto this domain, because it would compete with the version already indexed.
Are you making a similar decision?
If the analysis resembles your situation, email me with the context and the decision you need to make.