David Collins

Tulsa, Oklahoma

Growth reaches its ceiling at the edge of the infrastructure built to support it — while everything still appears to be working. The ceiling doesn’t announce itself. It shows up as friction in systems that don’t scale. Value leaks.

The demand is working. The phones are ringing. The numbers look right. What isn’t visible yet is where the system drifts under the load it is asked to carry — because the brand is ultimately expressed through those systems under pressure.

The work is building that infrastructure — not the campaign, not the framework, but the underlying architecture of how demand gets created, routed, measured, and converted. Demand sets expectations the system carries. The harder question is whether the operational infrastructure is ready for the results.

That work requires being present across functions that don't naturally talk to each other. The infrastructure outlasts the org chart it was built inside.

That capacity isn't found in dashboards. It's built under pressure by those who have been inside systems long enough to know how they fail before they do.

Systems bridge the gap between a lead and a client. Judgment bridges the gap between a system and a result. Both require maintenance.

Across more than a decade inside a single organization — growth visible in the real estate, the built-out offices, the operational scale required to service what the marketing produced. Infrastructure rebuilt multiple times to carry that growth. Efficient marketing strategies drove operational growth that dwarfed the marketing operation fueling it.

The work included the full stack — demand generation, technology infrastructure, content operations, data intelligence, AI systems, vendor relationships, and a distributed production operation spanning editorial, creative, technical, and operational functions.

It also included the things that don't appear on org charts: knowing which number stopped describing reality, knowing when the framework blessed the wrong structure, and knowing what the system was carrying before it showed where it would fail.

The AI practice runs across the same system — from content infrastructure to workflow in a regulated environment, where client confidentiality and professional liability aren't compliance checkboxes but the actual design constraints. Getting practitioners in a privileged environment to trust and use new tools requires a different order of change management than standing up a pipeline. Both are in production.

The prior work covered different ground — data journalism and investigation, digging into public records and institutional systems, winning the trust of human sources, documenting civil unrest and its resolution at 100,000 watts, at consequential moments that required more documentation than commentary.

The most visible work has always run inside established systems, contributing what those systems did not develop on their own. The less visible work operates between systems — where alignment is prompted as often as it is built.

The through line isn't journalism or marketing or technology. It's pattern recognition in resistant systems and the discipline to find what actually moves them.

Different tools. Same problem.