In partnership with
35% of leads come in after 5PM.
If you don't respond within 5 minutes of a call, conversion drops 80%.
By morning, they've already called someone else.
The businesses closing that gap are seeing real results.
Air Texas booked a $20K job from their very first after-hours call and canceled their $2,000/month answering service.
Premier Heating & Air cut response time from 12 minutes to 1 and tripled lead conversion.
Air Design ran 187 membership jobs through automated outreach and generated $24K with zero manual work.
That's what happens when every call gets answered, every lead gets followed up, and every membership gets worked, automatically.
Podium's AI Operating System does all of it, in one place, built specifically for HVAC, plumbing, electrical, and garage door companies.
The moat isn't the model anymore. It's who sits inside your building.
THE SIGNAL
On July 2, 2026, Microsoft announced Microsoft Frontier Company — a new operating unit backed by a $2.5 billion commitment and 6,000 engineers, industry specialists, and salespeople whose job is to embed directly inside enterprise clients and co-design, deploy, and optimize AI systems. Two days earlier, AWS committed $1 billion to its own version of the same play. Anthropic, OpenAI, and Google have already shipped theirs.
Commercial CEO Judson Althoff resisted the "Forward-Deployed Engineer" label but confirmed the shape of the move: outcome-driven engineers, sitting on your side of the firewall, wiring Microsoft's models into your workflows and your data. This is not consulting. It is the vendor bringing their own workforce inside your walls — and calling the result your AI transformation.
THE IMPLICATION
The AI Wage Gap just got a new failure mode: the internal team you thought you were building is being quietly replaced by the vendor's team. For two years, every CHRO deck has said the same thing — we will upskill our people, we will build AI fluency in-house, we will own the transformation. Microsoft, AWS, Anthropic and OpenAI have now decided that is too slow, too uneven, and too risky for their revenue targets. So they are shipping the humans with the software. Six thousand of them, in Microsoft's case alone.
The two paths just got sharper.
Path one: your operators build the artifacts — the org-specific prompts, the decision workflows, the model routing rules — and the vendor's engineers become dependencies you manage.
Path two:the vendor's engineers build the artifacts, own the tribal knowledge, and your team becomes the change-management wrapper around someone else's implementation. In path two, the AI Wage Gap doesn't just widen between your top performers and your median — it opens up between your org and the vendor that now understands your business better than you do.
THE MOVE
This week, name ONE workflow inside your org that will be AI-transformed in the next 90 days — and write down, in one page, who owns the artifact when it ships. Not the tool. The artifact: the prompt library, the routing logic, the eval set, the decision guardrails. If the honest answer is "a Microsoft/AWS/Anthropic FDE will build and hold it," you have a Wage Gap problem the org chart is hiding from you. Rewrite the ownership line before you sign the SOW, not after.
The operators who are pulling ahead this quarter are the ones treating vendor forward-deployed engineers as scaffolding, not staff — useful for 90 days, gone by day 91, with the artifact left behind in your team's hands.
🎯 Portfolio Executive Cohort — limited seats.Build the artifact, not the policy →
The Leverage Signal is written by Yuri Kruman: 3x CHRO/CLO, AI trainer at Meta, Microsoft and OpenAI, founder of Portfolio Leverage Co. and author of the forthcoming Closing the AI Wage Gap. Reply to this email. I read every one.
📬 Forwarded this? Subscribe free → One signal, one move, every weekday.