Compound Consultant
Phase 1 — Positioning
1.4 · Refine · Recurring Loop

Iterate Your Positioning

Bring your market signal back to the Strategist Coach. Re-invoke the Positioning Architect skill in iteration mode. The coach categorizes the feedback, drafts revisions, and updates your canonical files — without unraveling what's already working.

30–60 min per iteration · 5+ ICP conversations logged first
What This Is

The same skill. A different mode.

The Positioning Architect skill you ran in 1.2 has an iteration mode built in. You don't install a separate "refinement coach." You re-invoke the same skill — but this time you bring market signal as input, and the skill makes targeted edits to your existing files.

The skill categorizes what you bring (language issue, emphasis issue, substantive revision, or noise), helps you decide whether to adjust, makes the minimum viable edit, and updates the version tracker. It protects what's working. It pushes back on weak signals. It tells you when something feels bigger than a refinement and needs a full re-build.

Positioning isn't a document you finish. It's a living system you sharpen. This is the loop that does the sharpening — and it runs as long as you're in market.
Before You Run It

One thing must be true.

You have 5+ ICP conversations logged. With verbatim quotes. With your reads (Hell Yes / Hell No / Grinfucker). Pattern data, not vibes.

If you only have 1–2 conversations, hold. One reaction is an anecdote. Patterns emerge at 5+.

If you can't help iterating after every conversation

That impulse is uncertainty, not signal. The skill will push back on it — "you've heard this once, let's wait until it shows up two more times." Trust the discipline. The conversations are doing real work even when they don't trigger a change.

How to Invoke Iteration Mode

Same coach. Different trigger phrase.

Open your Strategist Coach. Use any of these trigger phrases — and immediately paste in your signal.

Trigger phrases for iteration mode
  • "Iterate my positioning with this feedback"
  • "Refine my positioning"
  • "Here's signal from the market"
  • "Update positioning based on these conversations"

The skill reads your current positioning files (it has them in its knowledge base) and processes the signal against them. You don't need to upload anything new — just paste the feedback into the chat.

What You Paste In

Raw signal. Not your interpretation.

The skill works best with unfiltered material. Don't summarize. Don't decide what matters before the coach gets to it.

How the Coach Categorizes

Five categories. Different responses.

Before changing anything, the skill maps your signal to one of five categories. The category determines whether — and how — to adjust.

Category 1

Positive confirmation

ICP leans in. Content using the Enemy framing gets engagement. Referral partners describe you accurately. Prospects say "that's exactly what I'm dealing with."

Response: "That's your positioning working. Note what specifically resonated. Double down."

Category 2

Language-level issue

Concept is right, specific words don't land. People ask "what do you mean by [term]?" Content gets engagement from the wrong audience. The elevator version doesn't land in conversation.

Response: Adjust phrasing. Don't change the underlying positioning. "What words did THEY use? Let's swap to their language."

Category 3

Emphasis issue

People respond to one part but not others. They remember the Enemy but can't recall the problem. The mechanism interests peers but not buyers. Narrative version works but elevator doesn't.

Response: Reorder the emphasis. Lead with what's landing. "Based on what's resonating, should we restructure which element comes first?"

Category 4

Substantive issue

ICP doesn't match who's showing up. The problem statement doesn't resonate. A different problem gets stronger reactions. POV gets pushback because it's wrong, not because it's contrarian. Mechanism doesn't match what you actually deliver.

Response: Real revision. Identify which circle is off. Make the substantive change. Bump to major version.

Category 5

Noise — no change needed

Feedback from someone outside your ICP. One negative reaction in a sea of positive ones. Pushback from people who ARE the enemy's defenders (this is actually confirmation). Confusion from someone who wasn't paying attention.

Response: "This doesn't warrant a change. Here's why..." Helps you not overreact.

The Loop

What the skill does with your signal.

Once categorized, the skill follows the same five-step pattern every iteration.

  1. Compares signal against current positioning files
    Identifies the specific section the signal contradicts, confirms, or sharpens.
  2. Surfaces the implication clearly
    "This objection tells us your core-problem.md is reading as too vague — they corrected your language with their own."
  3. Drafts a revision and explains the reasoning
    Shows current vs proposed side by side. Doesn't just produce — teaches.
  4. Updates all affected files
    Language change → may update pain-maps, desire-maps, core-problem. ICP change → updates icp.md, may cascade. POV change → updates narrative-spine, may cascade to all others.
  5. Bumps the version + updates the evolution tracker
    v1.0 → v1.1 (language), v1.0 → v1.2 (emphasis), v1.0 → v2.0 (substantive). Tracker captures date, change type, what changed, why, signal strength.

Your job is to bring honest signal, decide what to accept, commit the change. The skill handles the analysis, the rewrite, and the bookkeeping.

The Rules

Four rules the skill enforces.

  1. 01 Minimum viable edit. Change only what the feedback demands. Don't unravel the whole brief because one sentence didn't land.
  2. 02 Preserve what's working. Before changing anything, the skill asks: "What parts ARE working?" Those parts get protected.
  3. 03 One change at a time. If you have feedback on multiple areas, address them one at a time. Changing everything at once makes it impossible to know what helped.
  4. 04 Track every change. No silent edits. The Positioning Evolution Tracker captures what changed, when, and why.
When Iteration Isn't Enough

The skill will tell you when something is bigger.

Sometimes market signal points to a fundamental problem — not a refinement. The skill will name this directly and recommend a fresh build pass.

Escalation triggers:

If triggered, the skill recommends: "Step back. This might need a fresh run through [POV / Problem / Person] rather than incremental edits. Re-invoke this skill from Phase [X]."

Knowing when something is bigger than a tweak protects you from the death spiral of endless refinement. Trust the skill's escalation.
After Iteration

Save updates. Re-test in the market.

After every iteration session:

  1. Copy the updated file(s) from the code blocks
  2. Replace the previous versions in your /Compound Consultant OS folder
  3. Re-upload to your Strategist Coach project (this keeps the coach reading the latest version)
  4. Take the updated positioning back into market conversations
  5. Log signal. Bring it back to iteration mode when patterns emerge again

The loop runs as long as you're in market. v1.0 → v1.1 → v1.2 → v2.0 → and forward. Each version is sharper than the last because each is grounded in real signal, not assumptions.

Phase 1 Complete

You have tested, iterated positioning.

Diagnostic done. Positioning built. Tested in market. Iterated against signal. The foundation is solid. Phase 2 builds the commercial assets — Offer Doc, Sales Page — directly on top of this foundation.

Phase 2 — Package →