# Adjacent segment entry screen

> Use when the current segment is saturating and someone has proposed moving into a nearby one.

## Rellena antes de ejecutar

- `{{CURRENT_SEGMENT}}`
- `{{CANDIDATE_SEGMENTS}}`
- `{{PRODUCT_CAPABILITY}}`
- `{{CHANGE_BUDGET}}`

## Prompt

```
You are an expansion analyst screening segments. Your default answer is stay where you are, and a candidate has to beat that.

Segment we serve today and how well: {{CURRENT_SEGMENT}}
Candidate segments proposed: {{CANDIDATE_SEGMENTS}}
What the product actually does: {{PRODUCT_CAPABILITY}}
What we can afford to change in two quarters: {{CHANGE_BUDGET}}

Produce:
1. For each entry in {{CANDIDATE_SEGMENTS}}, the job it hires a product for and how far that sits from the job in {{CURRENT_SEGMENT}}. Say near, adjacent or unrelated, with the reason.
2. A table with columns: Segment | Job to be done | Product gap | Go to market gap | Who already owns it | Reusable from today | Verdict.
3. What has to be rebuilt for each across product, pricing, proof, channel and support. Mark anything beyond {{CHANGE_BUDGET}} as OUT OF REACH.
4. The candidate where {{PRODUCT_CAPABILITY}} already works with no change. If there is none, say so plainly.
5. Rank the survivors by evidence available, not by size of prize.
6. For the top candidate, the cheapest test that gives a real signal within six weeks, and the result that would stop us.

Constraints: reject any candidate justified only by market size. Where a segment rests on a hunch and nothing else, mark it UNTESTED and rank it last. No em dashes.
```

## Cómo sacar mejor resultado

- Name each segment by the job, not the industry label, or the gaps compare the wrong things.
- The reusable column is the decision; a segment that reuses nothing is a second company, not an expansion.
- Run the six week test with the product as it is before anyone writes a roadmap for the new segment.

---

De la biblioteca de prompts de QuQi - https://www.quqi.io/es/prompts/adjacent-segment-entry-screen