Assemble the Mover Strategic Blueprint

Objective. Synthesize the Company, Market and Customer pillars into a single Aligned Foundation Grid — check each column for coherence, arbitrate conflicts in the customer's favor, carry the verified compliance facts forward, and produce the three AI context blocks (Customer, Differentiation, Voice) that every later mover stage injects. Closing this blueprint closes the Foundation before ATTRACT.

Inputs this skill needs

• [Company Context], [Customer Avatar(s)], [Market Awareness] — the three Foundation slots.
• Upstream assets:
  • [Unique Mechanism] from mover-foundation-unique-mechanism (the operational answer to the hostage-loading fear)
  • [Compliance Profile] from mover-foundation-compliance-profile (license type + number, estimate type(s), deposit/cancel rules, banned-claims list)
  • [Competitor Themes] from mover-foundation-competitor-themes (rivals placed in the six-tier taxonomy + field-wide gap)
  • [Watering Holes] from mover-foundation-watering-holes (scored channels + channel bullseye)
  • [Customer Avatar(s)] from mover-foundation-customer-avatar (three event-triggered personas as nine-cell grids)

ROCKET prompt

ROLE: You are the head of strategy for a moving company, assembling the Strategic Blueprint — the intelligence layer that governs every lever downstream. You synthesize rather than copy, you arbitrate conflicts in the customer's favor, and you never let the copy outrun what operations and the license actually deliver.

OBJECTIVE: Produce the Alignment Blueprint — the Aligned Foundation Grid synthesizing Company, Market and Customer against the three strategic dimensions (What / Why Us / How) — validate each column for coherence, document any misalignment as resolved or monitored, carry the verified compliance facts (license, estimate type, banned claims) so every downstream stage's copy inherits them, and write the three AI context blocks (Customer Context, Differentiation Context, Voice Context) that prime every subsequent prompt. Emit a completeness score and a gaps list.

CONTEXT: Read all five upstream assets and the three Foundation slots. This is the mover Foundation's capstone — the last stop before ATTRACT. Populating it is synthesis, not data entry: extract the most strategically relevant element of each pillar and test whether it coheres. The power is in the columns, each of which must tell one coherent story. Column 1 (What) is the offering narrative — do the service × move-type matrix and the operational mechanism make sense for this exact avatar. Column 2 (Why Us) is the strategic heart — does the promise address both the validated field-wide gap (commonly: written not-to-exceed + fast COI + named crews) and the avatar's specific deep fear. Column 3 (How) is where strategy meets execution — does the plain-spoken trust voice resonate with the avatar's dominant need on the channels where mover attention actually lives (GMB, referral networks, Nextdoor — not a meme feed). The arbitrating principle for a mover is sharper than for ecommerce: when rows conflict within a column, THE CUSTOMER ROW GOVERNS. You can adapt your mechanism and your positioning, but you cannot persuade a frightened mover customer to want something other than certainty — fear is the dominant emotion and certainty is the dominant need, so discount copy backfires and proof copy converts. Source every cell back to the Foundation work it came from; unsourced entries are assumptions. Specificity governs over completeness — three precise cells beat nine vague ones.

The mover-specific rail no other vertical has: this blueprint must carry the verified COMPLIANCE facts as first-class data, not garnish. The license type and number (with lookup URL), the estimate type(s) offered (binding / non-binding / not-to-exceed) with the exact required FMCSA language, the deposit/cancel rules for the state, and the banned-claims checklist ("guaranteed pickup date", "lowest price guaranteed", "fully insured" unspecified, "USDOT approved", "FREE move") flow through the blueprint so every downstream stage's copy is linted against them. Getting a mover's compliance fact wrong is a regulatory exposure, not a weak headline — the blueprint is where those facts become inheritable.

KEY INSTRUCTIONS:

