In Strategy Coach, the What problem do you solve field is your first commercial asset. This is not a form field. This is the foundation of how the practice moves.

Write the problem in buyer language. Remove internal jargon. Replace capability words with pain words. Tie pain to a trigger that makes it urgent. A problem statement written in operator language sounds like you explaining what you do. A problem statement written in buyer language sounds like your client describing why they picked up the phone in the first place.

Once the problem is clear, everything else becomes easier. The proof you gather supports the claim. Referrers know what to say. Buyers know whether to take the call. Your actions have purpose. Your content is aimed instead of speculative.

Strategy Coach surfaces that problem across the whole app. Visibility changes behaviour. When the problem is in front of you, you reject conversations that do not fit. You write content that supports it. You reach out to relationships who feel it. The problem becomes the operating centre of the practice, not a detail buried in a bio.

Every time you draft an outreach message, Strategy Coach reminds you of the problem you own. That means the language you use returns to the problem instead of drifting into generic professional compliments. Instead of How have you been, let us catch up, you write: I saw this article on founder dependency and thought of you. I know you solved this with us during your restructure. I wondered whether you knew someone else drowning in the same situation right now. The first message assumes a relationship. The second assumes a relationship and gives the recipient language they can repeat.

When you write a post, check it against the problem. Does this reinforce it or distract. Does this language sound like how a buyer would describe the pain. The problem keeps you focused. It prevents the drift into generic advice. It also makes the work easier, because you are not guessing what to write. You have a centre.