Zapier vs foundation model
Two different tools for two different jobs. Zapier is deterministic — same trigger, same steps, same output every time. A foundation model is non-deterministic — every output drifts. The boundary is "small tasks with clear objectives."
What it does (the operator translation)
Zapier listens for a trigger and runs a fixed chain of steps. New Zillow lead, send SMS, log row in a sheet. Same trigger this Tuesday, same trigger next Tuesday — the steps execute identically. Determinism is the feature.
A foundation model is the opposite. Hand it the same prompt twice and you get different drafts. That's the feature for creative work — listing copy, follow-up text, sphere ranking — and the bug for invariant work. You don't want your "new lead → SMS" path to drift.
Yan, Husain et al. in Part I of What We Learned from a Year of Building with LLMs make the boundary explicit: "Small tasks with clear objectives make for the best agent or flow prompts." Part III on strategy adds the operator rule: "Don't buy SaaS for what an LLM can do." The two halves of the boundary.
The clean rule: deterministic plumbing belongs in Zapier or Make.com. Drafting, ranking, summarizing, voice-matching belong in the foundation model. Confuse the two and you either get drift in your routing or wrappers in your drafting.
Why a working REALTOR cares (the breakpoint)
For a 12-deal agent below all three workflow thresholds, the foundation model covers it. Above 30 sides, $500 in paid leads, or a second human on the file — wire three deterministic Zaps for the routing and keep the model for the drafting. Two tools, two jobs.
What this is NOT (the category-flip)
Foundation models are NOT a Zapier replacement. They're a draft-and-think replacement. The vendor pitch that conflates the two — "AI automation that handles everything" — confuses the determinism boundary the underlying research is explicit about.
Related terms
Workflow automation · Phone-first workflow · AI agent · LLM agent
Where this comes up in The Listing Machine
The determinism boundary anchors the Workflow Automation pillar. The Listing Machine teaches both halves — the three Zaps to wire and the phone-first prompts that replace the rest of the wrapper stack.