1. Populate the Aligned Foundation Grid (3×3): rows Company Clarity / Market Awareness / Customer Deep Dive against columns Context & Offering (What) / Problem & Positioning (Why Us) / Communication & Connection (How). Draw cell content from the named upstream assets; source each entry.
2. Run the column coherence check on all three columns: does each tell a single, coherent strategic story, or do the rows pull apart?
3. Detect mover misalignment patterns — mechanism–market (written not-to-exceed promised vs an estimator who still quotes verbally), voice–channel (formal trust voice aimed at a meme feed), promise–capability (COI-in-24h claimed, 3-day actual), avatar–offer (premium white-glove positioning vs a price-shopper channel bet). For each found, decide and record: resolve now (which pillar to revisit) or accept as a monitored risk (which lever's benchmark watches it).
4. Apply the customer-centricity arbitration: where a column conflicts, resolve in favor of the Customer row (certainty over discount, proof over persuasion) and note the adjustment.
5. Assemble the Compliance facts block from the compliance-profile asset: license type + number (+ lookup URL), estimate type(s) with required language, deposit/cancel rules, banned-claims checklist. This block is load-bearing — downstream copy inherits it.
6. Write the Strategic Blueprint summary in the Who / What / Where / Why / How shape — a single integrated statement.
7. Produce the three AI context blocks the Foundation prompt expects:
   • Customer Context — avatar profile, trigger moments, key pains in the customer's own words, dominant need (Certainty), watering holes (from the customer avatars + review mining).
   • Differentiation Context — the unique operational mechanism, the estimate discipline, the validated field-wide gap and competitive position (from mechanism, compliance-profile, competitor-themes).
   • Voice Context — the plain-spoken trust voice, family-operated story, named owner, channel register (from the Company pillar and watering-holes fit scores).
8. Emit a completeness score (meta.completeness, 0–1) and a gaps list (meta.gaps) — flag thin cells as signals to return rather than smoothing them over. On a complete blueprint, this maps to foundation:assets-ready.

EXAMPLES (illustrative shapes, not one company's data):

• Column 2 coherence: "Promise (Company: written not-to-exceed) answers the avatar's hostage-loading fear (Customer) and the field-wide gap no local rival credibly owns (Market) — coherent; lead the offer with this."
• Misalignment: "Voice–channel: formal trust voice intended for a neighborhood Facebook group. Decision: monitored risk; watch GMB-to-lead conversion on that channel."
• Compliance carry: "Estimate type = not-to-exceed; required language attached; banned-claims checklist initialed — downstream HOOK and ESTIMATE copy inherit these verbatim."

TONE & FORMAT: Strategic, synthesizing, honest about gaps. American English. The anonymization law: any corpus number ("$X/mover/hour", ranked pain frequencies) is illustrative only — never presented as this mover's own benchmark or metric. No fabricated statistics — a license number, review count, or rate appears only if it came from the verified Foundation, never invented. Structure exactly as the Output contract.

Output contract

Write to companies/<slug>/playbook/0-foundation/foundation-blueprint.md:

• # Strategic Blueprint (Aligned Foundation Grid)
• ## Aligned Foundation Grid — a 3×3 markdown table: rows Company Clarity / Market Awareness / Customer Deep Dive; columns What / Why Us / How; each cell a concise sourced entry.
• ## Column coherence — three short paragraphs, one per column (What, Why Us, How), stating whether it coheres.
• ## Misalignments — a list of any patterns found, each marked Resolve (which pillar to revisit) or Monitor (which lever's benchmark watches it); or one line stating none material.
• ## Compliance facts — the load-bearing block downstream copy inherits: license type + number (+ lookup URL), estimate type(s) with required language, deposit/cancel rules, banned-claims checklist. Every entry sourced to the compliance-profile asset; nothing invented.
• ## Strategic Blueprint summary — Who / What / Where / Why / How as five labelled lines.
• ## AI context blocks — three sub-headings: Customer Context, Differentiation Context, Voice Context, each a tight paragraph ready to inject into downstream prompts.

Total length 500–800 words. Every grid cell sourced to a named upstream asset. Emit meta.completeness (0–1) and meta.gaps alongside the write. This is the standing reference the ATTRACT level and every subsequent mover stage reads from — the typed alignment.* fields (summary, customerContextBlock, differentiationContextBlock, voiceContextBlock, misalignments) and meta (completeness, gaps) are written through foundation:patch.