Field notes from the operation.
Working papers on Transfer of Experience and AI agents, shipped by teams running agents in production.
How a Two-Partner Search Firm Booked 16 Meetings in 7 Weeks Without Hiring
171 executives contacted. 37% replied. 16 qualified meetings. Zero messages sent without a human yes. Here is the approval-led system behind it.


A two-partner executive-search firm booked 16 qualified meetings in about seven weeks, from 171 executives contacted, with a 37% reply rate. They did not add headcount. Every message required a human yes before it was sent.
The results are not estimates from a slide. They come from the approval ledger that controlled every send. Here is what AI Jungle installed, why the first weeks still required close partner involvement, and how the correction loop improved the system.
The situation: credible, connected, and out of hours
Every mandate came through the partners' personal network. That network was the firm's most valuable asset and its operating bottleneck.
Pipeline moved only when a partner personally researched a contact, wrote the message, followed up, and booked the call. Both partners also had client work to deliver. Time spent on pipeline reduced delivery capacity; time spent on delivery starved the next quarter's pipeline.
The standard answer was another business-development hire: $120K+ a year for someone senior enough to represent the firm, roughly six months to ramp, and the risk that the accumulated context would leave with the person.
The partners asked a better question: can outreach run without consuming their hours, while still sounding and behaving like them?
What we installed: their judgment, not a generic sequence
We did not deploy a generic outbound tool. We built one agent around the firm's own way of working.
1. Extract the judgment
We worked with the partners to make their invisible rules explicit: how they qualify a contact, which signals matter, what belongs in a first message, and what they refuse to say.
Those rules were written in plain language. The partners could read them, challenge them, and correct them. The system did not hide the firm's judgment inside a black box.
2. Give the agent the work, not the keys
The agent researched approved contacts, prepared drafts in the firm's voice, and organized follow-up. It worked from a contact set the partners controlled. It did not get autonomous permission to send.
3. Put every message through the approval ledger
Every draft reached the partner's phone with three choices: approve, edit, or skip.
Approve sent the message. Edit returned the correction to the workflow. Skip meant not sent. Nothing bypassed that decision.
Across 171 contacted executives, the number of messages sent without human approval was zero. Every send traces back to a recorded yes.
The numbers
| Metric | Result |
|---|---|
| Executives contacted | 171 |
| Reply rate | 37% |
| Qualified meetings booked | 16 |
| Time frame | About 7 weeks |
| Messages sent without human approval | 0 |
The reply rate was not the result of a larger cold list. The agent worked the partners' relationship network and adjacent contacts, using rules extracted from the partners themselves. Their judgment determined who deserved attention; their approval determined what was allowed to leave the firm.
That is why the numbers are verifiable. The ledger connects each sent message to an approval decision, rather than asking the reader to trust a marketing dashboard.
The metric that mattered during the first weeks: edit rate
The first drafts still needed substantial partner correction. That was the initial failure mode: the system could create activity before it had captured enough of the firm's judgment.
The team did not solve that by granting the agent more autonomy. It treated every correction as operating data and fed it back into the readable rules.
By week three, edits had dropped sharply. The agent was not simply producing more drafts. It was converging on the firm's way of selecting, framing, and writing, while the approval gate remained in place.
For client-facing agents, edit rate is a better early trust metric than output volume. A shrinking edit rate shows that the transfer is improving. A flat one shows that a human is still carrying the real work behind the interface.
Why the approval ledger is more than a safety button
The ledger did three jobs at once.
Control. Nothing left the firm without a partner's yes.
Accountability. The operating results could be traced to specific approved actions.
Improvement. Each edit became a correction the system could retain instead of relearning the same lesson tomorrow.
Human approval was not an apology for weak automation. It was the mechanism that made the agent safe enough to use on relationship capital and useful enough to improve.
The comparison with hiring
A hire buys one person's capacity and places the ramp-up in that person's head. The installed system captures the partners' operating rules in a form the firm can inspect and retain.
The point is not that software replaces a business developer. The point is that the firm had a repeated, high-context workload that did not require another person to own every step. The partners kept the judgment calls; the agent carried the preparation and repetition around them.
That is the practical meaning of grow without hiring: not removing people from the business, but adding capacity without putting every additional unit of output on another payroll line.
Could you build this yourself?
Yes, if the firm can commit to four disciplines:
- extract the unwritten judgment before automating the workflow
- keep a real approval record for every client-facing action
- turn corrections into persistent rules
- assign an operator who remains accountable after launch
The models are available to everyone. The difficult part is transferring experience into a system and operating the correction loop until the output earns trust.
FAQ
Does the AI send messages by itself?
No. Every message requires explicit approval from a partner. In this engagement, zero messages went out without a recorded human yes.
Why was the reply rate 37%?
This was not anonymous mass outbound. The system worked from the partners' relationship network and approved adjacent contacts, using their selection rules and voice.
How quickly did the drafts improve?
The partners corrected drafts heavily at the start. By week three, the edit rate had dropped sharply because the corrections were being transferred back into the rules.
What does an engagement like this cost?
AI Jungle starts with a $999 Leverage Audit, credited toward the install. A First Agent Install is $9,500 fixed. Ongoing partnerships start at $5,000 per month plus performance where attribution is honest. Current terms are maintained on our pricing page.
What happens if the partnership ends?
The goal is transfer, not lock-in. The firm's rules, operating history, and approval record remain part of the system built around its work.
This firm added business-development capacity without adding headcount, while keeping a human decision in front of every message. If your firm's growth still depends on work only the owner has time and context to do, start with the AI Jungle Assessment.