Make money doing the work you believe in

Prompting in 2025 vs 2026 is not the same skill. At RevOps AF this week I'll discuss the Future of AI and RevOps. Here's what I believe has changed:

๐—–๐—น๐—ฒ๐˜ƒ๐—ฒ๐—ฟ ๐—ฝ๐—ต๐—ฟ๐—ฎ๐˜€๐—ถ๐—ป๐—ด โ†’ ๐—ฆ๐˜๐—ฟ๐—ฎ๐˜๐—ฒ๐—ด๐—ถ๐—ฐ ๐˜€๐˜๐—ฟ๐˜‚๐—ฐ๐˜๐˜‚๐—ฟ๐—ฒ

2025: find the magic words

2026: design the reasoning path step by step so the model doesn't have to guess

๐—ข๐—ป๐—ฒ ๐—ด๐—ฟ๐—ฒ๐—ฎ๐˜ ๐—ฝ๐—ฟ๐—ผ๐—บ๐—ฝ๐˜ โ†’ ๐—” ๐˜€๐˜†๐˜€๐˜๐—ฒ๐—บ ๐—ผ๐—ณ ๐—ฝ๐—ฟ๐—ผ๐—บ๐—ฝ๐˜๐˜€

2025: the single brilliant prompt was the goal

2026: interconnected instructions across agents, with frameworks like Context โ†’ Task โ†’ Constraints โ†’ Output holding the whole thing together

๐—–๐—ผ๐—ป๐˜ƒ๐—ฒ๐—ฟ๐˜€๐—ฎ๐˜๐—ถ๐—ผ๐—ป โ†’ ๐—”๐—ฟ๐—ฐ๐—ต๐—ถ๐˜๐—ฒ๐—ฐ๐˜๐˜‚๐—ฟ๐—ฒ

2025: prompt engineering

2026: intent orchestration, where you're defining how an agent thinks, not just what to ask it

๐—ก๐—ฎ๐˜๐˜‚๐—ฟ๐—ฎ๐—น ๐—น๐—ฎ๐—ป๐—ด๐˜‚๐—ฎ๐—ด๐—ฒ ๐—ผ๐˜‚๐˜๐—ฝ๐˜‚๐˜ โ†’ ๐—ฆ๐˜๐—ฟ๐˜‚๐—ฐ๐˜๐˜‚๐—ฟ๐—ฒ๐—ฑ ๐—ฐ๐—ผ๐—ป๐˜๐—ฟ๐—ฎ๐—ฐ๐˜๐˜€

2025: hope the response looks right

2026: the output is JSON, treated like an API response, because unstructured text breaks workflows the second the model's phrasing shifts

๐—ข๐—ป๐—ฒ ๐—บ๐—ผ๐—ฟ๐—ฒ ๐˜๐—ต๐—ถ๐—ป๐—ด:

Prompts are living documents now. They drift. Models update. Use cases shift. The practitioners building durable systems are versioning their rubrics like specs, not writing them once and walking away.

May 6
at
4:37 PM
Relevant people

Log in or sign up

Join the most interesting and insightful discussions.