---
name: map-what-ring-specific-content
description: "Make it clear what your business sells before you plan more content."
category: Strategy & Measurement
stage: —
definitive_article: /topic-wheel
status: complete
---

# Map the WHAT offer at the center

Make it clear what your business sells before you plan more content. This guide defines the center of your topic map. Start with the real offer, who buys it and the problem it solves.

**The path:** Real offer → Clear WHAT → Evidence check → HOW topics

**Start when:** A new or revised Topic Wheel needs its central offer defined.

## Inputs

- [Topic Wheel, the map of your offer, topics and real stories](https://blitzmetrics.com/topic-wheel/) current source and any existing wheel.
- The actual service or product, buyer, service area and supporting business records.
- Current customer language and the owner’s accepted scope.

## Steps

1. Follow the maintained geometry: WHAT is the center, HOW is the middle ring of useful topics, and WHY is the outer ring of people and real stories. The stable task slug contains “ring”; it does not make WHAT an outer content backlog.
2. List what the business actually offers. Separate a current offer from an aspiration or a past service, and name the buyer problem it solves.
3. Draft one plain sentence stating the offer and who it serves. Use a specific customer-facing description rather than a broad mission slogan.
4. Check that sentence against the service page, real work and the owner’s accepted scope. Resolve conflicting claims or geography; do not make the offering broader to fill a wheel.
5. Place the checked WHAT in the center with source links and date. Put proposed questions in a separate backlog; they will connect to HOW topics and WHY stories, not replace the central offer.
6. Hand the center statement to the HOW task. Keep the existing canonical offer page as the trunk of the [SEO Tree, the map of related pages](https://blitzmetrics.com/seo-tree/); propose a missing page only after checking for an existing owner.

## Definition of done (QA checklist)

Quality assurance (QA) means checking the result against its agreed requirements; see the [Article Guidelines](https://localservicespotlight.com/article-guidelines/).

- [ ] The WHAT center states a real specific offer and customer problem.
- [ ] The saved wheel uses WHAT center/HOW middle/WHY outer consistently.
- [ ] Sources and the next topic-mapping task are linked.

## Example(s)

**Fictional teaching example. This is not a client result or proof of a completed run.**

A fictional plumbing firm offers emergency repair and heater installation in one city. That is its WHAT. “Why does my heater leak?” is a useful recording question, but it is not the center of the wheel. The question belongs under a heater topic connected back to the actual service.

## Handoff and Content Factory context

[Map HOW topics](https://local-service-spotlight.github.io/task-library/?task=map-how-ring-methods#task-map-how-ring-methods) receives the checked WHAT and service proof.

This work supports Produce in the [Content Factory: Produce, Process, Post and Promote](https://blitzmetrics.com/content-factory/). The selected sources pass to Process, approved outputs go to Post, and useful proven work can enter Promote. The real inputs and handoff above set this task’s scope.

## Start with an agent

Give the AI worker this recipe, the real Inputs, the desired result and the actions already authorized. Ask for the saved output, source evidence, passed and failed checks, and the next owner. A skill is a set of instructions. Loading it does not prove access, install a scheduled job or complete the work. Use the [current installation guide](https://localservicespotlight.com/install/) only if reusable setup is needed; a ZIP contains instructions and is not an access grant.

Use the actual supported app and verified source access. A model name is not a promise of browser control, memory or unattended work. For recurring work, inspect the real job’s trigger, owner, timezone and observed firing; this recipe creates no schedule. Before any media playback, mute the player and set volume to zero. A silent review does not prove sound was heard.

## Record the real execution

Open the run record when work begins. Keep one execution ID, the exact starting recipe revision, input sources and actual state. Write a [meta article, the record of one real execution](https://blitzmetrics.com/meta-article-prompt/) with results, checks, failures and next owner. Link it to this task in the [Task Library](https://local-service-spotlight.github.io/task-library/). Writing is required; public release follows existing authority.

Reuse the same execution ID for internal reviews, meta writing, revisions and retries. A blocked run stays open with its dependency and owner, without an invented finish time. Keep historical public examples as dated evidence; article counts alone are not verified execution frequency. Use supported findings to propose and verify a recipe improvement.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** —
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 2 (supporting)
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Save this task’s actual output, source, date and checks where the receiving owner can read them. Follow the Inputs and Handoff sections for its next step.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- [Maintained source guide](https://blitzmetrics.com/topic-wheel/)
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=map-what-ring-specific-content#task-map-what-ring-specific-content)
- [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Definitive article and task recipe standard](https://blitzmetrics.com/definitive-article-guide/)
- [How recipes and run records work together](https://localservicespotlight.com/meta-articles/)

## Review and evidence still needed

The inherited contributor status is `complete`. It is preserved, not promoted by this rewrite. That label alone does not verify document readiness, account access, an actual execution or a client outcome.

A relevant real execution, source evidence, independent reviewer and accepted handoff remain to be recorded. The fictional example teaches the method and does not fill a real-run evidence gap. The opening and full method need a named semantic reviewer; the task-specific path is source guidance, with visible desktop/mobile presentation still to check.