Confidential — Meeting Prep Wed 5 Mar 2026
Strategic briefing

Coopers Meeting
Playbook

What to say, what to protect, and what to ask. A field guide for David's exploratory meeting.

Confidential David Caggiari-Pallett Coopers (recruitment) Exploratory meeting
The situation

Competitors who could be partners.

Coopers are Yoni's collaborators in the recruitment space. They're colleagues, potential partners, but also competitors. This meeting requires surgical precision on what to reveal.

David has a real competitive advantage — an AI operating system that multiplies his productivity. The goal is to explore partnership without giving away the recipe.

The meeting is exploratory. No deals, no commitments, no technical details. Just positioning and listening.

Critical: Align with Yoni first

Yoni already uses the same system. If Coopers talks to Yoni after your meeting, Yoni might reveal details. Before Wednesday: ask Yoni directly what Coopers knows and what he's told them.

If Yoni has already shared details → calibrate accordingly. If Yoni has said nothing → you're free to play the "proprietary system" card.

Your positioning

Show the what, never the how.

Coopers doesn't need to understand the technology. They need to understand that you've solved a problem they're still thinking about.

Rules of engagement

The line between intriguing
and giving it away.

Say this
  • "Proprietary AI system" for recruitment professionals
  • "Validated on myself" — real results, real productivity gain
  • "Knowledge partner", not a chatbot — it learns your business
  • Show polished outputs (reports, strategies, analyses)
  • "Looking for commercial partners", not tech partners
  • "Replicable across verticals" — tested on 6+ different professional profiles
Never say this
  • Never name ABChat, Claude, brain, workspace
  • Never show the interface or terminal
  • Never mention the architecture (markdown, folders, tmux...)
  • Never reveal your tech provider exists as a single person
  • Never say "it's easy to replicate"
  • Never discuss open source components
Meeting structure

Three phases, stay in control.

Phase
1

Listen first

Opening

"Tell me what you're working on."

Let Coopers talk first. Understand their pain points, their AI strategy (if any), their clients' needs. The person who asks questions controls the room. Gather intel before revealing anything.

Phase
2

Drop the hook

Core

"We've already solved that."

When they mention AI challenges or productivity issues, casually mention you've built something that works. Show results, not methods. If they lean in, you're winning. If they don't, you've lost nothing.

Phase
3

Close with a question

Exit

"Would your clients pay for this?"

Don't close with a pitch. Close with a question that makes them think about you after the meeting. "If this worked for your client base, what would that look like?" Leave them wanting more. Schedule a follow-up only if they ask for it.

IP Framework

The guitar and the song.

David's metaphor is perfect for internal use. Here's how it translates for external conversations:

Platform IP ABChat is Giobi's. The instrument.
Content IP The vertical solution is yours. The music.
For Coopers "Proprietary WorkTech platform + our recruitment expertise."
Legal detail Premature. Discuss only if they propose a concrete deal.
The real defensibility

IP in the traditional sense (patents, proprietary code) is weak here and that's fine. The real moat is execution: 6+ active brains across different verticals, a validated onboarding process, and a track record of "the best working days I've ever had" from the first non-technical user.

For Coopers, the message is simple: we have a working product, validated users, and replicable deployment. They can be a distribution partner or they can watch from the sidelines.

Intelligence gathering

Questions that extract value.

Every question you ask is information you get for free. Every answer you give is information they get for free. Optimize the ratio.