Draft · Team presentation · 12 Sep 2026

Connek Marketing Strategy

Privacy-first corporate MCP gateway. Product pivot — Steve builds, Andy’s side markets.

Demand: WARM → PROBE Window: Oct 2026 probe No spend / outbound without Andy yes

1. Executive summary

Connek is a privacy-first corporate Model Context Protocol (MCP) gateway — a Composio-style connector layer for agent platforms where the organisation owns the secrets, not a third-party connector SaaS.

Regulated mid-to-large buyers keep repeating the same objection: handing API keys and OAuth to a hosted catalog is a compliance non-starter. That pain is real. It is not yet proven paid demand. Honest posture: warm → probe.

October wedge: six VenMCP marketing connectors (Google Analytics 4, Google Search Console, Google Ads, Meta Ads, DataForSEO, Google Tag Manager) — depth, not catalog race — plus Keycloak / OpenID Connect (OIDC), bring-your-own (BYO) OAuth, audit, Australian residency / virtual private cloud (VPC) path.

Pivot: Connek is the product the team works on — not Ven Agency delivery packaging. Steve owns build. Andy’s side owns marketing and planning. Probe success = calls, problem statements, letters of intent (LOIs) / paid pilots — not vanity launches.

2. Situation

Why pivot

VenMCP already runs real connectors, portal, Keycloak/OIDC patterns, and Australian endpoints. Keeping that only as “agency delivery” traps the product thesis inside client work. Andy’s 12 September 2026 brief: Connek is the product — Steve builds, Andy’s side markets.

Market problem

Agent platforms need connectors. Hosted catalogs win breadth. Regulated buyers (finance, healthcare, government, compliance-bound software-as-a-service) often refuse the trade: credentials leave the network. They want self-host or VPC, org identity provider (IdP), BYO OAuth, vaults, audit, allowlists, residency, and a data processing agreement (DPA).

Why warm, not hot

Uncertainty: Public posts ≠ purchase orders. No fabricated metrics. No claim of paid demand we have not earned.

3. Product definition

What Connek is

What Connek is not

Honesty gate: If October tokens still sit on Ven-managed infra, say: managed AU residency, encrypted at rest, no multi-tenant key pooling. Customer KMS / VPC vault = post-pilot roadmap. Never overclaim custody.

4. Positioning + USPs

Connek is company-owned MCP connectors for agent platforms — your login (Keycloak / OIDC), managed Australian hosting for secrets we can describe honestly, audit and residency — not another hosted catalog that pools your keys. Customer vault / your-network path is roadmap until Steve confirms it ships.

Positioning statement

For platform and security leaders at regulated mid-to-large organisations who need agent connectors without handing keys to a third-party SaaS, Connek is an org-owned MCP gateway that ships a deep marketing connector pack behind the customer’s IdP, BYO OAuth, audit, and Australian residency / VPC path. Unlike Composio, Claude managed MCP catalogs, and thin DIY gateways, Connek sells custody and connector quality in one wedge.

Five USPs (honest)

USP 1 Honest custody — managed AU hosting (encrypted, not pooled); customer vault only after Steve confirms
USP 2 AU residency + documented VPC path
USP 3 Audit of tool calls + org allowlists
USP 4 Depth on six VenMCP marketing connectors
USP 5 Design-partner path: pilot, LOI, DPA outline

October USP #1 lock: Today’s VenMCP still stores Google refresh tokens on our side (encrypted). Lead with managed Australian hosting until Steve confirms a customer-held vault ships.

USPVs ComposioVs Claude managed MCPVs DIY
Honest custody (managed AU default) They win managed catalog; many still hear third-party custody Convenient inside vendor trust boundary; we sell a clearer perimeter story DIY can match custody; we productise managed AU for pilots
AU + VPC path Residency often enterprise custom Follows AI vendor cloud story Self-host anywhere; we offer managed AU first
Audit + allowlists Enterprise tiers; mid-market catalog-first Vendor-platform governance You build logging/RBAC; we aim pilot-ready export
Six-connector depth They win 1,000+ toolkits — we don’t claim that Coverage chase; our wedge is marketing stack DIY starts empty; we ship a pack
Design-partner commercial Self-serve + enterprise call Platform upsell No sales kit; we sell a time-boxed pilot

We will not claim: beating Composio on connector count; paid demand; SOC 2 / BAA / air-gap in October; Reddit/HN = pipeline.

