Marketing Identity: Lead-Gen Layer
Single source of truth for who we're chasing and with what hook. Every marketing-related skill loads this first. This skill complements commons:identity (brand-level positioning) with the distribution-and-lead-gen layer.
Upstream Sources of Truth (read before drafting)
Load these once per session in order:
commons:identity: positioning, vocabulary, the two ICPs, the two CTAs/var/www/html/systemprompt-web/reports/pivot/positioning.md: approved pivot positioning (wins on any conflict)/var/www/html/systemprompt-web/reports/pivot/handbook.md: pillars, value model, KPIs, tiers (copy facts from here, never invent)/var/www/html/systemprompt-web/reports/marketing/marketing-strategy-master.md: current strategy state (read-only here, written bymarketing-strategy-master)
If any file is missing, stop and tell Ed.
The Lead Definition
Two kinds of lead, tracked separately:
- Partner lead: a consultancy, system integrator or AI practice that submits a partner application at
/partners/apply, or replies to outreach asking how the programme works. Qualified when the firm has a delivery practice and named people who would certify. - Buyer lead: an enterprise buyer who submits a request at
/partners/find. Qualified when they name a workflow, an executive owner and a likely pillar. Buyer leads are routed to certified partners; we do not sell to them directly.
Page views, follows and likes are not leads.
Funnel 1 (primary): Partner programme for consultancies
Who: practice leads, alliance leads, managing partners and delivery heads at consultancies, system integrators and AI practices.
What they say out loud:
- "Our clients want governed AI and we have no repeatable method."
- "We need an AI practice that is more than prompt workshops."
- "How do we prove our people can deliver this?"
The hook: "AI implementation is a services business with a software core. Get the software, the method (three tracks, seven pillars) and the certification to sell, design and build governed AI inside your enterprise clients."
CTA: Become a partner → https://systemprompt.io/partners/apply
Funnel 2: Find a certified partner, for enterprise buyers
Who: CIO, CISO, COO, CRO, CFO, CHRO at organisations that want a governed AI implementation with a measurable KPI.
What they say out loud:
- "Security keeps blocking our AI rollout."
- "The board asks what our AI spend buys."
- "We have one workflow that is drowning and nobody can safely automate it."
The hook: "Governed AI across the systems that run your business, designed and implemented by a certified partner and measured against your own baseline."
CTA: Find a certified partner → https://systemprompt.io/partners/find
Buyers are a content and inbound audience. Do not cold-email executives at enterprise buyers; build authority through pillar content they find when they search.
Where They Live Online (validate with data, do not assume)
| Channel | Audience | Signal |
|---|---|---|
| Practice and alliance leads at consultancies and SIs; CIO/CISO/COO at buyers | AI practice launches, hiring for AI consultants, posts about AI rollout and governance | |
| Consultancy and SI communities | Partner-ecosystem groups, AI practice leaders | Practice building, certification, delivery method |
| Industry newsletters and events | Both | AI architecture, governance, FinOps, operating model |
| Search (pillar and track pages) | Both | Pillar outcome queries, AI governance queries, AI certification queries |
Never use as funnels: GitHub repos, crates.io, docs.rs, install pages or the template repo. Those are not CTAs any more.
CTA Rule
All distribution drives to exactly one of the two CTAs:
- Become a partner →
/partners/apply(partner-facing content) - Find a certified partner →
/partners/find(buyer-facing content)
Pillar and track content may use "See the certification" as a contextual link. Never "Book a call", "Request a demo", "Start free", "clone the template" or a GitHub link. One CTA per post.
Hypothesis Format (mandatory for every action)
Every logged action must include:
[H-###] If we {verb + specific action} on {channel} targeting {ICP-subsegment},
then {metric} will {direction} by {Δ or target} within {window}.
Reason: {insight or prior evidence}.
Example:
[H-112] If we post a breakdown of "Sales owns why, Business Analyst owns what,
Development owns how" on LinkedIn targeting practice leads at SIs,
then /partners/apply submissions (14d) will increase from baseline [N]
to ≥[N+2] within 14 days. Reason: the three-track split answers the
"how do we staff an AI practice" question directly.
Ambiguous metrics ("more engagement", "better reach") are rejected. Pick a metric from lead-tracker's output.
Rules for Every Draft
Inherits everything from commons:brand-voice, plus:
- No em dashes. Commas, parens, periods, or restructure.
- No banned words (see commons:brand-voice pivot banned list). Extra banned in outreach: "reach out," "touch base," "circle back," "exciting news," "game-changer," "excited to share."
- Qualify, never offer a call. Ask the question that qualifies (practice size, delivery capability, workflow, executive owner, pillar). Never offer a call, meeting or demo. Route to the CTA.
- No unsubscribe footer. Outreach is personal 1:1 from Ed.
- Never fabricate traction. No made-up partner counts, customer quotes or percentages. Use real numbers from
lead-trackeror omit. - One CTA per post. One link.
- Specificity beats enthusiasm.
- The product is "the software" or "the runtime". Never library, platform, framework, template or open-source project.
- Brand is
systemprompt.io, always lowercase. - Say "three tracks" and "seven pillars" exactly.
- No hashtags on any platform.
- Ed posts everything himself. Drafts must be copy-paste ready, no placeholders like
{name}unless it's a personalised DM and the placeholder is in square brackets at the top of the file for Ed to replace manually. - Every draft is tagged with its
[H-###]in a footer comment sohypothesis-ledgercan track it.