Marketing reframe

Marketing Reframe

Public edition. Re-authored from a production calibration skill. The production version carries private source routes and course references; this edition keeps the judgment contract: how a real mechanism earns Marketing language without being inflated into commercial ownership.

The judgment, in one screen

What this skill prevents: Marketing-washing — adding words such as segmentation, lifecycle, campaign, or attribution to work whose mechanism cannot support them. The opposite failure matters too: leaving a real Marketing judgment hidden behind internal workflow language and making the hiring manager translate it alone.

The calls it hardcodes:

• Name the buyer and next action first. A capability is useful only relative to someone who needs to make a decision: continue reading, invite an interview, change a priority, trust a handoff.
• Recover the mechanism before naming the capability. signal -> judgment -> action -> state / handoff -> observed result -> next-cycle change. Missing links stay missing; tool names cannot fill them.
• Choose the smallest portable capability. One or two precise reads beat a wall of Marketing vocabulary. The mechanism must still make sense after the fashionable noun is removed.
• Label the evidence level. Direct proof, analogous proof, method inspiration, or forbidden claim. Domain, scale, causality, and ownership never rise through wording.
• Translate intent, not just nouns. A valid reframe changes who the work serves, which decision it improves, or which next action becomes possible.

One system, worked (the public run): screening a large job-market pool under a written rubric directly proves qualification and attention-allocation discipline in the candidate's live system. It is analogous proof for commercial segmentation: the judgment shape transfers, but it does not become campaign-targeting ownership. The worked run applies that same test across stakeholder research, positioning, conversion QA, CRM state, and loss learning.

Everything below is the working contract. The public run fills it against the same Candidate GTM system this repository exhibits.

Purpose

Turn a real project, workflow, or experience into a Marketing / GTM capability read that a hiring manager can understand and the operator can defend in twenty seconds. The output is a calibration brief for a public surface or downstream writer — not final copy and not permission to borrow role nouns.

The skill has two modes:

• Proof reframe: what Marketing / GTM capability does this true mechanism demonstrate?
• System-intent calibration: who does this workflow node serve, which action or state should it improve, and where does its output hand off?

The mechanism test

Before naming any capability, reconstruct:

signal / input
  -> judgment
  -> action
  -> state or handoff
  -> observed outcome
  -> next-cycle change

If the material proves only tracking, call it tracking. If it proves a defined metric, a review rhythm, and a decision consequence, measurement may be defensible. If it proves a loss hypothesis but not causal credit assignment, call it loss learning — not attribution ownership.

Evidence levels

Level	What it means	Public-language consequence
Direct proof	Same judgment shape, work object, and outcome were performed	Role-native language is safe within the proven scale and ownership
Analogous proof	The judgment transfers, but domain, scale, or ownership differs	Name the portable capability and the analogy; keep the commercial boundary visible
Method inspiration	A framework helped design the approach, but execution proof is absent	Keep it in method or learning language, never as an outcome claim
Forbidden claim	The wording would require nonexistent ownership, causality, domain, or scale	Do not publish it; wording cannot repair the gap

Capability families

Use the minimum family that explains the mechanism:

• market / buyer understanding;
• qualification, segmentation, prioritization;
• positioning, value proposition, message QA;
• channel or touchpoint orchestration;
• lifecycle follow-through;
• CRM state and data trust;
• AI-assisted workflow orchestration with human approval;
• measurement and decision learning.

These are lenses, not a checklist. A project does not become stronger by claiming all eight.

Output contract

Target buyer / next action:
Original intent:
Reframed Marketing intent:

| True mechanism | Capability | Evidence level | Natural proof angle |
|---|---|---|---|

Do not borrow:
Downstream handoff:

The brief must let the next writer preserve the mechanism and boundary without copying this framework's vocabulary verbatim.

Quality gate

• Buyer gain: does the reframe identify who uses the work and what decision or action changes?
• Mechanism gain: did the capability grow from a real judgment chain rather than noun substitution?
• Evidence honesty: are domain, scale, causality, and ownership still where the source left them?
• Human story: can the operator explain the signal, judgment, action, and next-cycle change without hiding behind tool names?
• Node fit: does the workflow node own its direct result — targeting accuracy, message clarity, conversion QA, state integrity, or learning — rather than claiming the whole funnel's outcome?

What this skill never does

• Never turns one contact into a persona or a static list into lifecycle ownership.
• Never calls a loss hypothesis formal attribution.
• Never converts a personal CRM workflow into production administration.
• Never converts AI-assisted research and QA into autonomous operation.
• Never replaces the hiring-market read, candidate truth source, or final surface owner.