The ultimate guide to Martech | Austin Hay (Reforge, Ramp, Runway)

Hay describes buying tools and building the connections or custom pieces around them. A stack needs architecture and an understanding of the problems it serves. Adding another vendor does not itself make the system easier to operate.

He often sees a growth employee who knows every setup become overwhelmed as tools and dependencies accumulate. Pain can include an inability to change something safely because nobody knows how it was built. That is a signal to examine ownership and specialist capacity, not simply buy a replacement tool.

Hay says early companies may focus on survival, while scale makes pricing terms, liability and future usage costs more important. A low price at today's volume can hide a much larger future expense. His examples are discussion points, not current vendor quotes or legal advice.

He contrasts centralized and decentralized martech and describes Ramp moving between models. The decision depends on whose problems the function solves and whether it can get resources. He does not claim one reporting line fits every B2B company.

A second tool can add both spend and uncertainty about which system to use. Hay also asks how a business prevents returning to the same duplicated state. Consolidation needs rules for future adoption, not only a one-off cleanup.

He treats access and permissions as part of system design, using accidental test emails as an example of what can go wrong. He also asks what happens a year from now if the setup stays unchanged. Think ahead without overbuilding so much that today's product needs suffer.

Hay looks for learning ability, enough technical skill to inspect APIs and systems, and a willingness to ask what the problem is before choosing a familiar tool. His interview question asks how a candidate would assess the current stack. A resume label alone does not show that approach.