Split builder/operator voice in outreach case study

Keep first person for the engineering decisions (I built, I checked,
I gave the AI a stake), switch to generic third person for the
operational description of who runs the system day to day (by hand,
one can write... the operator out of the loop).

Author: IntellyCode

case-studies/ai-delegation-outreach.html

@@ -208,7 +208,7 @@
 
           <h1 class="article-title">Building an AI Agent You Can Trust to Act on Your Behalf</h1>
 
-          <p class="summary"><strong>Getting an AI to generate things is easy. Getting one you can trust to act on your behalf, unsupervised, is the hard part, and it is an engineering problem more than a prompting one. I built such a system for personalized cold outreach, where a single mistake lands in a stranger's inbox with my name on it. By hand, I could write maybe 50 personalized emails a day. The system now runs until it hits the email provider's send limit, around 400 to 500 a day, at the same personalization and the same reply rate, with me out of the loop.</strong></p>
+          <p class="summary"><strong>Getting an AI to generate things is easy. Getting one you can trust to act on someone's behalf, unsupervised, is the hard part, and it is an engineering problem more than a prompting one. I built such a system for personalized cold outreach, where a single mistake lands in a stranger's inbox. By hand, one can write maybe 50 personalized emails a day. The system can now run until it hits the email provider's send limit, which is ten times higher than that, at the same personalization and the same reply rate, with the operator out of the loop.</strong></p>
 
           <p>Most people use AI as a thing that hands work back to them. You ask it to write something, summarize something, or answer a question, and you are sitting right there to read what comes back and catch the mistakes before they matter. That is the easy half. The hard half is handing an AI a real task with real consequences and walking away, trusting it to run on its own with nobody reading every line before it leaves. That is the difference between a tool that drafts and an agent that acts, and the second one is where most people get it wrong.</p>
 
@@ -244,9 +244,9 @@ <h1 class="article-title">Building an AI Agent You Can Trust to Act on Your Beha
 
           <p>It is spam precisely when there are no rails. The AI runs unchecked, the content is generic, the facts are made up, and nobody stands behind any of it. That is the exact failure I spent the whole build trying to prevent. What this system does is the opposite. Every email is personalized and built on real, validated information about the actual person and company, not invented. There are real stakes wired into how it reasons. And the framing is not an AI off on its own, messaging the world as it pleases. It is a person handing a bounded, well-defined task to an AI that can do it reliably and faster, while faithfully carrying the intentions of the person it acts for. The line between this and spam is the same as between an agent you can trust and one you cannot.</p>
 
-          <p>So what happened in the end? By hand, I could write no more than about 50 personalized emails a day. With the system running, the limit is no longer me. On a full day, it runs until it reaches the email provider's send cap, somewhere around 400 to 500 emails, each researched and personalized for its recipient. The bottleneck moved off me completely.</p>
+          <p>So what happened in the end? By hand, one can write no more than about 50 personalized emails a day. With the system running, the limit is no longer the operator. On a full day, it runs until it reaches the email provider's send cap, somewhere around 400 to 500 emails, each researched and personalized for its recipient. The bottleneck moves off the operator completely.</p>
 
-          <p>And that is the real result, which is not really about email at all. The shallow work now runs on its own at machine speed, reliably enough to leave alone, which frees me to focus on the deep work that actually creates something.</p>
+          <p>And that is the real result, which is not really about email at all. The shallow work now runs on its own at machine speed, reliably enough to leave alone, which frees the operator to focus on the deep work that actually creates something.</p>
         </div>
       </article>
     </main>