Your move
Name the expensive problem
Define the buyer condition your work is meant to change before describing the service.
Name the buyer, the observable condition they want changed, and the cost or consequence in their own evidence. Do not manufacture a dollar value to make the offer sound important.
Do this now
Three moves, in order.
- Collect exact language from buyer conversations, requests, losses, delays, or repeated work.
- Separate the symptom they notice from the condition your work can change.
- State the consequence using their measure—or leave it qualitative until verified.
Build the artifact
Problem statement
Copy these fields into a note, document, or sheet you already use.
Buyer
Who owns or feels the problem
Current condition
What is happening now
Consequence
Measured or observed impact
Evidence
Where this came from
Give AI the bounded job
Prompt from your artifact—not from vibes.
Turn these buyer notes into a problem statement. Preserve their measures and wording. Do not add ROI, urgency, cost, frequency, or emotion that is not in the evidence.
Before you use it
The work leaves your hands only when:
- The statement names a buyer and current condition.
- Any number points to a real record.
- The problem can exist even if your service does not.