LDTech and EAS are two Midwest growth-stage companies running a 90-day Architecture Engagement in parallel. Both had the pattern Growth Architecture was built for. Strong operators. Real customers. Real opportunity. A patchwork of marketing activity that wasn't producing pipeline.
For LDTech, we defined a behavioral ICP across three buying tensions (the Overloaded Operator, the Risk-Aware Professional Firm, the Growth-Strained Builder). We separated TAM from active demand inside a one-hour Des Moines footprint: $17.5M to $63M of addressable MSP spend, with 20 to 30 SMBs actively evaluating at any given time. The strategic reframe: stop chasing geography. Be visible the moment the trigger hits.
For EAS, we built four ICP hypotheses around compliance pressure, ownership ambiguity, growth-driven volume, and the high-volume / compliance-optional segment. The TAM work showed a serviceable market within a two-hour Des Moines radius of 1,600 to 3,000 viable organizations, $20M to $54M in annual ITAD spend, and 40 to 100 organizations under active pressure at any moment. The strategic reframe, in plain language: $15K MRR isn't a TAM problem. It's a product-readiness and access-motion problem.
This is what Growth Architecture looks like in motion. Not a finished case study. A live one.