Protexxa X Enquire AI 2.0
Ting Zhou + Rick Huijbregts
28 July 2026, 14:30 UK / 9:30 ET
Teams
Collect the overdue answer. Unblock the engine. Open the real conversation.
Rick promised "one concerted response" on 21 July and went silent six days ago. The campaign has not produced a single new reply in eight days, the seat runs out of names this week, and the widened targeting you are on record requiring sign-off for has never been approved. Settle those three things in the first twenty minutes, then use Ting's own 2.0 framing to book the working session for the Protexxa-level build.
Pre-flight
Before the call
The invite time does not match what was agreed in writing. Trust the invite.
- Where: Microsoft Teams, meeting ID 219 266 311 489 405, passcode zu74J9j8. Organizer Ting.
- Time trap: Ting agreed "10 to 10:30 AM ET" in writing on 23 Jul, but her live invite says 9:30 to 10:00 ET, which is 14:30 UK. Join at 14:30 UK. If the room is empty at 14:40, message Ting; keep 15:00 to 15:30 UK clear as spillover.
- RSVPs: Dan accepted. Ting accepted. Ben and Rick both still needsAction. Rick has not written a word since 22 Jul. His no-show is a live risk; if he skips, hold the engine items with Ting and put the response question to Rick directly for a dated answer.
- Ben decision, settle before 14:20: Dan wrote on 21 Jul that Ben is stepping back from this account. Ting then named Ben into the 2.0 roster and negotiated the slot with him. Decide deliberately whether Ben joins. The 2.0 reset argues yes; just do not drift into it.
- Matt Fisch is not invited, per Ting's own line: "Our next meeting will be without Matt. I'll schedule a separate meeting for him under Protexxa." Respect the boundary; he is still the only connected seat and still executes any follow-up you agree today.
- Deck already in their hands: protexxa-ting.enquirerconsulting.com (also aliased as netzzar-protexxa). No pricing on it. It maps the exact build you will propose.
- The map to share on screen: protexxa-buyer-map.enquirerconsulting.com. Live Reachable Buyer Map: 3,000 to 3,500 CISOs at US 1,000+ orgs vs 20,000+ wider security leadership (six times the room), 20,000+ security-owning CIO/CTOs, vertical bands for financial services, healthcare and higher ed. Bring it up when you ask for the aperture sign-off. Prospect-safe and breach-clean.
- The pack was sent. Report, lead CSV, workflow, playbook, plus the v2 correction, all delivered 20 Jul. You can reference "the report we sent you" safely. Positives figure: say 27, per the v2 correction.
Live numbers, read this morning
The scoreboard
Press B before any screen share. Speak these calmly; they argue for you.
Since the 20 Jul call: the engine ran, nothing else moved
- Invites: 782 lifetime, up 210 since 20 Jul. Accepts: 84, 10.7 percent lifetime, and only 8.6 percent on the newest 210. The narrow CISO/CIO aperture is still live and still decaying.
- Replies: stuck at 8. Zero new prospect replies in eight days, on 210 fresh invites and 238 sequence messages. Every inbound in the window was a vendor, a recruiter or a sponsorship pitch.
- Lead stock: 117 names left as of last night, below the 200 floor, burning roughly 27 a day. The only live seat runs dry inside a week. This is why the aperture decision cannot wait another cycle.
- The aperture evidence, era level: the wide-targeting era accepted at 20.6 percent. The client-directed CISO/CIO narrowing accepts at 11.5 falling to 10.7. Same engine, same weeks, ECG's own wider campaigns ran 15 to 34 percent.
- Relationship totals: 2,362 invites, 434 accepts, 60 replies, 27 positives, 1 meeting held, and that meeting was a personal friend. The gap has never been the door opening. It is what happens after.
- Follow-up truth (from the 21 Jul audit, unchallenged in writing): of 27 positives, 26 had no chase, 20 had nothing since 18 June, no CRM was used. Rick already owned this on the 20 Jul call: "the follow-through is on us."
The paper trail
Where things stand, in their words
Every quote below is from email, verbatim, unchallenged since.
What they said
- Rick, 20 Jul call
- "The follow-through is on us." "You wouldn't do that for $900 a month, this is a different scope we need to understand."
- Rick, 22 Jul
- "My apologies to you and Ben. Please leave this with me. I will be the one following up with you on next steps. Please, for now, ignore any other comms from the rest of the team."
- Ting, 23 Jul
- "I genuinely believe we're now on much stronger ground... Netzzar X Enquire AI 2.0 ( Rick + Ting + Dan + Ben )."
- Matt, 21 Jul
- Escalated ("Please call me right now... Or maybe we shut it down"), then conceded by evening: "As we converge on a proper or fair definition of a qualified lead, we are fully in agreement."
What is on the table, unanswered
- Dan's ask, 21 Jul
- "Please confirm which option Netzzar is choosing." Option 1: ECG owns targeting and messaging within the agreed brief, Netzzar owns every positive-reply handoff, CRM entry and chase. Option 2: Netzzar dictates targeting and messaging in writing and owns the consequences. Six days, no answer.
- Aperture gate
- Dan, in writing, twice on 20 Jul: nothing goes out until the widened targeting is agreed. No written approval exists. Rick's campaign build is blocked behind it.
- Rick's seat
- Sanctioned openly on 20 Jul. The connect link expired 25 Jul, unused. Workspace still shows exactly one seat: Matt's.
- Their commitments, 20 Jul
- HubSpot import of the 59-row lead CSV (never confirmed), re-warm the positives, a claim-and-call owner. None confirmed done.
- Contract truth
- $900 per month per seat, up to two seats, six-month minimum to roughly 22 to 23 October, monthly rolling after. No renewal cliff. Asserted in writing 21 Jul, unchallenged.
Minutes 0 to 20
Run the agenda, in this order
Warm, brief, then the question. Silence after it. Do not fill it.
Rick, good to see you. Before we get into this week: you said you'd come back to us with one concerted response on next steps. Where did you land?
Then stop. Whatever comes back, anchor it to the two options. If Rick is absent, put the same question to Ting as carrier of the 2.0 reset, and get a date for Rick's answer.
Restate the choice cleanly if the answer is vague.
"Option one: we own targeting and messaging inside the brief we agree, and your team owns every warm handoff, the CRM entry and the chase. Option two: you specify targeting and messaging in writing, and own the results. We recommend one. Which is it?"
A decision, or a date for one
The numbers, thirty seconds, no blame.
"Since we spoke: 210 more invites, zero new replies. Same narrow targeting, same result. The wide targeting accepted at twenty percent, the narrow runs at ten and falling. Nothing about the engine changed. The aperture did."
Agreement that targeting is the variable
Ask for the aperture sign-off on this call.
"You have my written commitment that nothing goes out until targeting is agreed. I need that agreement today: every title that owns human risk, VPs and directors of security, heads of information security, security-owning CIOs and CTOs, not only CISOs. The seat runs out of names this week."
A yes on the widened brief
Rick's seat, two clicks, while everyone is here.
"Rick, your seat link expired before you could use it. We'll send a fresh one right now, it is two clicks, and your campaign gets built on the widened targeting we just agreed. It stays staged until you approve the copy."
Link clicked, or a hard commit today
Their three commitments, an owner and a date each.
"Three things from the 20th sit with your side: the HubSpot import of the 59 leads we sent, re-warming the 27 positives, and a named owner for claim-and-call. Who owns each, and by when?"
Names and dates, not intentions
Checkpoint before the bridge
"So agreed: widened targeting live this week, Rick's seat connecting, and your side owns the follow-up rhythm. Then let's talk about the bigger question Ting raised."
Minutes 20 to 30
The 2.0 bridge, in Ting's own frame
She asked for this conversation in her 16 Jul strategy-session note. She signs VP Marketing. She is the buyer.
Ting, you called this 2.0, and you asked how we demonstrate the value of the lead generation, showcase measurable customer success, and turn those stories into more opportunities. Honest answer: the engine opens the right doors, but every conversation lands on a site that hasn't moved since 2024, no published customer proof, and wins that live in people's heads. Rick said it on the twentieth: that isn't a nine-hundred-dollar-a-month problem. It's a build.
The build, as the deck already maps it
- A website that sells Defender: rebuilt around the security buyer, proof first, a booking path that does not leak, wins published the week they happen.
- The Defender AI brain: offer, proof, buyer profiles, voice and campaign learnings in one operating layer, for every seller on both teams. The layer we run our own business on.
- A proof engine: customer success captured on video and in writing, measured monthly, amplified, and fed back into outreach.
- The handoff structure: claim-and-call with named owners, a reply desk that never sleeps, a weekly scorecard from requests to revenue. We run exactly this on our own pipeline.
The ask, the only close that matters today
The next step is a working session, the four of us, where we map Protexxa's weak points against the next two quarters. After that we present the exact build live, and you decide with the full picture. Can we put forty-five minutes in the diary this week or early next?
Internal only
Offer shape and anchor handling
Press B before any screen share. No number is said today, in any direction.
Hold the frame on money
- Rick self-anchored "around $20k" on the 20 Jul call. Do not accept it, do not argue it. The line: "Scope first. We'll bring the exact build and the number to the session, and we present it live."
- The shape this maps to: a fixed four-month Build Run Own engagement (site, AI brain, proof engine, handoff structure), then an optional managed-service layer. The internal four-month build anchor applies; components can narrow the scope, and the number moves with the work, never the price for the same build.
- The AI brain alone has a smaller monthly-shape comparable from the software side of the book. If they flinch at full scope, phase it: proof engine and handoff first, site and brain behind it. Scope moves, price per scope holds.
- Never fold the $900 engine work into the build number. The engine seats are the existing contract. The build is new scope on top.
- Context hygiene: today you book the session. The scope and the number get built in their own working session and presented live. Not on this call, not in email.
Language rails
Say this, never that
The breach ban is Matt's explicit legal instruction from 20 Jul. It binds everything external.
Never the word "breach". Ever.
Approved framings: visibility into employee exposure, credential exposure, dark web risk, human-layer risk, what a scan might show. "We give visibility, we never claim detection of a breach."
Proof organizations: five names only
Gwinnett County Schools, RxVantage, Scotiabank footprint, Bell Canada, Sobeys. Always attributed to the Protexxa Defender platform, never to Netzzar. No other organization gets named, ever.
Titles: get them right
Rick is Protexxa's COO (and EVP Learning, runs Cyber Nations). He is not Netzzar's CEO; the Netzzar contract was signed by their CEO Martin per Ting's own April email. Ting signs Vice President, Marketing, and has since April. Claudette McGowan signed the service agreement as Netzzar's counterparty in her Chief Strategy Officer capacity.
Contract facts, if raised
Six-month minimum from late April, so the term runs to roughly 22 to 23 October, monthly rolling after with 30 days notice. The "9 days remaining" banner Matt once quoted was the platform trial, not the contract. Say it without triumph.
Positives count
27, per the v2 correction they received on 20 Jul. If anyone says 25, the correction added three replies the platform had not surfaced.
If email deliverability comes up
You warned in writing on 21 Jul that data-security copy is a spam magnet. If, and only if, their own sending comes up: their test blasts from netzzar.net, netzzar.co and netzzarhq.com landed partly in spam in our own inboxes. Offer help, not criticism.
Information discipline
Hold back
Press B before any screen share.
Do not say these
The client's entire outreach and follow-up capacity is one person and one seat, and that person's attention is visibly elsewhere right now. Push for structure, owners and the second seat. Never the personal detail. Specifics are in chat, deliberately not on this page.
netzzar.com is a half-converted template with junk pages still live. It is evidence the channel has no marketing engine, and a future workstream. If it comes up, it is an opportunity, not a joke.
Protexxa's public org page looks stale on marketing leadership. If marketing ownership comes up, ask who owns it now. Never name-drop a departure you cannot prove.
Matt escalated, Rick apologised, Ting reset it. The reset is your asset. One backward-looking sentence maximum, then forward.
The historical data lives in the delivered report and CSV. The portal shows the live canonical numbers. That boundary was Dan's own 20 Jul decision.
No number today. The anchor conversation happens live, at the session, against the mapped scope.
Last five minutes
Close on the session, with owners and dates
Do not leave with "we'll regroup internally" again. That already cost six days.
Say the whole agreement back before goodbye.
So today: targeting widens this week and I'll confirm the brief in writing. Rick, the fresh seat link is in your inbox, two clicks. Your side owns the HubSpot import, the re-warm of the 27, and claim-and-call, with the owners we just named. And we're booked for the working session on [day] to map the Protexxa build, where we'll present the full picture live. Anything I've got wrong?
After the call: post a Note to the Netzzar Account in EspoCRM, and if the rescope advanced, create the RC- engagement card (none exists today, the account has no ECG pipeline record). Then the widened-audience build and the stock refill, gated on the sign-off you just won.