A working brief for Cinthia, Maya and Coley
You only pay when qualified meetings land
More accounts like SoftBank.
1:1 named-account campaigns for every CISO, Head of AI Security, AppSec and Platform buyer. Produced by my autonomous ABM engine.
Prepared for Cinthia Portugal, VP of Global Marketing; Maya Kamoshita, Director of Revenue Marketing; Coley Burke, Head of Global Sales.
From Andy Wool, Cambridge, UK. Formerly Global ABM, SentinelOne; Senior Marketing, Sophos. You pick 10 Tier-1 accounts in 20 minutes. Kits ship in days, not a quarter.
Not an official Zenity page. Produced 1:1 by my autonomous ABM engine.
Why this brief exists
You have the category. We’ll generate more clients like SoftBank.
On 3 August 2026 you announced a $125M Series C led by Norwest — to accelerate platform innovation, expand Zenity Labs, and deepen presence in Europe and Asia Pacific. Gartner, 17 April 2026: “Zenity Is the Company to Beat in AI Agent Governance.” Norwest: “The agent is the new perimeter, and the perimeter needs a platform of its own.”
What is already true
- Purpose-built for AI agents. Intent-aware. Deterministically allow / modify / block before the action occurs.
- Unified layer across Microsoft Copilot, ChatGPT Enterprise, Gemini, Claude, Codex, Cursor, custom agents in AWS Bedrock/AgentCore, Microsoft Foundry, Google Vertex AI.
- Revenue tripled in each of the past two years; on track to triple again this year. (Company PR. No ARR cited here.)
- Majority Fortune 500 / Global 2000; longest-standing include many Fortune 50. Named customer: SoftBank Corp.
- Labs is loud: AgentFlayer; PleaseFix at Black Hat; Copilot Studio research. The named-account layer is what I produce.
What I produce for you
- 1:1 campaigns into CISO / Head of AI Security / AppSec / Platform committees — per named account.
- Coverage for hunters walking into F1000 committees in the US, Europe and Japan.
- The same quality you are reading now, at scale, in days, not a quarter.
- You only pay when qualified meetings land. Not on content produced. Not a retainer.
Commercial model
You only pay when qualified meetings land.
20 minutes. 10 of your actual Tier-1 accounts. HubSpot stays yours.
Per named account
The kit you are holding. Then ten more.
This page, the companion landing, the ads, the emails, the outreach: produced by my autonomous ABM engine for Zenity. Same treatment for each account you name in the working session.
Landing
A 1:1 page in the account’s language. The Zenity page is the quality bar.
Ads + email
LinkedIn and display, split by persona. Five-touch email, first touch under 130 words. Role-split, not a blast.
Outreach + brief
Connection notes, InMails, a voice-note script the AE can actually send. A PDF someone inside the committee can forward without rewriting.
Cinthia · LinkedIn
“I've said it for a while now. The AI security challenge is no longer what AI generates. It's what AI agents decide and do.”
That line belongs in every named account — in front of the CISO, Head of AI Security, AppSec and Platform buyer — not in a generic campaign. My autonomous ABM engine puts it there, 1:1.
Cinthia, Maya, Coley — this is for you
Category. Meetings. Coverage.
Cinthia Portugal
VP of Global Marketing. Seattle.
Category leadership in every named account, not a generic campaign. The story you already tell security leaders becomes 1:1 for the four people who sign.
Maya Kamoshita
Director of Revenue Marketing. Seattle.
Meetings and pipeline after inbound. You already proved the website can book. I produce the named-account layer that turns a target into a qualified meeting. HubSpot stays yours.
Coley Burke
Head of Global Sales. New York.
Coverage for the hunters walking into F1000 committees in the US, Europe and Japan. A full kit per named account. You only pay when qualified meetings land.
The committee your AEs sell to
CISO. Head of AI Security. AppSec. Platform.
My autonomous ABM engine writes 1:1 for each — not one generic page for “security leadership.”
Public partners on the map: Microsoft, AWS, OpenAI, Salesforce, ServiceNow; VARs AHEAD, Trace3, Carahsoft; SIs Slalom, TCS, Genpact, Orange CyberDefense. A Microsoft or GSI motion arrives as a 1:1 campaign into a specific account’s committee — not a co-branded PDF.
FedRAMP In Process. Public sector via Carahsoft. Industries you name: financial services, healthcare, pharmaceuticals, technology, energy, manufacturing, highly regulated.
New pipeline. Faster deals. Expansion.
What the kits are for.
Pipeline
New named accounts
Hunters walking into F1000 committees in the US, Europe and Japan. A full 1:1 kit they can send in week one. Replies land in HubSpot the way you already run inbound.
Velocity
Open F1000 deals
Multi-thread the four-persona committee. Kill “wait for Microsoft” per tenant: Copilot Studio inline GA Nov 2025; Foundry runtime inline GA 17 Mar 2026; Agent 365 GA May 2026. Labs research is the 1:1 proof layer, not a spray campaign.
Expansion
Fortune 50 / 500
SoftBank-class logos. As Norwest wrote: Fortune 20 tech — 90% of vulns remediated with 2 FTEs, tenant +280%; Fortune 50 FS — 80% risk reduction across 150,000+ resources, agent volume +180%; Fortune 200 consulting — 90% fewer violations, 95% of high-risk cases auto-remediated. Those are expansion 1:1s.
Coley · LinkedIn, Series C
“This funding is fuel to close the gap between how fast enterprises are deploying agents and how ready they are to secure them.”
The GTM rhyme is the same: agents are in production; 1:1 named-account campaigns put you in front of the committee that has to secure them. You only pay when qualified meetings land.
Example 1:1 · generic Fortune 1000 bank · not a live prospect
A Fortune 1000 bank rolling out Copilot Studio + custom agents.
This is what my autonomous ABM engine would produce as the spine of a 1:1 kit. Labelled so it cannot be mistaken for a live account plan. No real bank is named. The shape is the point: committee split, Microsoft objection, Labs proof, partner path, HubSpot stages.
Account hypothesis (example)
A US-headquartered Fortune 1000 bank. Wealth, commercial, and a growing developer platform. Microsoft 365 Copilot in production for knowledge workers. Copilot Studio in a controlled roll-out for operations and servicing. A small platform team standing up custom agents on Azure AI Foundry and a second experiment on AWS Bedrock. AppSec is already in the ticket stream; there is no titled Head of AI Security yet — the CISO’s deputy is wearing it. NIS2-class reporting anxiety in the European subsidiary. Board has asked for “agent inventory” without a system of record.
Why Zenity, in their language
Not model safety. Not prompt filtering. Intent: what the agent is allowed to decide and do. Deterministic allow / modify / block before the action hits core banking, servicing, or the document store. One layer across Copilot, Copilot Studio, Foundry, Bedrock — so the bank does not buy a different control for each lab. SoftBank Corp is the only named customer this kit will use; expansion proof for a bank 1:1 should come from Norwest’s Fortune 50 FS diligence (as Norwest wrote), not from invented logos.
| Persona | The 1:1 page says | Proof layer |
|---|---|---|
| CISO | Agents are already deciding. Governance, visibility, control without freezing the bank’s AI programme. | Cinthia’s line, in their language. Gartner “company to beat.” EU AI Act / NIS2 on the European book. |
| Head of AI Security (or deputy) | Intent-aware detection. Allow / modify / block. Not a dashboard of prompts after the fact. | AgentFlayer zero-click class; PleaseFix across agentic browsers; Copilot Studio research. |
| AppSec | Studio apps and custom agents as an application surface: connectors, tools, over-permissioning. | Poisoned document → Drive/SharePoint exfil. Copilot Studio vuln. Inline Studio GA already in market. |
| Platform | One control plane across Copilot / Studio / Foundry / Bedrock. Marketplace procurement. | AWS Security Hub extended / Marketplace; Azure; Agent 365 as the “wait for Microsoft” objection, answered per tenant. |
Example 1:1 continued · still not a prospect list
What actually ships for that bank.
Assets I would return
- A 1:1 landing page for the bank’s committee (the Zenity page you already have is the quality bar).
- Four ad tracks, one per persona, plus a partner variant if Microsoft or a GSI is already in the account.
- A five-touch email sequence, first touch under 130 words, split by persona — not a single “Dear Security Leader.”
- AE outreach: connection notes, InMails, a 30-second voice-note script a hunter can actually send.
- A hero brief someone inside the committee can forward to the CISO without rewriting.
HubSpot: replies land as S0/S1 the way you already run inbound. Fields the AE has to fill anyway: metrics (agent inventory, over-permissioned tools), the CISO as signer, decision criteria (intent / inline block), decision process (four-persona + procurement), paper process, who else has to say yes, competition (including Microsoft as stall).
The Microsoft stall, written per account
Every AE will hear it. Copilot Studio inline is GA. Foundry runtime inline is GA. Agent 365 is GA. M12 is in the cap table. The 1:1 does not bash Microsoft. It draws the line the platform already draws: Microsoft is the estate; Zenity is the intent-aware control plane across Copilot and the custom agents that will not live only in Foundry. Partner path: Microsoft + the SI already in the bank — enablement → account mapping → joint customer marketing → in-person activation.
Clock and commercial
A real kit ships in days, not a quarter. You only pay when qualified meetings land — not on this content. No real bank is named here. Norwest diligence numbers are not this bank. SoftBank Corp is named in copy only; no customer logo.
A thesis for named-account coverage · not a ratified plan
1:1 kits that travel with the hunters.
Europe was named in the round. NIS2 and the EU AI Act are creating board-level urgency around AI governance that did not exist eighteen months ago. My autonomous ABM engine’s job is the named-account layer underneath that expansion — so lighthouse logos are not waiting on a playbook.
Israel is home-market gravity (Tel Aviv R&D), not a net-new greenfield in the first four quarters unless you argue otherwise. HubSpot remains the system of record. You only pay when qualified meetings land.
The commercial model
You only pay when qualified meetings land.
20 minutes. Ten of Zenity’s actual Tier-1 accounts. My autonomous ABM engine produces a full 1:1 kit for each — landing page, ads, emails, outreach, hero asset — in days, not a quarter. Payment is on qualified meetings, not on content produced. Not a retainer. HubSpot stays yours.
In the 20 minutes
- Walk the Zenity page (this is what 1:1 looks like when the account is you).
- Align on jobs: Cinthia category, Maya meetings, Coley coverage.
- Name ten Tier-1s (or five if ten is a second meeting).
- Agree clock. Days, not a quarter. Pay when qualified meetings land.
What you keep
- HubSpot stays yours.
- I cover named accounts. Your team stays your team.
- SoftBank Corp remains the only named customer in this kit. No invented logos, no invented ROI.
- Inbound stays inbound. Docket already books. This is the 1:1 layer after the meeting.
If this kit is sharp on Zenity, it will be sharp on the ten accounts you actually care about.
Open the 1:1 page · zenity.climaxmarketing.co.ukPrint this file to A4 (background graphics on) for a PDF leave-behind. Suggested live slug: zenity.climaxmarketing.co.uk/brief.