5. Target customer

LensDefinition
PrimaryPlatform / AI platform eng lead + Security/IT (CISO-adjacent) at mid–large regulated orgs
VerticalsFinance, healthcare, government, compliance-bound SaaS
TriggerRolling out agents; stuck on credential custody, residency, or IdP
CriteriaSelf-host/VPC; org IdP (OIDC/Keycloak); vault; audit; allowlists; DPA; AU residency
SecondaryTeams that already rejected Composio/Zapier MCP on custody/residency

Who we ignore

Channels: Warm Ven network + LinkedIn primary. Hacker News for themes. Reddit tertiary only — not primary validation.

6. Messaging framework

Headline options (DRAFT)

  1. Org-owned MCP. Your IdP, your vault, your residency.
  2. Agent connectors without handing your keys to another SaaS.
  3. Deep marketing MCP for regulated teams — custody first, catalog later.

Proof points (only if true)

Objection handlers

ObjectionHandler
Composio has SSO/SCIMTable stakes. Ask where tokens live and if AU/VPC is standard. Offer architecture interview.
Need 50 connectorsPre-qualify for marketing wedge + paid custom later. Else not an Oct partner.
Just another gateway?Commodity without depth + honest custody. Demo VenMCP + residency.
Claude MCP is enoughFine inside that vendor’s boundary. We exist for org-owned OAuth/audit outside one AI vendor.
We’ll self-host OSSValid. We sell time-to-pilot: IdP, vault story, six connectors, audit, DPA outline.
Where do tokens live?Answer only from architecture truth doc. Never invent customer KMS.
What’s the price?No public list. Internal only: discuss A$5–15k POC or A$2–5k/mo pilot (1–3 months).

Tone: plain British English. Calm. Specific. No hype. Expand jargon once.

7. Go-to-market (October probe)

Window: ~12 Sep → 31 Oct 2026 (Melbourne). Soft public launch optional. Prefer thin commercial wrapper + 1–2 design partners.

Channels

#ChannelUse
1Warm Ven network + LinkedIn15–20 shortlist → interviews → pilot/LOI
2Competitive teardown (buyer mode)Composio/Arcade enterprise demos; custody gaps
3Hacker NewsThemes only — not pipeline
4RedditTertiary noise filter

Assets (unpublished until Andy yes)

Needs Andy’s yes

  1. Probe scope + kill criteria
  2. Custody story we may sell
  3. Warm outbound + landing drafts unlock
  4. Steve as build owner / eng spike confirm
  5. Soft-launch decision
  6. Any spend (domain, ads, counsel, tools)
  7. Pricing bands for any public surface

Roles: Andy = decisions + marketing/planning. Steve = build. James = warm intros when unlocked. Charlie/agents = drafts only — no spend/publish.

8. Success metrics (probe)

Discovery calls completed≥5
Written problem statements≥2
LOIs or paid pilot agreements≥1 strong (ideally 2)
Pilot live (non-Ven IdP or clear managed AU)≥1
Custody/residency rejection of Composio/Zapier in notes≥2 calls

Not metrics: HN upvotes, Reddit karma, Product Hunt, vanity traffic, launch blog without commercial signal.

Kill / park if

Do not kill solely because Reddit or Hacker News is quiet.

9. Open decisions

Andy (marketing / planning / commercial)

  1. Approve this strategy and probe scope (or edit)
  2. Confirm custody story for October (managed AU vs true customer vault)
  3. Unlock or withhold warm outbound + landing/one-pager drafts
  4. Soft launch mid-Oct: yes / no / after first three calls
  5. Working name Connek — proceed; domain/trademark timing (no buy yet)
  6. Keep A$5–15k POC / A$2–5k/mo as internal talk-track only?
  7. Who owns call notes + LOI chase day-to-day under Andy’s side?

Steve (build)

  1. Confirm primary deploy: managed AU + documented VPC path
  2. Architecture truth: where tokens live today vs mid-Oct demo
  3. Multi-tenant isolation + audit export: scope and exit date
  4. Connector harden priority across the six
  5. Confirm out-of-October: SCIM, air-gap appliance, catalog expansion

Joint

  1. Kill criteria still stand under “Connek is the product” pivot?
  2. Weekly 30-min Andy–Steve checkpoint after 14 Sep return
  3. End-Oct gate memo: continue / narrow / park — who drafts?