ZeroNoise Logo zeronoise
Post
Zapier, Ramp and Replit rebuild around agents as the PM work shifts to deciding what to build
•
4 min read
• 295 docs
Operators at Zapier, Ramp and Replit describe products and teams rebuilt around agents, and Postman reports PMs prototyping instead of writing PRDs. Also: a context-sharing argument for AI workflows, a free-tier pricing case study, and a viral-sharing test.

Three operators on rebuilding around agents

Zapier. Wade Foster says Zapier MCP is now Zapier's fastest-growing area. Users install it in the agent they already use, and the agent builds their automations in code. He calls Zapier "a code-based product now, even though the users aren't" . His test for an agent-first product: find what agents are still bad at that the models and harnesses won't fix. Then build a tool that an agent can sign up for, buy and use the way a person would . On cost, he tells customers to have the agent build a workflow rather than act as one. Deterministic Zaps run about 71% cheaper in some benchmarks than an agent that reasons from scratch on every run . His view on competing with the AI labs: the best companies quickly drop experiments that new models make pointless .

Ramp. Ramp counted 7,000 pull requests from non-engineers in Q2, mostly from its customer-experience team. Two years ago that number was "functionally zero" . The speaker contrasts this with the usual path, where a ticket goes from PM to designer to engineer and ships two months later, if it isn't marked "won't fix" . Ramp says its MCP usage is growing about 10% per week, and it began onboarding customers to its Glass harness this week .

Replit. When vibe-coding competitors spent heavily on ads, Amjad Masad chose "unsexy" enterprise work instead. Replit asked customers like American Express what would make them comfortable building mission-critical apps on it, and that enterprise business has compounded . With agents handling task-level work, he says staff now spend more time with customers and on "what's worth building" .

The common thread: agents are becoming customers for PMs to design for, as well as tools that change who on a team ships.

The PM role: prototypes over PRDs

Aakash Gupta passes on Postman's founder saying that PMs there are "building APIs and prototyping in Claude instead of writing PRDs," and that designers ship PRs through Cursor. Gupta calls it a harder job that needs taste and technical instinct . Market data points the same way. Juicebox's data on recruiter outbound searches shows falling demand for software engineers, rising demand for PMs and faster growth for AI engineering. Design hiring is down 20% year over year. Lenny Rachitsky says this matches his own job-market report . Gupta's Levels.fyi analysis covers 5,013 PMs and 47,318 engineers. PMs start $25K behind engineers in pay, catch up around year 8 ($256K vs. $260K) and earn more after year 12 .

Context is built through the work

In TBM 452, John Cutler lists ways context-sharing fails even among competent people. Experts can't put tacit judgment into words, the people asking can't say what decision they're trying to make, and clarifying questions come across as tests of competence . He questions the hype around "giving AI context." Instead of making ever more knowledge machine-readable, he suggests designing AI that builds context the way people do, through collaboration, observation and doing the work together .

A thread where PMs asked how to get better at prompting landed in a similar place. The top reply calls poor results "a clarity of thought issue," not a prompting problem . Another commenter warns that too much context, or outdated context, can ruin a session . A third keeps a doc tree on how their systems work that the agent reads. The agent researches and records what it finds before it writes any ticket, so each new chat doesn't start from zero .

Pricing: high conversion hid one-time demand

A music-library transfer app found that its free limit converted well, but most subscribers cancelled after their one transfer. After a decade of flat revenue, it made basic transfers free and now charges only for auto-sync and playlist tools. Revenue "dropped significantly" . One reply argues that a flat per-transfer price would have kept the one moment users clearly paid for . Another says to pick leading signals now, such as second-month return rates and sync conversions, and set a date to review them .

Sharing that actually spreads

In an r/startups thread, one commenter offers a test for viral sharing: can the person who receives the shared item get value in under a minute, and is your app the obvious way to get more? Quizlet study sets pass. Streaks mostly help retention, not acquisition . Another suggests measuring how many recipients open a shared result without signing up. If almost none do, the share "is just noise" .

Zapier, Ramp and Replit rebuild around agents as the PM work shifts to deciding what to build